-
Notifications
You must be signed in to change notification settings - Fork 11
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
OS X compilation issue #12
Comments
the cmake setup is probably incorrect, and there's 3rd party files just chucked in with the PCS2 code. i.e. GLee is 3rd party & should be moved to Or maybe it should be changed to be more like fso; and move all 3rd party stuff into |
Maybe @asarium can offer some suggestions on fixing the cmake config? |
Yeah if that's the way to get per-project compilation options it probably needs to be done. I think older compilers were more lax about this, older LLVM apparently treated it as a warning. Now it's a halting error. |
ah yes, g++ on 'buntu 16.04 is still treating it as a warning so I didn't worry too much about it before... |
Benklop's got a fix for it - we're just testing it and if we can get it to work he'll submit the fix. |
C++11 is supposed to be handled by the CMake function |
@countbuggula any news on the fix being tested by Benklop? |
Since FreeBSD is using a new clang version as well, this is also blocking PCS2 from compiling there. Any word on a solution to getting our third party libs from using the same defines as our C++ code? |
@countbuggula ping :) |
Bueller? |
Well, I changed jobs and no longer have Mac so I need to check with benklop
and see what he has. Thanks for the reminder.
…On Sat, Jun 3, 2017, 9:47 AM Cliff Gordon ***@***.***> wrote:
Bueller?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjTNmMTpBK7XojNBMHewse78eWsUFnvks5sAYAPgaJpZM4LF_TU>
.
|
After looking into this, it actually seemed to have come from fmt's own CMake config file. fmt avoids setting the CPP11_FLAG argument if a CXX standard is defined within CMake already, so I tested defining one on the command line and that caused this error to stop. A solution therefore might be to permanently define the C++11 standard within our main CMake files and the fmt one should avoid setting it in a way that conflicts with C files. |
I think this has been done. Can this be closed? |
I haven't tried compiling PCS2 in ages so I can't confirm or deny this is still an issue. I can try it again on my Macbook and see if something similar is still happening. But if we see an actual change has been made to the repo to account for this since it was filed, then we can go ahead and close it out and I'll file a new or reopen this if I run into any issues next time I try compiling it. |
I don't actually know for sure whether the change has been made. I thought it had been, but I don't have a Mac to check. |
I'm following up with Benklop again to see if he remembers submitting any changes. |
I was thinking more like just looking at the PR history, would myself but lazy since I keep replying to this thread when I'm on my phone |
From Benklop: |
I do have a mac now too, just a different one. I can try and confirm this issue or its resolution some time this week. |
Still getting:
|
Looks like we may need to only use the c++11 standard definition with .cpp files? I tried with an older minimum Mac OS X version but it still uses the most recent framework available so not much else I can do I don't think. Are we currently applying CXXFLAGS to CFLAGS, or the equivalent, with this CMake setup?
The text was updated successfully, but these errors were encountered: