I have made only one change so far to SConstruct, and that is to use a 
custom=xxx.py option for scons. Of course I will try to preserve the MinGW 
build (I will put back the older tools to make sure).

All my other changes so far are to the custom options files. There are now 2 
for MSVC builds:

custom-msvc-debug.py
custom-msvc-release.py

I have changed the organization of third-party libraries. Essentially all 
third-party dependencies are in a "U:\" drive which is mapped to a real 
drive on my PC. Developers could similarly map a "U:" drive on their PCs and 
be able to use the new custom files in Csound CVS without editing them.

Once I figured out why MSVC wasn't running from SCons (you need the whole 
Environ(ENV=os.environ), not just Environ(PATH=os.environ['PATH']), it 
started going pretty fast.

More and more open source projects come with MSVC solutions that actually 
build, so I guess this is a trend.

I am using MSVC 2005 free edition with Platform SDK 2006, but the latest 
stable versions of everything else (including SCons).

I'm kind of excited by this. I think it will be an improvement -- if I can 
get it to go all the way.

Regards,
Mike

----- Original Message ----- 
From: "victor" 
To: "Developer discussions" 
Sent: Saturday, February 09, 2008 4:54 PM
Subject: Re: [Cs-dev] Trying Microsoft Visual Studio


> That's good. Please make sure this does not break the mingw build,
> as I rely on that to build my Windows executables. You can use
> the already existing MSVC definitions in SConstruct for that.
>
> Victor
> ----- Original Message ----- 
> From: "Michael Gogins" 
> To: "Developer discussions" 
> Sent: Saturday, February 09, 2008 9:27 PM
> Subject: [Cs-dev] Trying Microsoft Visual Studio
>
>
>> Regarding building the next version of Csound for Windows, I have decided
>> to
>> attempt to continue to use the existing SConstruct, but get it to work
>> with
>> the free edition of the Microsoft Visual C++ compiler.
>>
>> This may introduce a delay or other complications, but I feel it is the
>> best
>> way forward. The best thing about this, if it works, will be that I can
>> easily debug Csound with the excellent Microsoft debugger (the GNU
>> debugger
>> on Windows is very hard to use and frequently just crashes).
>>
>> I am now involved in satisfying all of the various dependencies
>> (libsndfile,
>> PortAudio, portmidi done so far; then FLTK, etc., etc...).
>>
>> I will keep the list posted with progress and any questions or problems I
>> run into.
>>
>> Regards,
>> Mike
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net