Skip to content
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

iOS port build_ios.sh and *.cmake files are not compatible #84

Closed
unphased opened this issue Aug 31, 2013 · 5 comments
Closed

iOS port build_ios.sh and *.cmake files are not compatible #84

unphased opened this issue Aug 31, 2013 · 5 comments
Labels
Build Global flag to mark build relates topics
Milestone

Comments

@unphased
Copy link

For whatever reason my dev tools live under /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer, not /Developer/....

There are several hard-coded locations that cause this to fail.

Furthermore, there are sections of the script that assume that it is being run from port/iOS and the makefile assumes that it is running from the root directory (complete with hardcoded paths beginning with port/iOS) which also ensures that it will never succeed.

I've since given up on this script and have had success with the Xcode3 project in the workspace directory. Appreciate that being there.

@sherief
Copy link
Contributor

sherief commented Sep 8, 2013

Is there interest in including an Xcode file for OS X / iOS builds in the repository? I use an Xcode file to build assimp for my OS X projects and creating an iOS target using that won't be hard. If the maintainers are OK with it I can push those.

@unphased
Copy link
Author

unphased commented Sep 8, 2013

An up to date xcodeproject would be much appreciated. I am currently unable to get assimp building for iOS without using the boost dependency (which I have to use another 200MB framework I found somewhere).

@sherief
Copy link
Contributor

sherief commented Sep 8, 2013

Hmmm, I'm only deploying for OS X so far and my project already links to boost so the cost of that dependency isn't visible in my case, though I can understand how it can be costly on iOS devices. I'll take a look into it. Is using Boost on iOS completely out of the question?

@unphased
Copy link
Author

unphased commented Sep 8, 2013

No, I wouldn't say so, the boost framework I grabbed worked without any hitches so it is still a minimal amount of configuration involved in making assimp to build for iOS now that I have been able to succeed at it. So I wouldn't say this is hugely important. I just saw that since there was clearly an effort being made to work around requiring boost it would probably be nice if that worked.

@sherief
Copy link
Contributor

sherief commented Sep 8, 2013

Well I don't know about Boost-free builds but I'll try to get an iOS Xcode project up and running, at least in another branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Global flag to mark build relates topics
Projects
None yet
Development

No branches or pull requests

2 participants