Additions to Project File Structure

Jump to bottom

Nicholas VanCise edited this page Dec 25, 2020 · 7 revisions

Reference Structure

In Depth Summary

.../Mac/build.gradle This file defines and integrates into our system the RoboVM gradle and compiler version we are using, along with defining the ios subproject and its dependencies
.../Mac/ios/build.gradle This file defines an empty robovm configuration, along with our Quorum file dependencies
.../Mac/ios/Info.plist.xml This file is a structured text file containing essential configuration information for a bundled executable, in our case loading these from the robovm.properties file described below
.../Mac/ios/Jars/... This directory contains our compiled Quorum source code, the standard library, and the standard plugins in jar format
.../Mac/ios/natives/liballnatives.a This File is a static archive containing all of our native C/C++/Objective-C code needed to run our application, accessed through JNI. Use nm ./liballnatives.a | less to view method signature contents.
.../Mac/ios/robovm.xml This file contains our compiler configuration for RoboVM. Here we explicitly specify our mainJar containing our main class, our target operating system and architecture, what should be included in the class path, our bundled natives, external resources, weak frameworks to link against, and our plist
.../Mac/ios/robovm.properties This file contains information to populate the plist file with, where this can also be used to populate fields in the robovm.xml
.../Mac/settings.gradle This file makes the ios subdirectory visible to the higher level main gradle build script