no .xcodeproj file generated

[meehjeevan]

How do I open the project in xcode for iOS? there's no .xcodeproj file generated.

[rh101]

How do I open the project in xcode for iOS? there's no .xcodeproj file generated.

If you follow this guide, then it should generate the project for you:
https://github.com/axmolengine/axmol/blob/dev/docs/DevSetup.md#ios-tvos-and-macos

If you are getting errors, then include the errors in your post.

[paulocoutinhox]

How do I open the project in xcode for iOS? there's no .xcodeproj file generated.

I have some shortcuts in Makefile that can help you (ios, macos, tvos):
https://github.com/paulocoutinhox/axmol-native-helper/blob/main/Makefile

[meehjeevan]

While trying to run on iOS simulator I got this error:

[meehjeevan]

And sometime these errors too.

[rh101]

Show the step by step process you used to create project, and also list the environment, which OS version, Xcode version, CMake version, etc..

[meehjeevan]

for creating project I've used the same command from the guide.
Android version is working..
for ios version, I ran this command
axmol build -p ios -a x64 -c

build_ios_x64 folder was generated, from there I opened the .xcodeproj file on xcode and tried running on simulator

OS version: 10.15.7
Xcode: 12.4
cmake: 3.29.3

[rh101]

I think the docs are out of date. Try this instead:
(arm64 Sim) axmol build -p ios -a arm64 -sdk simulator -c
or
(x64 Sim) axmol build -p ios -a x64 -sdk simulator -c

[meehjeevan]

same issue with this too...
is it because I'm using an old mac and max version of xcode I can use for now is 12.4.

[meehjeevan]

No, I'm using xcode 15.4. I got it worked in a quite strange way. First I ran the newly generated project on xcode and then I placed class files (.cpp and .h) one by one in the source folder and in cmakelists and hit run. Whichever file it threw error as not found I placed them one by one and kept hitting run then it finally worked. There wasn't really errors in codes. It just didn't work at once with dozens of class files. I don't know how migrated project on ios got it worked for you guys but I got it worked this way.
Funny thing, till now, I was running on simulator. And when I now tried to run on connected device then again same error occurred. Again have to do repeat the same cycle.
BTW, for real device is this command correct?
axmol build -p ios -a arm64 -c
If yes, Should I use same command for release version too?

[rh101]

BTW, for real device is this command correct?
axmol build -p ios -a arm64 -c
If yes, Should I use same command for release version too?

Yes, that's the correct command to generate the project for real devices. The same project is used for any type of build, debug, release, release with debug info etc.. Once you open the project in Xcode, set the type of build in the scheme settings.

[meehjeevan]

Hello everyone,

I’m able to run the app on a connected device, but I encountered the same errors shown in the screenshots when trying to archive it in Xcode.

I tried archiving on an empty, blank project that is generated initially when creating a project using the command, and archiving works there. However, when I replace the source, contents, and CMakeLists.txt with my project’s files, I can run the app on a connected device, but archiving still doesn’t work.
Same errors are shown when I run Analyze on xcode too.
Now, I'm unable to create .ipa file and can't distribute or publish update on app store. What would I do now?

[smilediver]

Do you have .c or .m files in your project? Do they include any Axmol headers? Do you include Axmol headers into prefix/precompiled header? I think you have C or Objective-C files that include Axmol's C++ headers, and hence the compilation errors.

You can use the following method to export and post your build log, or at least find and post the logs for failing commands, that would make it easier to determine the build issues: https://stackoverflow.com/a/30084344/254101.

[meehjeevan]

No, I don't have any .c or .m files created by myself. I figured it out, I have a file which has same name and it conflicted with a file in ios sdk's coreFoudation. Thanks.