Migrate to meson build system with PPL 1.2

[cxzhong]

Replace the setuptools/distutils build with Meson:

• Add meson.build for the root project, ppl/ package, and tests/
• Add pyproject.toml with meson-python backend
• Remove setup.py, setup.cfg, and tests/setup*.py

Use Meson wrap to fetch PPL 1.2 source on demand instead of bundling:

• Add subprojects/ppl-1.2.wrap downloading from sagemath/sage releases
• Add subprojects/packagefiles/ppl-1.2/meson.build as build overlay
• Add compiler-fixes patch for C++17 compatibility (std::iterator,
  std::auto_ptr, std::mem_fun_ref, memcpy casts, missing includes)
• Generate ppl-config.h at configure time without template file
• Prefer system PPL via ppl-config script, fall back to subproject

Update CI workflows:

• Add wheel builds for ubuntu, macOS ARM, macOS Intel, and linux-arm
• Build GMP and GLPK from source for manylinux wheel portability
• Add free-threading (cp314t) and musllinux support
• Add macOS-15-intel runner to dist.yml matrix
• Update pyproject.toml license to GPL-3.0-only
• Pin cibuildwheel to v3.3.1, upgrade CI actions to v6
• Fixes Use meson-python to build #33

[dimpase]

This should not bundle ppl unconditionally. ppl is relatively popular library and is available on many systems.

While ppl does not provide pkg-config configuration, it installs a script called ppl-config, which does things like ppl-config --cxxflags, etc

That is, to get the correct CXXFLAGS (important for C++ compatibility), one can just get them by calling ppl-config --cxxflags. Same for linking (call ppl-config --ldflags)

[cxzhong]

This should not bundle ppl unconditionally. ppl is relatively popular library and is available on many systems.

While ppl does not provide pkg-config configuration, it installs a script called ppl-config, which does things like ppl-config --cxxflags, etc

That is, to get the correct CXXFLAGS (important for C++ compatibility), one can just get them by calling ppl-config --cxxflags. Same for linking (call ppl-config --ldflags)

Since the traditional wheel build also pack ppl and others into wheel.

[dimpase]

one does not need to build a dylib from source in order to pack it into a wheel.
pplpy is packaged by Arch, Gentoo, and they certainly will object
to this kind of design

[cxzhong]

one does not need to build a dylib from source in order to pack it into a wheel.
pplpy is packaged by Arch, Gentoo, and they certainly will object
to this kind of design

OK, Then I try to find ppl. If do not find then use subproject. but for wheel build. I think it is better to build everything static.

[dimpase]

I don't see how it's better. If you have a dylib on your system, you want to reuse it
(ppl also has gmp as a dependency, so it's basically bloating
things up for no reason)

[cxzhong]

I don't see how it's better. If you have a dylib on your system, you want to reuse it
(ppl also has gmp as a dependency, so it's basically bloating
things up for no reason)

because it will let user just pip install pplpy, then the user can run this without install some system packages

[cxzhong]

Now, if you install libppl-dev and ppl-dev. it can build from system's ppl. If not, it will run a subproject.

[dimpase]

I don't see how it's better. If you have a dylib on your system, you want to reuse it
(ppl also has gmp as a dependency, so it's basically bloating
things up for no reason)

because it will let user just pip install pplpy, then the user can run this without install some system packages

there is a number of reasons why it's less preferable: @orlitzky has a good answer I am sure

[tobiasdiez]

A good compromise is to try to detect ppl and if not available use it from a subproject. But pls don't include the source files directly, but use a wrap (eg https://github.com/dimpase/primecountpy/blob/master/subprojects/primecount.wrap): https://mesonbuild.com/Wrap-dependency-system-manual.html

[orlitzky]

There is a good list at https://wiki.gentoo.org/wiki/Why_not_bundle_dependencies but even that is missing some things like needing to duplicate patches to fix the build with newer compilers, and the ways various licenses change when you are copy/pasting code rather than linking.

And who wants to install pplpy if they don't have PPL first?

[dimpase]

A good compromise is to try to detect ppl and if not available use it from a subproject. But pls don't include the source files directly, but use a wrap

yeah, vendoring the sources of ppl is totally unnecessary - I haven't looked at the implementation details yet.

[tobiasdiez]

And who wants to install pplpy if they don't have PPL first?

Well, from a user's perspective installing a binary wheel of pplpy that includes PPL is definitively more friendly than having to install PPL first manually, and then building pplpy from source.

[tobiasdiez]

Thanks. This looks prettyy good to me. A few smaller suggestions/nit-picks from my side.

[cxzhong]

@dimpase @tobiasdiez can you review this again?

[tobiasdiez]

Just a few minor suggestions

[cxzhong]

Thanks, I will try to apply this.

[cxzhong]

It is very hard to debug here

[cxzhong]

It is very hard to debug here

I can not let cibuildwheel linux subproject ppl to find subproject gmp. but macos is ok. it seems a bug in meson build system

[tobiasdiez]

I think you just forgot to specify them as dependencies of the subproject: https://github.com/sagemath/sage/blob/e37154cba140e8fc6ba3220c558cd3e8ada228ad/subprojects/packagefiles/maxima/meson.build#L31

[cxzhong]

I think you just forgot to specify them as dependencies of the subproject: https://github.com/sagemath/sage/blob/e37154cba140e8fc6ba3220c558cd3e8ada228ad/subprojects/packagefiles/maxima/meson.build#L31

still can not find gmp in cibuildwheel. I ran locally in Ubuntu. But in macos, it can be built.

[cxzhong]

Then we need to bump the version to 0.9.0

[tobiasdiez]

LGTM. Thanks again!

Follow-ups would be:

• Migrate to uv (instead of pip install)
• Figure out how to include gmp etc as subprojects instead of manually installing them from source

[cxzhong]

LGTM. Thanks again!

Follow-ups would be:

• Migrate to uv (instead of pip install)
• Figure out how to include gmp etc as subprojects instead of manually installing them from source

We may do this in follow-up pr

[cxzhong]

This is ready to merge now @dimpase