I have everything in C:/utah, which mimics the Linux/Unix "/" or root 
directory.

So I have:

c:/utah/usr
c:/utah/opt
c:/utah/home

And I have:

c:/utah/usr/mingw
c:/utah/usr/msys

Inside mingw and msys, everything is default from the installers or zip 
files.

I have in /utah/usr/msys/1.0/local the usual Linux/Unix local stuff, i.e. 
bin, docs, include, info, lib. This is where the stuff I build gets 
installed, including third-party dependencies (mostly).

Other third-party stuff goes into c:/utah/opt, just as in a standard 
Linux/Unix filesystem.

I also install Csound 5, once it builds, into c:/utah/opt/csound to test the 
Windows installer.

It is sometimes necessary to use completely qualified pathnames in custom.py 
because gcc doesn't pick up /usr/local/include, etc., without that. I have 
attached my custom.py.

I do everything from inside the MSYS shell (bash shell). This causes a 
problem with the scons script which is not found, so I have created shell 
scripts to invoke scons. I have attached one of these as well.

Note: I only ever build the double-precision version of things.

I hope you don't mind, I'm copying my response to the csound-devel list.

Hope this helps,
Mike


----- Original Message ----- 
From: "James Hearon" 
To: 
Sent: Tuesday, October 25, 2005 10:27 PM
Subject: msys


>
>
> Hi Michael,
> Stil struggling with libsndfile on build.  Wondering if you'd mind sharing 
> how you have your msys and build srcs set up?  For ex. I have 1.0 (msys) 
> folder with local/lib inside that, BUT OUTSIDE 1.0 I have separate folders 
> for the srcs fltk, libsndfile, portaudio, swig, MinGW etc.  Seems like you 
> were installing everything inside the msys folder.  So I'm guessing you 
> have something like /usr/local/lib/libsndfile, then.  Is that right?  Do 
> you also have /usr/local/lib/MinGW too?
>
> Thanks,
> Jim Hearon
>
>
>