fc7b01e694
As a regression / misbehaviour compared to waf 2.0 when a Python
module is installed it seems that, even tho `PREFIX` is set for the whole
project, it is ignored.
In the past this was not ignored, namely:
```
(pydir,) = conf.get_python_variables(["get_python_lib(standard_lib=0, prefix=%r) or ''" % conf.env.PREFIX])
```
While with the current version we would always get (if not forced
with specific `PYTHONDIR` and `PYTHONARCHDIR`) the hardcoded path defined
at compilation time (`/usr/local/lib` in all cases I saw)
This patch takes this into account, using the user schema that permits to
customize the output passing the userbase variable, which is set to `PREFIX`
value indeed.
sysconfig.get_preferred_scheme('user') could give us the user schema, but
this is Python >= 3.10 only, so instead we construct the name manually
depending on the OS.
|
||
|---|---|---|
| .pipelines | ||
| build_system_kit | ||
| demos | ||
| docs | ||
| playground | ||
| tests | ||
| utils | ||
| waflib | ||
| zip | ||
| .gitignore | ||
| ChangeLog | ||
| configure | ||
| DEVEL | ||
| LICENSE | ||
| README.md | ||
| TODO | ||
| waf-light | ||
| wscript | ||
ABOUT WAF
Waf is a Python-based framework for configuring, compiling and installing applications. Here are perhaps the most important features of Waf:
- Automatic build order: the build order is computed from input and output files, among others
- Automatic dependencies: tasks to execute are detected by hashing files and commands
- Performance: tasks are executed in parallel automatically, the startup time is meant to be fast (separation between configuration and build)
- Flexibility: new commands and tasks can be added very easily through subclassing, bottlenecks for specific builds can be eliminated through dynamic method replacement
- Extensibility: though many programming languages and compilers are already supported by default, many others are available as extensions
- IDE support: Eclipse, Visual Studio and Xcode project generators (
waflib/extras/) - Documentation: the application is based on a robust model documented in The Waf Book and in the API docs
- Python compatibility: cPython 2.7 to 3.x, Jython 2.7 and PyPy
Learn more about Waf by reading The Waf Book. For researchers and build system writers, Waf also provides a framework and examples for creating custom build systems and package distribution systems.
Download the project from our page on waf.io, consult the manual, the API documentation and the showcases and experiments.
HOW TO CREATE THE WAF SCRIPT
python ./waf-light configure build
CUSTOMIZATION
The Waf tools in waflib/extras are not added to the waf script. To add some of them, use the --tools switch. An absolute path can be passed if the module does not exist under the 'extras' folder:
./waf-light --tools=swig
To customize the initialization, pass the parameter 'prelude'. Here is for example how to create a waf file using the compat15 module:
./waf-light --tools=compat15 --prelude=$'\tfrom waflib.extras import compat15\n'
Although any kind of initialization is possible, using the build system kit may be easier (folder build_system_kit):
./waf-light --make-waf --tools=compat15,/comp/waf/aba.py --prelude=$'\tfrom waflib.extras import compat15\n\tprint("ok")'
To avoid regenerating the waf file all the time, just set the WAFDIR environment variable to the directory containing "waflib".
HOW TO RUN THE EXAMPLES
Try this:
cp waf demos/c/
cd demos/c/
./waf configure build