fa5500228e
1. Relying on `python3 -m pytest --help` to test for pytest can fail because the pytest packages's __main__ is still invoked; this can trigger import problems and falsely indicate that pytest is missing. A simpler test is to just confirm that pytest is importable. If so, the interpreter returns 0. Otherwise, an ImportError is thrown and the interpreter will return 1. 2. Many templates require a custom do_check just to set PYTHONPATH to either a build directory (especially for compiled extensions) or some subdirectory of the source tree. Setting PYTHONPATH automatically to the build directory should drastically reduce the need for custom do_check in py3 templates. (This only applies to python3-module.sh because pep517 builders will have unpredictable build directories.) Closes: #31354. |
||
|---|---|---|
| .. | ||
| R-cran.sh | ||
| README | ||
| cargo.sh | ||
| cmake.sh | ||
| configure.sh | ||
| fetch.sh | ||
| gem.sh | ||
| gemspec.sh | ||
| gnu-configure.sh | ||
| gnu-makefile.sh | ||
| go.sh | ||
| haskell-stack.sh | ||
| meson.sh | ||
| meta.sh | ||
| perl-ModuleBuild.sh | ||
| perl-module.sh | ||
| python-module.sh | ||
| python2-module.sh | ||
| python3-module.sh | ||
| python3-pep517.sh | ||
| qmake.sh | ||
| raku-dist.sh | ||
| ruby-module.sh | ||
| scons.sh | ||
| slashpackage.sh | ||
| texmf.sh | ||
| void-cross.sh | ||
| waf.sh | ||
| waf3.sh | ||
README
BUILD STYLES ============ These shell snippets provide support for multiple build systems, i.e GNU configure, CMake, etc. A build style file must provide at least the following functions: - do_configure - do_build - do_install If a source package defines its own do_xxx() function, the function defined in the build style file is simply ignored.