-
Notifications
You must be signed in to change notification settings - Fork 418
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 in assimp #37
Comments
Hi there! Could you provide some more details on which Mac you're building on, which version of Xcode you're using, and the build output produced when your build fails? I've been tracking down another assimp related build issue, so you're probably not alone on this one. |
The mac I'm building on is MacBook Pro Mid-2012 version and I'm running on Xcode 9.1
Everything is just warnings apart from the last line. |
Heres a more detailed summary of the error:
|
Hey there, sorry for the delay. Holidays here. 🦃 So it looks like assimp is still broken (for me anyway). You could try either updating to the latest submodules |
Hey I updated the assimp to version 4.0.1 and the previous issue seems resolved but the new issue was that config.h could not be found. The cmake seems to generate the config.h in For the time being, I just copied the config.h file and added it to |
Yeah, I've opened assimp/assimp#1566 and am tracking what I know so far there. Apologies again for the inconvenience. |
@ryantonini @Polytonic I also build project in OSX by Xcode. Try checkout assimp tag v3.1 maybe help workround this issue. Build Success in my machine.
|
@zhangzj I appreciate the pull request -- I'm somewhat hesitant to go back a version though, especially since 3.1 is over a year old, and there's a lot of nice stuff fixed in 4.x.x version. I'll think it over, but for now I'm glad that fixes the problem for you locally! |
@Polytonic OK, no problem. |
I'm having the same problem, any updates on this issue? |
You can disable building the GLTF importer if you don't need support for this format: cd "GlitterFolder"/Build Scroll down and disable the flag ASSIMP_BUILD_GLTF_IMPORTER. I was able to compile on OS X without this feature enabled. |
I can confirm this works. Thanks for the workaround @simonber ! |
Hmm. Seems like there's no movement on the assimp side of things. I'm open to more permanent workarounds at this point. Will probably go with disabling GLTF Importer for now (as outlined above) unless anyone has alternative suggestions. |
Hello there ! I'm working on a rendering engine, and I stole the dependency management of glitter :) (and I'm also following learnopengl.com) I know glitter builds just fine, because somehow you managed to generate the config.h in Can you please give me some pointer ? |
First off, I apologize for the delay. I understand the broken behavior of Glitter led to a poor user experience, and going forward, I'll try to do better about promptly closing out these kinds of issues. Second, while I personally feel the problem is up to For those affected, if it's not too much trouble: would you mind grabbing the above change and trying again? 😬 |
Hello again ! Thanks for you reply :) My request was: "how the hell the submodule + cmake approach is working on Glitter, but not on my personal project when I try to replicate it ?" (and that question remains without answer). The good news with you workaround is:
So thank you ! |
Hm, without more detail, I'm not sure I can provide much information. Perhaps you need to clone submodules or make sure your paths line up? Those are usually the most frequent user errors I've encountered. I can't really help much more beyond that though. |
The original issue was resolved in assimp #2047. This reverts commit 73275f5.
When I build the project for the first time on Xcode on OSX, I get an error in the glTFExporter.cpp file from assimp. The error occurs on line 585 and reads: Ordered comparison between pointer and zero ('aiVector3D *' (aka 'aiVector3t *') and 'int')
If anyone could help, I would appreciate it.
The text was updated successfully, but these errors were encountered: