-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Build failure OSX #10
Comments
I would recommend you stick with Xcode's clang instead. We don't test with MacPort or HomeBrew installed compilers and we don't really intend to (we don't have the bandwidth unfortunately). It definitely looks like a mismatch between the compiler and the standard libraries (we've seen similar issues on Linux between gcc and clang). What do you get when running
|
I get this:
And the same for saying Is there a way to tell the filament build script to use /usr/bin/clang and /usr/bin/clang++ instead of the one on the PATH? |
You can try to |
Same problem. |
Did you nuke the cmake directory first? (Just checking, I can't think of what else the problem could be) |
You could just remove the tests from libs/utils/CMakeLists.txt in the meantime |
Nope. I will try that... same problem. I will try upgrading to High Sierra, should provide newer clang? |
[BTW thanks for prompt support!] |
Upgrading to High Sierra should definitely fix it. I've compiled Filament myself on 4 different MacPros/MacBook Pros and they all work properly with High Sierra installed. I wish I could help you more but it's hard without a machine that reproduces the issue. |
Its hard even with a machine. I run Linux and Windows 10 Summer as well. C++ has become a real pain. With clang 6, I get linker warnings building my code. Its not my code, its clang's library. Sigh. Also the brew Caveats are a bit confusing.
I cannot add flags to compilation lines at the moment. The compilation lines are hard coded into binaries. Environment variables are fine. I don't know what it means "add the following LDFLAGS". Add what to what? Even the export hint above is wrong. That only finds |
So I have High Sierra now. Installed Xcode tools. Same error.
|
Something's not right, with the latest Xcode and tools you should be on clang-902 (Apple LLVM version 9.1.0). (BTW you can use -c with build.sh to trigger a clean build). Here's the top of my CMake output:
This is with Xcode 9.4.1. |
i did run xcode-select --install .. hmm .. you're right. Its the same compiler. Checking AppStore it tells me I installed version 9.4 of the tools. But, you're right those tools aren't the current ones. Sorry AppStore won't let me copy/paste. Stupid crap. AppStore ALSO tells me there is an update for El Capitan Xcode 8.2. Grrr. |
Ok .. I will try to manually download xcode from the AppStore. Its installing it. Despite telling me I already did install it .. GRRR .. give me Debian any day. |
Ok, after AppStore download of 5+G failed because I ran out of credit and then restarted from scratch (come on, Apple are you morons? FTP could restart downloads 40 years ago), $100 later Xcode installed and filament built! |
I encountered the same build error with clang-3.8 on Ubuntu 16.04. That's the default version you get from You can install a newer version of clang with the command |
- change AssetLoader to allow create asset with cgltf_data - change ResourceLoader to allow passing in decoded image bytes via cgltf_image.extensions, and skip decoding in this case
- change AssetLoader to allow create asset with cgltf_data - change ResourceLoader to allow passing in decoded image bytes via cgltf_image.extensions, and skip decoding in this case
Hi I get this with easy build, I'm using a brew installed clang 6.01 on OSX 10.12.1 (Sierra).
I suspect there's a mismatch between the brew installed compiler and the Xcode supplied libraries. Not sure why clang++ isn't using its own libraries.
(and lots more).
The text was updated successfully, but these errors were encountered: