Menu

Gradle

Gradle is the build system for Kotlin, and is the equivalent of SwiftPM for Swift development. When Skip transpiles your project, it converts your Swift code into Kotlin, and it also converts your Package.swift file into a build.gradle.kts file in the transpiler plugin’s output directory. This conversion happens transitively on all your project’s Skip-enabled dependencies, including the core SkipStack modules. This results in a local inter-connected network of Gradle projects containing the entirety of your project’s source dependency tree.

The following sections detail Skip’s use of Gradle, including how to build with Gradle from the command line.

Skip App Projects

Consider a minimal Swift app project created by the commands:

skip init command output

% brew install skiptools/skip/skip
% skip init --show-tree --no-build --no-test --no-module-tests --free --icon-color '' --appid=skip.hello.App --version 1.0.0 hello-skip HelloSkip

.
β”œβ”€ Android
β”‚  β”œβ”€ app
β”‚  β”‚  β”œβ”€ build.gradle.kts
β”‚  β”‚  β”œβ”€ proguard-rules.pro
β”‚  β”‚  └─ src
β”‚  β”‚     └─ main
β”‚  β”‚        β”œβ”€ AndroidManifest.xml
β”‚  β”‚        └─ kotlin
β”‚  β”‚           └─ hello
β”‚  β”‚              └─ skip
β”‚  β”‚                 └─ Main.kt
β”‚  β”œβ”€ gradle
β”‚  β”‚  └─ wrapper
β”‚  β”‚     └─ gradle-wrapper.properties
β”‚  β”œβ”€ gradle.properties
β”‚  └─ settings.gradle.kts
β”œβ”€ Darwin
β”‚  β”œβ”€ Assets.xcassets
β”‚  β”‚  β”œβ”€ AccentColor.colorset
β”‚  β”‚  β”‚  └─ Contents.json
β”‚  β”‚  β”œβ”€ AppIcon.appiconset
β”‚  β”‚  β”‚  └─ Contents.json
β”‚  β”‚  └─ Contents.json
β”‚  β”œβ”€ Entitlements.plist
β”‚  β”œβ”€ HelloSkip.xcconfig
β”‚  β”œβ”€ HelloSkip.xcodeproj
β”‚  β”‚  └─ project.pbxproj
β”‚  └─ Sources
β”‚     └─ HelloSkipAppMain.swift
β”œβ”€ LICENSE.LGPL
β”œβ”€ Package.swift
β”œβ”€ README.md
β”œβ”€ Skip.env
└─ Sources
   └─ HelloSkip
      β”œβ”€ ContentView.swift
      β”œβ”€ HelloSkip.swift
      β”œβ”€ HelloSkipApp.swift
      β”œβ”€ Resources
      β”‚  └─ Localizable.xcstrings
      └─ Skip
         └─ skip.yml


Running swift build in the hello-skip folder builds the module and performs the transpilation.

This derived project hierarchy will look like:

hello-skip swift build output

hello-skip % tree .build/plugins/outputs/hello-skip/HelloSkip/skipstone/

.build/plugins/outputs/hello-skip/HelloSkip/skipstone/
β”œβ”€β”€ HelloSkip
β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β  └── src
β”‚Β Β      └── main
β”‚Β Β          β”œβ”€β”€ kotlin
β”‚Β Β          β”‚Β Β  └── hello
β”‚Β Β          β”‚Β Β      └── skip
β”‚Β Β          β”‚Β Β          β”œβ”€β”€ ContentView.kt
β”‚Β Β          β”‚Β Β          β”œβ”€β”€ HelloSkip.kt
β”‚Β Β          β”‚Β Β          └── HelloSkipApp.kt
β”‚Β Β          └── resources
β”‚Β Β              └── hello
β”‚Β Β                  └── skip
β”‚Β Β                      └── Resources
β”‚Β Β                          β”œβ”€β”€ Localizable.xcstrings -> /private/tmp/hello-skip/Sources/HelloSkip/Resources/Localizable.xcstrings
β”‚Β Β                          └── resources.lst
β”œβ”€β”€ HelloSkip.skipcode.json
β”œβ”€β”€ SkipFoundation -> ../../../skip-foundation/SkipFoundation/skipstone/SkipFoundation
β”œβ”€β”€ SkipLib -> ../../../skip-lib/SkipLib/skipstone/SkipLib
β”œβ”€β”€ SkipModel -> ../../../skip-model/SkipModel/skipstone/SkipModel
β”œβ”€β”€ SkipUI -> ../../../skip-ui/SkipUI/skipstone/SkipUI
β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”œβ”€β”€ gradle
β”‚Β Β  └── wrapper
β”‚Β Β      └── gradle-wrapper.properties
β”œβ”€β”€ gradle.properties
└── settings.gradle.kts


The resulting Gradle project hierarchy contains not only the links to the transpiled output for the current project, but also links to the project output for each dependent module. These dependencies are automatically created as a result of the Skip transpiler plugin being run on the dependent projects.


Building Locally

Gradle projects can be run manually, either from Android Studio or using the gradle command-line tool. Skip app projects created with skip init have a root Android/ folder that contains a settings.gradle.kts file. This can be opened in Android Studio, or it can be run directly from the command line.

The Android build folder is configured by settings.gradle.kts to output to the root .build/Android/ folder. This centralizes the location of the build artifacts and enables a single folder to be ignored in a .gitignore file (rather than the default Gradle folder name of build/).

skip init command output

$ skip init --appid=com.xyz.HelloSkip hello-skip HelloSkip

Initializing Skip library hello-skip
[βœ“] Create project hello-skip (0.73s)
[βœ“] Resolve dependencies (5.89s)
[βœ“] Build hello-skip (15.2s)
[βœ“] Created module HelloSkip in ~/Desktop/hello-skip/HelloSkip.xcodeproj

$ cd hello-skip 

$ swift build --build-tests

Fetched https://source.skip.tools/skip.git (0.92s)
…
[294/294] Linking libHelloSkip.dylib
Build complete! (23.13s)

$ skip gradle -p .build/plugins/outputs/hello-skip/HelloSkip/skipstone/HelloSkip test

GRADLE> > Task :HelloSkip:preBuild UP-TO-DATE
…
GRADLE> > Task :HelloSkip:testDebugUnitTest
GRADLE> > Task :HelloSkip:test
GRADLE> 
GRADLE> BUILD SUCCESSFUL in 20s
GRADLE> 204 actionable tasks: 204 executed
note: Gradle SUCCESSFUL

$ skip gradle -p Android/ assemble

GRADLE> > Task :app:preBuild UP-TO-DATE
GRADLE> > Task :app:preDebugBuild UP-TO-DATE
GRADLE> > Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
GRADLE> > Task :app:generateDebugBuildConfig
GRADLE> > Task :HelloSkip:preBuild UP-TO-DATE
…
GRADLE> > Task :SkipUI:bundleReleaseAar
GRADLE> > Task :HelloSkip:compileDebugJavaWithJavac NO-SOURCE
…
GRADLE> > Task :app:processReleaseJavaRes
GRADLE> > Task :HelloSkip:extractDebugAnnotations
GRADLE> > Task :HelloSkip:mergeDebugGeneratedProguardFiles
GRADLE> > Task :HelloSkip:mergeDebugConsumerProguardFiles
GRADLE> > Task :SkipUI:assembleRelease
GRADLE> > Task :SkipUI:assemble
GRADLE> > Task :HelloSkip:mergeDebugJavaResource
GRADLE> > Task :app:compileDebugKotlin
GRADLE> > Task :HelloSkip:syncDebugLibJars
GRADLE> > Task :app:compileDebugJavaWithJavac
GRADLE> > Task :app:mergeReleaseJavaResource
GRADLE> > Task :app:dexBuilderDebug
GRADLE> > Task :app:processDebugJavaRes
GRADLE> > Task :app:mergeDebugGlobalSynthetics
GRADLE> > Task :app:mergeProjectDexDebug
GRADLE> > Task :app:mergeLibDexDebug
GRADLE> > Task :HelloSkip:bundleDebugAar
GRADLE> > Task :HelloSkip:assembleDebug
GRADLE> > Task :HelloSkip:assemble
GRADLE> > Task :app:mergeDebugJavaResource
GRADLE> > Task :app:minifyReleaseWithR8
GRADLE> > Task :app:shrinkReleaseRes
GRADLE> > Task :app:packageRelease
GRADLE> > Task :app:createReleaseApkListingFileRedirect
GRADLE> > Task :app:assembleRelease
GRADLE> > Task :app:assemble
GRADLE> 
GRADLE> BUILD SUCCESSFUL in 53s
GRADLE> 403 actionable tasks: 403 executed


The .apk from the build will be placed in the .build/Android/app/outputs/apk/ folder:

$ ls -lah .build/Android/app/outputs/apk/*/*.apk

57M .build/Android/app/outputs/apk/debug/app-debug.apk
13M .build/Android/app/outputs/apk/release/app-release-unsigned.apk


Skip Framework Transpilation

A valid Skip project must contain a Skip/skip.yml file in each Skip-enabled module. This file is a YAML document that describes the module’s representation in the Kotlin/Gradle world. During transpilation, this file is combined with all the dependency project’s skip.yml files and used to affect how the Gradle project is created. Use skip.yml to customize the Gradle build process, or to add dependencies on external Java or Kotlin libraries that you can then use directly from Skip code.

Gradle projects use the files settings.gradle.kts and build.gradle.kts for configuration, much like a Swift Package Manager project uses Package.swift. These are kotlin-script files that can configure all aspects of the build process, from compilation arguments to output post-processing. More can be read on the topic at https://docs.gradle.org/current/userguide/writing_build_scripts.html.

Skip abstracts away the details of the Gradle project configuration for Framework projects by automatically deriving a valid Gradle project from the SwiftPM Package.swift dependencies combined with the contents of each project’s Skip/skip.yml file. The Skip transpiler outputs a Gradle project folder hierarchy as part of its output process.

Framework Build Outputs

Framework projects differ from app projects in that while app projects surface the various Gradle app-level build files (Android/settings.gradle.kts and Android/app/build.gradle.kts), framework projects generate and maintain the build structures for the transpiled projects. Skip considers the generated Gradle project, along with the transpiled Kotlin code, to be ephemeral. Cleaning the build may delete the files, and re-running the transpiler will override any changes. Unless you (manually) export or archive the Gradle project, it may be overwritten at any time.

When building from the command-line using swift build or skip test, the gradle projects will be output to the .build/plugins/outputs/ folder, each in its own package-named directory. When building from Xcode, the outputs are instead placed in ~/Library/Developer/Xcode/DerivedData/ProjectName-identifier/SourcePackages/plugins/.

The Skip plugin is run in a restrictive sandbox that limits the output folders that the transpiler can write to. For this reason, each separate dependency is output to its own separate folder, and each depending project references it by making a symbol link to the local output for that project. For example, the HelloSkip app’s local dependencies on the SkipStack frameworks can be seen:

Skip build output file layout

$ tree -L 5 .build/plugins/outputs

.build/plugins/outputs
β”œβ”€β”€ hello-skip
β”‚Β Β  └── HelloSkip
β”‚Β Β      └── skipstone
β”‚Β Β          β”œβ”€β”€ HelloSkip
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β          β”‚Β Β  └── src
β”‚Β Β          β”œβ”€β”€ HelloSkip.skipcode.json
β”‚Β Β          β”œβ”€β”€ SkipFoundation -> ../../../skip-foundation/SkipFoundation/skipstone/SkipFoundation
β”‚Β Β          β”œβ”€β”€ SkipLib -> ../../../skip-lib/SkipLib/skipstone/SkipLib
β”‚Β Β          β”œβ”€β”€ SkipModel -> ../../../skip-model/SkipModel/skipstone/SkipModel
β”‚Β Β          β”œβ”€β”€ SkipUI -> ../../../skip-ui/SkipUI/skipstone/SkipUI
β”‚Β Β          β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”‚Β Β          β”œβ”€β”€ gradle
β”‚Β Β          β”‚Β Β  └── wrapper
β”‚Β Β          β”œβ”€β”€ gradle.properties
β”‚Β Β          └── settings.gradle.kts
β”œβ”€β”€ skip-foundation
β”‚Β Β  └── SkipFoundation
β”‚Β Β      └── skipstone
β”‚Β Β          β”œβ”€β”€ SkipFoundation
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β          β”‚Β Β  └── src
β”‚Β Β          β”œβ”€β”€ SkipFoundation.skipcode.json
β”‚Β Β          β”œβ”€β”€ SkipLib -> ../../../skip-lib/SkipLib/skipstone/SkipLib
β”‚Β Β          β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”‚Β Β          β”œβ”€β”€ gradle
β”‚Β Β          β”‚Β Β  └── wrapper
β”‚Β Β          β”œβ”€β”€ gradle.properties
β”‚Β Β          └── settings.gradle.kts
β”œβ”€β”€ skip-lib
β”‚Β Β  └── SkipLib
β”‚Β Β      └── skipstone
β”‚Β Β          β”œβ”€β”€ SkipLib
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β          β”‚Β Β  └── src
β”‚Β Β          β”œβ”€β”€ SkipLib.skipcode.json
β”‚Β Β          β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”‚Β Β          β”œβ”€β”€ gradle
β”‚Β Β          β”‚Β Β  └── wrapper
β”‚Β Β          β”œβ”€β”€ gradle.properties
β”‚Β Β          └── settings.gradle.kts
β”œβ”€β”€ skip-model
β”‚Β Β  └── SkipModel
β”‚Β Β      └── skipstone
β”‚Β Β          β”œβ”€β”€ SkipLib -> ../../../skip-lib/SkipLib/skipstone/SkipLib
β”‚Β Β          β”œβ”€β”€ SkipModel
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β          β”‚Β Β  └── src
β”‚Β Β          β”œβ”€β”€ SkipModel.skipcode.json
β”‚Β Β          β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”‚Β Β          β”œβ”€β”€ gradle
β”‚Β Β          β”‚Β Β  └── wrapper
β”‚Β Β          β”œβ”€β”€ gradle.properties
β”‚Β Β          └── settings.gradle.kts
β”œβ”€β”€ skip-ui
β”‚Β Β  └── SkipUI
β”‚Β Β      └── skipstone
β”‚Β Β          β”œβ”€β”€ SkipFoundation -> ../../../skip-foundation/SkipFoundation/skipstone/SkipFoundation
β”‚Β Β          β”œβ”€β”€ SkipLib -> ../../../skip-lib/SkipLib/skipstone/SkipLib
β”‚Β Β          β”œβ”€β”€ SkipModel -> ../../../skip-model/SkipModel/skipstone/SkipModel
β”‚Β Β          β”œβ”€β”€ SkipUI
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ build.gradle.kts
β”‚Β Β          β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
β”‚Β Β          β”‚Β Β  └── src
β”‚Β Β          β”œβ”€β”€ SkipUI.skipcode.json
β”‚Β Β          β”œβ”€β”€ SkipUnit -> ../../../skip-unit/SkipUnit/skipstone/SkipUnit
β”‚Β Β          β”œβ”€β”€ gradle
β”‚Β Β          β”‚Β Β  └── wrapper
β”‚Β Β          β”œβ”€β”€ gradle.properties
β”‚Β Β          └── settings.gradle.kts
└── skip-unit
    └── SkipUnit
        └── skipstone
            β”œβ”€β”€ SkipUnit
            β”‚Β Β  β”œβ”€β”€ build.gradle.kts
            β”‚Β Β  β”œβ”€β”€ proguard-rules.pro
            β”‚Β Β  └── src
            β”œβ”€β”€ SkipUnit.skipcode.json
            β”œβ”€β”€ gradle
            β”‚Β Β  └── wrapper
            β”œβ”€β”€ gradle.properties
            └── settings.gradle.kts


Building an app project APK

Building a framework project AAR

For more information on the published output format Publishing a project as module and Android Gradle Plugin Upload your library.


Gradle Dependencies

Every Skip App project depends on the SkipStack frameworks, which contain the five core modules for any application, and whose skip.yml files can serve as useful examples: SkipUI, SkipModel, SkipFoundation, SkipLib, and SkipUnit. Each of these projects are automatically transpiled in turn, resulting in a web of project links that constitute a buildable Gradle project. As these are dependencies that are locally checked out, their transpiled output can be referenced from Gradle through the relative symbolic links that are created as part of a module’s transpilation.

Read the Dependencies documentation to learn more about using skip.yml to add Java/Kotlin dependencies.