I changed SConstruct to make it possible to build both with MSVC and with MinGW on Windows.

There is a new SConstruct command-line option, "withMSVC", which defaults to 0.

If you set "withMSVC=1", the Microsoft Visual C++ compiler is used, and the "custom-msvc.py" file is loaded for additional options.

If you set "withMSVC=0" (the default), the MinGW compiler is used, and the "custom.py" file is loaded for additional options.

I solved the circular reference problem caused by needing to load options before examining options. The solution is to update the common environment with command-line options only first, then examine the value of withMSVC, then update the common environment with custom.py or custom-msvc.py depending on the value of withMSVC.

I tested this solution and verified that changing the value of withMSVC on the command line does indeed cause the correct custom file to be loaded.

Regards,
Mike



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net