-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
Conflicts: .gitignore
Still seems to reference a global gyp? I'm getting
|
a37f65a fixes path |
This works for me; builds makefiles just fine. Can we get an Xcode project for the OS X app too? I'm using the built-in debugger interface in Xcode. |
Ah sorry, there's |
Nice catch on the path fix. Yes, |
For the most part, this is looking great from an iOS / Xcode point of view. Comments:
|
Can you help me replicate, or share the errors?
We should support both platforms. The way to do this best is the question. I'm positive they can coexist. So, we either need to get the
The include paths to the header files should be showing up. Sounds like that is not enough? You need the actual listing of files to be somehow stored in the xcode project? I'm not aware if gyp can/will auto-build xcode projects like this - needs some research.
Yes, include paths should be there automatically in the generated project. If not its a bug. |
The supported platforms looked weird -- these should not be in the same target. That is, the end Xcode project should have two targets in the top-left pulldown -- one for OS X and one for iOS, each supporting the respective platform. I will see if I can get GYP to do this.
I think solving the above can result in an Xcode project with two targets, one for each platform. As for the
Yes, we need the files in Xcode. This is for code completion, type checking, easy header reading in the IDE, etc. |
This should be working now - take a look a let me know if we are closer. Do |
Looking better. More notes.
|
all done, closing this, merge of clean/rebased branch at #28 |
Moves the build to gyp instead of cmake. gyp has excellent support for building XCode projects and passing options down for specific settings.
Closes #18
Before merging: