-
Notifications
You must be signed in to change notification settings - Fork 135
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
appveyor not testing every build-option #280
Comments
Appveyor has a tendency to disable projects that appear to be "dead" with long running tests (especially if they start failing often). Therefore I would suppose they have a preference for testing each option once. In an ideal world we would have a very large compile farm testing all the different arches with random options. But it's far from an ideal world (for this sort of thing). |
Let's try this a different way: are you ok to:
[note: the PR is unlikely to happen before next week] Is it correct to assume:
|
Seems ok.
Ok.
It just creates libgmp.so and gmp.h instead of libmpir.so and mpir.h, I think, to be compatible with GMP.
I think there is a separate gmpxx.h. There might even be a small libgmpxx.so. I actually forget about this, it's been so long since I looked. One of the main differences is that the tests actually check the C++ tests. |
I wanted to add binaries to the appveyor artifacts and stumbled over this one. We currently have 32/64 + static/shared (2x2), the missing parts are cxx yes/no (x2) and gmpcompat yes/no (x2).
Question: Should I add those to the build matrix as it is currently done (leading to increase of the builds from currently 4 to then 16) or is there a reasonable preference to only check non-cxx and non-gmpcompat once ([currently done in all 4 builds] and enabling those two flags for the current build-matrix = 6 builds in total)?
The text was updated successfully, but these errors were encountered: