At SCADE, we are working on streamlining the installation over the next couple of versions. Thanks to all that provided valuable feedback. Please find the instructions below
Installation changes from BETA5 to BETA6
- Please update CMake to use cmake version 3.8 or higher. See CMake install section
- Please use XCode 9.3 and Swift 4.1
- If you can "simulator could not be located error", check here
All download links are included in the below instructions.
SCADE 1.0 is supporting the following versions
- NEW Swift 4.1 on iOS, Swift 4.0.2 on Android
- iOS X 10.13 and greater
- Android 5.0 and greater
- OS requirement : Swift, and therefore SCADE, requires OSX version 10.13 or higher
- XCode 9.3 including Swift 4.1 is installed on the machine
- Android NDK R11c
- Android SDK 24.4.1 or higher
- CMake 3.10 or higher
- Gradle > 2-14.1 but < 3.0 Gradle 4.0 cannot be used
- Java 8
- Harddisk space: You need about 800 MB of harddisk space
You require Java 8 and higher. You can do this using the java -version command from the command shell as below
Alternatively, use the settings dialog:
- Open System Preferences
- Open java
and check the version. You should have Java 1.8 and higher
In case you have Java version 6 or 7, you need to update.
Option I : From the command line, type
brew tap caskroom/versions
brew cask install java8
Option II : Please find download link for Java 8 here
Option II - If you cannot use homebrew, use Java download link
- Open terminal
- Install homebrew if you don't have it
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
- Install makedepend
brew install makedepend
This will automatically link makedepend, however to confirm enter:
brew link makedepend
- Install wget
brew install wget
wget http://dl.google.com/android/repository/android-ndk-r11c-darwin-x86_64.zip -q --show-progress
- Unzip in user directory
unzip -qq ./android-ndk-r11c-darwin-x86_64.zip -d ~/
Be patient, this is a big file and takes about 2 mins.
If unzipping fails, download an archiver or unzipping app. There are several available on the App Store for free.
You should now find a directory
android-ndk-r11c in your user directory.
- Download sdk
wget https://dl.google.com/android/android-sdk_r24.4.1-macosx.zip -q --show-progress
- Unzip sdk
unzip -qq ./android-sdk_r24.4.1-macosx.zip -d ~/
- Run Android SDK Manager using
3.1 You may be presented with an error dialog (image below). Select the "More Info..." option. This will take you the download page. Follow all instructions. You may be required to restart your computer to allow the installation of Java to be complete.
Uncheck all default selections and choose
- Android 6.0 (API 23)
- Tools / Android SDK Build-tools version 23.0.2
- Extras / Android Support Repository
- Extras / Google Play Services
- Extras / Google Repository
Your selection windows should look like this
Now continue by pressing the Install 17 packages and accepting the licenses multiple times Finally, let's clear the android folder
- The .android folder. The .android folder that exists in the home directory of the user holdes settings that aren't needed and we want to start with clean slate.
- Delete the android folder using
sudo rm -Rf ~/.android
Gradle is our favourite build tool we use to build our Android and iOS app. If you are already using Gradle >= 2.14.1 and < 3.0 , you can skip this step.
Gradle can be installed in different locations. We use the local user directory
- Get Gradle using
wget https://services.gradle.org/distributions/gradle-2.14.1-all.zip -q --show-progress
- Unzip Gradle using
unzip -qq ./gradle-2.14.1-all.zip -d ~/
- Export Gradle home using
- Edit bash using
- In the VI edtor, after making the modifications, use :wq! to save and quit (Press Escape, type :wq! and press Return)
- Exit the terminal and open new terminal session for the bash setting to become active
gradle -vto review your version Your output should look similar to this:
CMake is used to compile and build the Apple iOS software
brew install cmake
- You are done.
cmake -versionshould give you cmake message stating a version of 3.11 (current cmake version as this time)
Especially if you have multiple versions of Xcode installed, its critical that you are using the correct version. Doublecheck using these commands
- swift -version
- xcrun swift -version
All these commands should point to Swift 4.1
If this doesn't result in Swift 4.1 option, try setting the command line tools Command Line Tools Setup
- Download SCADE here www.scade.io/download/
- The dmg file should now be in your Download folder (or similar folder)
- If your Mac did not automatically unzip the zip file, doubleclick to open the archive
- Scade.dmg becomes available in your folder
- Double click on Scade.dmg
- The Install dialog opens. Drag and drop Scade into the Applications folder
- Confirm that you want to overwrite any content
- Run SCADE from your applications directory
You find SCADE using Command + Space and searching for SCADE
or through your Applications Directory. Start it
- When you start SCADE for the very first time, you need to confirm this dialog
You will now be asked to provide a workspace folder. The workspace folder will contain the following assets:
- SCADE projects
- SCADE SDK and binary built during compilation process
Choose a good workspace location
Please make sure that the workspace location you choose is OUTSIDE of the directory where SCADE resides. In this way, you can update the software without impacting your work.
The following settings make it possible to compile to iOS and Android. Without the settings, you will be able to develop and run on iOS, but not be able to compile.
Open the preferences settings
and configure the paths. When you press the apply button, we do check the validity of the path.
Here are the default directories from the above installation steps:
- You need to append /bin/gradle to the home directory path of Gradle
- The default Android SDK path on MAC is
We use cmake for Android compilation, and unfortunately cmake cannot handle any spaces in the XCode path. Make sure that there are no whitespace in the XCode path, and if there are, rename the folder XCode is located in so that it doesn't contain spaces anymore.
Apple requires two different files for compiling apps
- a certificate file for signing the app, for instance cert.p12
- a mobile provision file prov.mobileprovisioning
You need to specify the location of these files in the build file of your app.
- Open the build file <YourApp>.build that can be found in the root directory of your project
- Scroll to the codeSignSettings section at the end of the file
- Modify the entries as shown below to reflect the location of your files
The certificate needs to be part of the keychain. Double click on it and make sure its part of your keychain:
Certificates can be password protected. Currently, we don't support password protected certificates, but will add this feature in the future.
Sometime the command line tools use the wrong version. Here the step to set command line tools to use Swift 3.1
- Run XCode 9.x
- Set Command Line Tools to use 9.1
Unfortunately, we have a few issues with backward compatibility that you manually need to fix. These are the obvious issues. Sorry for the inconvenience:
Please update the build file of your pre BETA5 project. Use right click, Open With .. Text editor and set the SDK setting to empty as shown here:
Old and incorrect:
New and correct:
We changed the path location within the project and you now need to use the relative path. For instance, all path should now point to res/<mybitmap>. In your existing project, whereever you referenced a resource (for instance bitmap) and provided a path, you need to update the path. The current bitmaps might be gone now, and you need to set the new correct location (i.e. the correct relative path) manually.
A change in the Swift language Swift Language change causes you to change some annotations:
- Please change the main file and add the @objc annotation like this:
- For EACH and EVERY variable that you use for binding, also if its a complex object, add @Objc dynamic in front of it.
if you forgot about this, we will kindly remind you
What went wrong:
You did not use new workspace folder
How to fix:
Switch to new unused workspace folder
What went wrong:
Command Line Tools in Xcode was not set
How to fix:
- Open Xcode
- Open Preferences: Locations
- Command Line Tools: Select an Xcode option
Also described in Set command line option