Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Wed, 22 Dec 1999 23:41:56 -0500
From: Christopher Faylor <cgf AT cygnus DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: New winsup layout
Message-ID: <19991222234156.A13583@cygnus.com>
Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i

I've been discussing changing the layout of the winsup directory
with DJ and Mumit and I'd like to get other's thoughts on the
matter.  The new layout that I've been playing with looks like this:

winsup
  cygwin
    config
    include
      ...
    regexp

  include
  mingw
    ...
  sysdef
  utils (cygutils?)

This essentially moves all of the cygwin-only stuff into its own
directory, adds an extra windows-only include (i.e., Anders w32api
stuff), and leaves everything else

The advantages are that it will be slightly easier to import include
and mingw and that (I think) the layout is cleaner.  The disadvantages
are that this adds an extra "make layer" to the process of building
cygwin.  Of course, you can always cd to winsup/cygwin if you just
want to build cygwin...

We had also discussed moving the w32api and mingw directory up a level
into "devo" but, personally, I like having all of the windows stuff
under one roof.

Does anyone have any objections to the above layout?

cgf