Replies: 2 comments
-
hi, |
Beta Was this translation helpful? Give feedback.
-
Sorry for the late reply. I still have difficulties building for iOS target on my M1 mac, so needed help on the side to validate the issue. Here is the project https://github.com/metaphore/mobivm-transient-resource-issue-showcase It declares both dependencies {
...
api "com.crashinvaders.vfx:gdx-vfx-core:$gdxVfxCoreVersion"
api "com.crashinvaders.vfx:gdx-vfx-effects:$gdxVfxEffectsVersion"
} The It seems like only the content of |
Beta Was this translation helpful? Give feedback.
-
Hi @Tom-Ski,
Not sure entirely how to cover this problem in a form of an issue, so I guess this format suits it better.
In short, I have troubles delivering asset files bundled inside the library's JAR to a LibGDX iOS submodule.
The same case is trivial for all other backend submodules. After adding the library's jar as a Gradle dependency, I can simply read the resources with either one of
Gdx.files.runtime()
,Gdx.files.internal()
orGdx.files.classpath()
, because the project's asset files are streamlined into the distribution archive. But it's not the case for MobiVM backend, where only the locally placed and declared inbuild.gradle
/robovm.xml
resource files make it to the output IPA.The question is there anything I can do to automate the asset inclusion for the library end-users, so they don't require any extra iOS configuration steps in order to integrate the library?
Beta Was this translation helpful? Give feedback.
All reactions