Hi Eric,
Friday, August 24, 2007, 4:43:55 PM, you wrote:
> Most likely, for the msvcgen run, you need to specify explicitly the
> build flags needed for wxWidgets rather than relying upon the ones
> discovered by the configure script (which obviously are for Unix
> rather than for Windows). You would need to invoke Jam assignments
> like the following:
> WX.AVAILABLE = yes ;
> WX.DEFINES = wxUSE_GUI=1 WXUSINGDLL=1 ;
> WX.LIBS = wxbase26.lib wxmsw26_core.lib wxmsw26_gl.lib opengl32.lib ;
> Naturally, you want to make those assignments only during the msvcgen
> run, which is possible by wrapping the code in a Jam conditional such
> as:
> if [ Property build : projgen ] = msvc
> {
> ...
> }
It actually adds this stuff to compiler "AdditionalOptions" and I
still don't know how to change this. I was trying to investigate the
problem and I saw that it is happens for cseditor but not for CS itself.
I can't find related differences between cseditor and wxtest jamfiles.
Searching for "if [ Property build : projgen ] = msvc" in CS dir
didn't help.
The "AdditionalOptions" string in CS is empty and in cseditor I saw
the stuff from my linux build.
--
greetings,
Piotr Obrzut mailto:[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[EMAIL PROTECTED]
