Improved build system generator for CPython C/C++/Fortran/Cython extensions

Edit Package python-scikit-build

Improved build system generator for CPython C/C++/Fortran/Cython extensions.

Better support is available for additional compilers, build systems, cross compilation, and locating dependencies and determining their build requirements.

The scikit-build package is fundamentally just glue between the setuptools Python module and CMake.

Refresh
Refresh
Source Files
Filename Size Changed
python-scikit-build.changes 0000007985 7.8 KB
python-scikit-build.spec 0000003549 3.47 KB
sample-setup.cfg 0000000085 85 Bytes
scikit-build-0.13.0.tar.gz 0000153612 150 KB
Revision 13 (latest revision is 45)
Benjamin Greiner's avatar Benjamin Greiner (bnavigator) accepted request 951777 from Benjamin Greiner's avatar Benjamin Greiner (bnavigator) (revision 13)
- Update to 0.13.0
  * If you are using scikit-build via pyproject.toml, please
    remember to include setuptools and wheel. A future version of
    scikit-build may remove the setuptools install-time hard
    requirement.
  * CMake module /cmake-modules/Cython now uses Cython default
    arguments. This no longer adds --no-docstrings in Release and
    MinSizeRel builds, so Cython docstrings are now retained by
    default. Additionally, --embed-positions is no longer added to
    Debug and RelWithDebInfo builds. Users can enable these and
    other Cython arguments via the option CYTHON_FLAGS. See #518
    and #519, thanks to @bdice for the improvement.
  * Experimental support for ARM64 on Windows. Thanks to
    @gaborkertesz-linaro in #612.
  * Support for MSVC 2022. Thanks to @tttapa for the contribution
    in #627.
  * Support the modern form of target_link_libraries, via
    SKBUILD_LINK_LIBRARIES_KEYWORD (somewhat experimental). Thanks
    to @maxbachmann in #611.
  * Update the Ninja path if using the ninja package. This fixes
    repeated isolated builds. Further path inspection and updates
    for isolated builds may be considered in the future. #631,
    thanks to @RUrlus and @segevfiner for help in tracking this
    down.
  * Allow OpenBSD to pass the platform check (untested). See #586.
  * Avoid forcing the min macOS version. Behaviour is now inline
    with setuptools. Users should set MACOSX_DEPLOYMENT_TARGET when
    building (automatic with cibuildwheel), otherwise you will get
    the same value Python was compiled with. Note: This may seem
    like a regression for PyPy until the next release (7.3.8),
Comments 0
openSUSE Build Service is sponsored by