From: Alan Gutierrez (alan-jamboost_at_[hidden])
Date: 2004-12-30 13:42:25
I'm not working on Boost.Build this week, sorry. Probably over
the weekend, and when I do, I'll be pursing the following tasks.
~ Create a top level rule.
I need to create a "bundle" rule for OS X. It is basically a
series of mkdir and cp calls.
~ Reference the output of another tope level rule.
I need to find the path to the exe generated so I can copy
it into my "bundle".
If the exe is an a directory:
osx/static/release/gui/tetris (Don't know conventions)
I'd need to create:
Need to figure out how to get that from:
bundle Tetris : src//tetris ;
~ Create a sub project.
I know how to to this now. Clear and clever.
~ Add an output, er, directory level? grist switch? platform directory?
The current Boost.Build system has a concept of a bit of
user-interface (er, grist?) that maps like:
Not going to cut it. I'm looking at Linux/GTK, Linux/X11,
Linux/curses, for example, not Linux/GUI. I need to be able
to generate directories like so:
Win32 for Win32 (Shared with cross compilers)
Win32 Cross-Compile (Same tree, different gcc's)
~ Compile headers out of line.
For debugging development, I want to compile my inline
functions, out-of-line, in an file that contains functions
that are included and compiled inline for release.
~ Specify compile configuration.
I need to be told where to find certian libraries that may
not be in the LD_LIBRARY_PATH, or ddl search path.
The site-config.jam file is the right way to do this. I
probably know how to write one by now.
-- Alan Gutierrez - alan_at_[hidden]
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