You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build: Fix a design problem. Before this we used to install the engine into the local maven repository. This had several flaws: Apart from spamming the developers mavenLocal repository with thousands(!) of engine versions, it was hard to predict the actual engine version to use. This is because with Pull Requests or Tags and different Branches the names changed, especially when both the engine and the sdk had a tag. Controlling the engine version is now only controlled by the TRAVIS_TAG ENV-Var or manually on the engine repo (where usually master is cloned otherwise)
Copy file name to clipboardExpand all lines: build.gradle
+25-25
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ repositories {
33
33
}
34
34
}
35
35
36
-
if (System.getenv('TRAVIS') !=null) {
36
+
/*if (System.getenv('TRAVIS') != null) {
37
37
if (System.env.TRAVIS_TAG != null && System.env.TRAVIS_TAG != "") { // Strangely it has to be both, because it's sometimes set as TRAVIS_TAG="" when we're in travis but no tag is set
38
38
// v3.3.0-stable-sdk1 becomes 3.3.0-stable
39
39
// Intentionally not using lastIndexOf here, we want the second "-".
@@ -69,7 +69,7 @@ if (System.getenv('TRAVIS') != null) {
69
69
70
70
// This is the engine version that will be used per default on every regular commit
Copy file name to clipboardExpand all lines: docs/building.md
+4
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,10 @@ It's not really a big process but you should be familiar with the command line a
4
4
We will skip the process of cloning the repo/downloading the zip, as the net is full of examples about this.
5
5
6
6
## Defining the Engine Version
7
+
Note: The following explanation is somewhat outdate: We cannot download the Engine as Maven Dependency, as that misses critical stuff like jbullet.jar.
8
+
Thus we have the scripts `build_engine.sh` and `fix_engine.sh`, which download and fix the engine install. Currently we use [Gradle Composite Builds](https://docs.gradle.org/current/userguide/composite_builds.html)
9
+
The engine will be downloaded into an `engine` directory, so care about editing this repository, when trying to use a specific engine version.
10
+
7
11
As the SDK has been split apart from the Engine Core, it simply downloads it as a dependency.
8
12
This comes in handy when it comes to build time however you're most likely unable to check your own engine changes.
0 commit comments