From: Mat M. <mm...@ad...> - 2008-04-12 05:42:27
|
I spent a little time rummaging around in the boost build manual for this, but didn't find an easy change to make this possible. As a semi-manual approach, you could try: Change the value of the variable $(TOP) in adobe_source_libraries/project-root.jam and in adobe_platform_libraries/project_root.jam to a directory to which you'd like built_artifacts to be a peer. Also, when building, you can invoke bjam with --build-directory=/some/path to alter the location of the boost artifacts. I don't have more cycles to spend on the build system for a while, but if you can figure out a way toset things up so that --build-directory also affects the ASL artifact location, while keeping the default location where it is now, I'd be happy to update ASL accordingly. - Mat "Jacob Foshee" <ja...@gm...> writes: > Great, yes, that did the trick! > > So, my next step is to incorporate this into our build. In general we try to keep build artifacts out of the source tree. Is there a way to > specify a different destination for built_artifacts? If not, I can make do w/out it, but might I make this a feature request? |