How should I start with IOS?

TooMuchJava · February 15, 2019, 2:48am

How do you integrate java and objective-c/swift?
From this page I can see how to build it, but the integration is a mystery to me.
https://wiki.jmonkeyengine.org/jme3/ios.html

Also, does anybody have any general tips about it?

Edit: also, how do I figure out if I am running on iOS from java? For Android I use System.getProperty(“java.runtime.name”).toLowerCase().equals(“android runtime”), but how can I check if it is running on iOS?

sgold · February 15, 2019, 6:18am

System.getProperty("os.name") should provide a clue what you’re running on. For details see:
https://www.mkyong.com/java/how-to-detect-os-in-java-systemgetpropertyosname/

Sorry, I don’t have any tips on integration.

Darkchaos · February 15, 2019, 11:12am

Use the SDK and start a new iOS Project (Or was it only enabling iOS under Deployment settings?) Either way it generates an xCode Project to use later on. You just code in java and don’t care about the iOS side. Be aware that you need Mac OS.

jayfella · February 15, 2019, 12:43pm

There’s a built in Enum for finding the platform. I think it’s JmeSystem.getPlatform() or something like that.

Edit: Yup.

github.com

jMonkeyEngine/jmonkeyengine/blob/master/jme3-core/src/main/java/com/jme3/system/JmeSystem.java#L153


    checkDelegate();
    return systemDelegate.newAssetManager();
}

public static boolean showSettingsDialog(AppSettings sourceSettings, final boolean loadFromRegistry) {
    checkDelegate();
    return systemDelegate.showSettingsDialog(sourceSettings, loadFromRegistry);
}

public static Platform getPlatform() {
    checkDelegate();
    return systemDelegate.getPlatform();
}

public static JmeContext newContext(AppSettings settings, JmeContext.Type contextType) {
    checkDelegate();
    return systemDelegate.newContext(settings, contextType);
}

public static AudioRenderer newAudioRenderer(AppSettings settings) {
    checkDelegate();

github.com

jMonkeyEngine/jmonkeyengine/blob/master/jme3-core/src/main/java/com/jme3/system/Platform.java

/*
 * Copyright (c) 2009-2019 jMonkeyEngine
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions are
 * met:
 *
 * * Redistributions of source code must retain the above copyright
 *   notice, this list of conditions and the following disclaimer.
 *
 * * Redistributions in binary form must reproduce the above copyright
 *   notice, this list of conditions and the following disclaimer in the
 *   documentation and/or other materials provided with the distribution.
 *
 * * Neither the name of 'jMonkeyEngine' nor the names of its contributors
 *   may be used to endorse or promote products derived from this software
 *   without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

This file has been truncated. show original

TooMuchJava · February 26, 2019, 11:56pm

The IOS sdk menu is empty in a MacOS Mojave emulator with XCode and sdk 3.2

thetoucher · February 27, 2019, 12:11am

I wouldn’t.

I’ve done some iOS work and would only tackle it again natively or using something like Unity that does all the work for me.

Not a very pro-active answer sorry, but it needs to be mentioned.

TooMuchJava · February 27, 2019, 12:12am

“I wouldn’t”

I’m sorry, but not a very descriptive answer…

Are you referring to using ios and JME together?

thetoucher · February 27, 2019, 12:22am

yep. The task appears to be a massive pain in the arse to me, I personally wouldn’t want to travel down that rocky road less travelled.

Just trying to save you huge headaches down the road. But by all means don’t let my pessimism stop you from doing it, I’m very often, if not always, wrong =)

TooMuchJava · February 27, 2019, 12:24am

I’m prepared to deal with some issues… Not surprisingly, the android version works just fine, but I’m guessing this will be harder to integrate.

thetoucher · February 27, 2019, 12:25am

good stuff =) I hope iOS works out smoothly so I/we can use it more.

TooMuchJava · February 27, 2019, 12:29am

It might be because i dont seem to have the cmd line developer tools

TooMuchJava · February 28, 2019, 4:11am

Followed this guide:

I got as far as linking.
I keep getting this error:

LD: -filelist file '../../build/iOS-arm64/libs.list' could not be opened errno=2 (no such file or directory)

Clang: error: linker command failed with exit code 1 (use -v to see invocation)

thetoucher · February 28, 2019, 5:42am

mmmkay, so where is the file ?

GTWhite · February 28, 2019, 5:07pm

It looks like you need to switch on IOS in the Jmoneyengine SDK then compile in the SDK first.

It should build the IOS natives and project file for you. My guide assumes you have already got to that point. My guide was from the point where you are starting with XCODE.

Have you enabled IOS and allowed it download Avian and then build the natives?

TooMuchJava · March 1, 2019, 12:49am

I think so, i did a clean-and-build, then enabled IOS deployment. Then I waited for the saving project properties dialog to go away, and opened XCODE. Lastly, I followed your steps until the linker bit.

GTWhite · March 1, 2019, 9:40am

Are you building on OSX?

If so, if I remember correctly folder names are case sensitive. I notice you have got upper case in the folder name iOS-arm64/libs.txt

Does this folder exist and have you got the case correct?

GTWhite · March 2, 2019, 9:53am

Are you getting these messages when building in the SDK? Especially the last message???

If so, then check if the ios-arm64, ios-arm and ios-x86_64 folders exist in the build folder?
If so, then build in the XCODE project. Note: DO NOT use CLEAN in XCODE or it will delete these folders. Only use BUILD.

build-ios:
init:
…
…
Packaging iOS classpath and resources
…
…
Creating iOS resources object file for arm
Creating iOS bootimage and codeimage for arm
…
…
Compiling native code for arm
…
…
Expanding libavian.a for arm
…
…
Create library list for arm
build-ios-arm:
init:
…
…
Creating iOS resources object file for arm64
Creating iOS bootimage and codeimage for arm64
…
…
Compiling native code for arm64
…
…
Expanding libavian.a for arm64
…
…
Create library list for arm64
build-ios-arm64:
init:
…
…
Creating iOS resources object file for x86_64
Creating iOS bootimage and codeimage for x86_64
…
…
Compiling native code for x86_64
…
…
Expanding libavian.a for x86_64
…
…
Create library list for x86_64
build-ios-x86_64:

The needed native iOS libraries have been built, open the XCode project at ios/project to run the application on iOS.

Darkchaos · March 2, 2019, 6:13pm

Wiithout looking into it: ProGuard obfuscates classes, maybe that’s part of the problem

TooMuchJava · March 2, 2019, 6:20pm

is there a flag to disable proguard like there is in android? (yea, I had to use that…)

GTWhite · March 3, 2019, 12:31pm

which library jars are including in your app?