From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-20 07:21:57
> > Your Jamfiles would have conditions for all supportest OSes:
> > lib gui : .......... : <os>NT:<define>FOO <os>palmos:<define>BAR ;
> > The only problem I see if that we need to adjust the tools so that they
> > understand the <os> feature.
> The <os> feature is currently builtin and defined to the OS that is
> running (e.g. cygwin, linux, NT). Maybe this could be <target-os>, which
> would allow you to leave <os> as the "host" operating system and
> <target-os> as the os being compiled to.
> E.g. bjam cw-8.3 target-os=mac # os=NT
Why would you want to have host os as property? After all, you can't build
with two host os at the moment. In other words
bjam cw-8.3 host-os=NT host-os=LINUX
makes no sense, so Boost.Build can just detect host os itself and use this
information when needed. And that means "os" can mean "target os".
> One of the motivations for using <gui> as a feature, or a better name
> might be <os-api>, is to allow support for different APIs, e.g.:
> bjam msvc-8.0 os-api=win32
> bjam msvc-8.0 os-api=win64
> bjam gcc-3.3 target-os=linux os-api=x11
> bjam gcc-3.3 target-os=linux os-api=motif
Maybe you're right, if you want to target Qt and gtk, then <os> would be too
> >>SIDE NOTE: When I compile a GUI application (<user-interface>gui) in gcc
> >>using bjam, I get a console window as well as the GUI frame. Is there a
> >>way to remove the console window in this configuration?
> > I don't know. Do you have WinMain as entry point?
> The WinMain entry point is implemented in lib gui. Maybe, if I add an
> extern WinMain to the header included by the application it may work.
I'm afraid I don't have any further ideas. It's being awhile since I wrote any
GUI code for windows.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk