FreeTDS Development Group

[Steve Langasek <vorlon AT netexpress.net>]

On Fri, Oct 11, 2002 at 11:34:04AM -0400, Lowden, James K wrote:
> > From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> > Sent: October 11, 2002 8:19 AM
> > > 
> > I'd use a src/win32 directory... with some project file/makefile

> I vote No on that suggestion.  

> $ ls -l src |grep ^d
> drwxr-xr-x  2 jklowden  staff    512 Sep 24 16:30 CVS
> drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 apps
> drwxr-xr-x  5 jklowden  staff    512 Oct 10 10:28 ctlib
> drwxr-xr-x  5 jklowden  staff    512 Oct 10 10:28 dblib
> drwxr-xr-x  5 jklowden  staff    512 Oct 10 12:40 odbc
> drwxr-xr-x  4 jklowden  staff    512 Oct 10 12:41 pool
> drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 replacements
> drwxr-xr-x  4 jklowden  staff    512 Oct 10 10:28 server
> drwxr-xr-x  5 jklowden  staff   1024 Oct 10 12:41 tds

> The directory structure is organized by library.  The right place to put
> Win32 stuff is in the library's directory.  Someone working on dblib can
> focus on that directory (and perhaps ../tds), regardless of the OS he's
> interested in.  That's equally good for all parties: if you segregate the
> Win32 sources, you'll likely break them by ignoring them.  

> If you find there's general Win32 stuff you need for all libraries, I'd say
> "replacements" is the right location.  If in any directory you find you need
> a lot of Win32 stuff, it might be a good idea to have a win32 subdirectory
> for it (say, for example, src/dblib/win32).  

> If you plop stuff in a src/win32 directory, you'll soon find a mixture of
> API support in there, not nice for them who follow.  

It may also be useful to have a top-level win32/ directory for general 
build-related stuff, if there turns out to be a lot of that needed.

Steve Langasek
postmodern programmer

Attachment: pgp82hbrvix1x.pgp
Description: PGP signature