|
Boost-Build : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-04-18 05:09:39
Consider:
use-project boost
: ../../.. ;
project my-project
: requirements <library>/boost/python//boost_python ;
# Declare a python extension
python-extension ext : ext.cpp ;
# Declare a python embedding application that expects to load ext
exe embed : embed.cpp ext /python//python ;
# test that application
run embed ;
The above doesn't work because in order to run embed, one needs the
PYTHONPATH environment variable set so that it includes the directory
into which the "ext" target is generated.
It would be nice to be able to do things like that without intruding
into the handlers for EXE targets and the "run" testing rule. Today,
AFAIK, there's no way to communicate the need to set environment
variables (or run commands) when an executable uses a library or
python extension.
Thoughts?
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com
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