-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: libgmp #97
Comments
Repository created, please file a MR. https://github.com/mesonbuild/libgmp Thanks. |
Bumping this because I'd like to help. Would there be any real worth-the-effort benefit to writing a wrap for gmp that does not rely on I'm asking this because I've had a quick look at the current build system for gmp and it's just one obnoxiously large autotools script I'm having a hard time understanding |
Yes, running the autotools script via the external project module may not be possible on Windows without installing a bunch of software (mingw userland providing a shell, coreutils, make, etc.) whereas configuring it natively via meson.build won't require any additional dependencies. That being said, using the external project module is the path of least resistance and almost certainly unblocks your personal work at least on Unix, so that might suffice. |
GMP's configure script is overly complicated for most purposes where only basic functionality of GMP is needed and maximum possible speed might be unimportant. Most of what it is doing is just enumerating every possible CPU architecture. As noted in configure.ac:
The last point is the main one which is that it chooses which assembly routines to use: The meson patch file linked above passes For my purpose I want Probably the vcpkg configuration is a better starting point for figuring out how to write a meson configuration rather than looking at GMP's configure.ac: |
https://gmplib.org
We have a wrap file and meson.build patch for a project that uses GMP in a cross compile on GitLab. It would be preferable if this were in wrapdb (and if it was reviewed by someone who knows what they are doing!). Most of the way it is implemented could be done better.
The text was updated successfully, but these errors were encountered: