Discussion about include file location.

   Date: Tue, 13 Aug 2002 10:32:27 -0600
   From: "Huston" <[email protected]>

   Does anyone know of another project with similar platform requirements and
   how they structure their source tree? I'm open to changing the structure,
   even moving the header files into a common directory as long as it works for
   all of the platforms: threaded_os - linux, netbsd, solaris, win32;
   non_threaded_os - qnx (not checked in yet).

A quick sampling of a few different packages:

* OpenSSL distributes a tar file with a directory "include/openssl" at
  top level.  The directory is filled with symlinks pointing to the
  include files.  I don't know if they use CVS; if so there may be
  some hack to maintain the links.  OpenSSL builds on very wide
  variety of systems.

* GLIB 2.0 has all the library source, both .c and .h, in a directory
  "glib" at top level.  This allows references "<glib/FOO.h>" to work
  during the build.  GLIB builds on unix-like and Windows systems.

* libxml2 has a directory "include/libxml" at top level.  All of the
  include files are located in that directory.  libxml2 builds only on
  unix-like systems.

Each of these packages has a different variant of the same solution.
What I did for beepcore-c is yet another variant.  I think that we
should choose a variant that everyone can live with and be done with
it.  I don't particularly care if it's the one I chose or something
else.

Chris


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code1