-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[gmp] 6.3.0 Build on Windows could be great if it could identify patch levels #43460
Comments
You can see the specific version number through the vcpkg command:
|
@Mengna-Li The following is an example of execution in my environment, but you can certainly see that it is
But if I use a previous version in another directory, I don't know what version it is (Version 6.3.0#2 should not have been released on 09/22/2024.).
|
You can use the |
@Mengna-Li It is my understanding that in your opinion the
|
Is your feature request related to a problem? Please describe.
Thanks for providing the vcpkg.
Currently,
gmp
version isv6.3.0
.If I just use the library, I don't know if it is
#0
,#1
or#2
.v6.3.0#2
includes #42443 .It is no longer easy to distinguish whether a library is built with cl.exe or with gcc.exe or others.
Proposed solution
Define something like
__GNU_MP_VCPKG_VERSION_PATCH_LEVEL
in gmp.h.Describe alternatives you've considered
No response
Additional context
As stated in the INSTALL file of MPFR 4.2.1, if the MPFR-formatted output functions based on ISO-conforming printf() are to be used in gcc.exe,
gmp
may be compiled withCC="gcc -D__USE_MINGW_ANSI_STDIO"
.If a module provided in an LL language such as Perl deals with its
gmp
, it may fail in the test case of its output functions if it is not known which one the library was compiled with.The text was updated successfully, but these errors were encountered: