-
Notifications
You must be signed in to change notification settings - Fork 107
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
Latest version of Xcode broke Corrade #52
Comments
However, upgrading to latest version of CMake seems to resolve the issue. Upgraded cmake 3.11.4 -> 3.12.2 and that seems to have resolved the issue. Looks like it was something wonky with Xcode, not sure what caused the issue, but FYI. |
Maybe put a check in if Xcode build, minimum cmake required is 3.12.2. Might work on older versions, not sure, but 3.12.2 fixed the issue for me. |
Hi, thanks for the report! 👍 Would you have a chance to test if this is a problem just specific to Corrade? I have no way to test this myself, but to me it looks like it's a general issue where older CMake won't work with latest Xcode -- not being specific to Corrade -- especially the weird If it's really a general issue, I don't think putting a Xcode-specific warning / error there is a good idea (all CMake-based projects would have to do that, then). If it's caused by something specific to Corrade, then yes, I'm all for it. |
As far as I can tell, this issue was specific to Corrade. I've tested the old version of CMake with newer Xcode and all the other projects built fine. Furthermore, it is specific to older CMake, and only Xcode build. The older CMake built the Corrade project just fine when I told it to make an Eclipse project. The extent of my troubleshooting was:
I don't really have a way of re-testing it with new Xcode and older CMake because I upgraded CMake, and I'm under a lot of pressure to get this thing I'm working on working. But in any case, as far as I can tell, for me, the problem was specific to the combination of (Corrade, older CMake, new Xcode). |
Also, with the new version of CMake, it never tries to make the
|
I totally understand that ;) My case right now as well. Thus thank you a lot for taking the extra time to report this. I bet this is due to my use of So my final question: what's your Xcode version? Or even better, what does CMake report as detected compiler version? Should be something like |
I've dumped some CMake vars, here they are. I think it's probably sufficient to check for
|
Managed to track this down to https://gitlab.kitware.com/cmake/cmake/issues/18099 (so CMake 3.12.0 has the fix already, it seems). Since a14b1ae I am failing early with an error, suggesting users to upgrade. If you would have a chance to verify it works as intended, I would be happy :) |
Hey, looks like the newest version of Xcode broke Corrade. Seems to build OK with Eclipse, but Xcode build fails.
I'm just starting to look into it, but here's what I get
The text was updated successfully, but these errors were encountered: