Automated script to create latest release (can be beta, or release) of Aseprite for macOS
Project is updated against aseprite v.1.2.9 build workflow.
You need to install Xcode by downloading it here.
After successfully installed, you install Xcode's toolchain by executing
xcode-select --install then follow along when popup shown up.
Now you're ready to use this script.
How to Build
bash aseprite.sh. Then open
If the application asks for root password, enter it. This is to be able to execute command to properly set environment path variable.
Command line Configuration
In case you want to install aseprite to different path, or your
xcode-select is not set properly, you can use either
--target to properly set things up before building.
To set your latest MacOS SDK root as part of Xcode toolchain. By default it will query current prefix-value from
xcode-selectand append it with
/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk. But in case, it doesn't work or
xcode-selectdidn't do the work, you can use this option to manually specify it.
To set you target path to install aseprite. By default it will be at
/Applicationsbut it might be different for some users.
So for example, you will execute
bash aseprite.sh --sdk-root /Volumes/Slave/Applications/Xcode8.3/Xcode.app/Contents/Developer --target ~/slave/Applications
Note that the current build system for aseprite only supports buliding against macOS 10.12. 10.13 didn't work as I tested it.
Normal, barebone version with no parameters.
With custom parameters to specify SDK_ROOT and TARGET
bash aseprite.sh --sdk-root /Volumes/Slave/Applications/YourCustomDir/Xcode.app/Contents/Developer --target ~/YourCustomDir/Appliations
Behind the Scene
The script will proceed with following
- Clone down Aseprite and Skia repository, and its dependencies required to bulid Aseprite.
- Compile and build dependencies
- Clone down Aseprite repository, then compile and build for latest release as tagged on Github (can be either beta or release version)
Aseprite.appis pre-created bundle file to wrap soon-to-be-built Aseprite. It contains script to execute an aseprite binary file with default executable path at
~/Applications/Aseprite/aseprite. Such bundle file is created with macOS's Script Editor application.
- If you previously clone any dependencies, the script will know and will instead try to update it from upstream for you. So you're ensured that it will operate on the most latest release state version of Aseprite.
- Updated version of Aseprite might break cloned dependencies's build workflow especially error about
CXXenvironment variables are not set to correct path. If this is a case, it's likely that you re-build on previously compiled source code of dependencies in which
cmakestill keeps the old configurations used in successfully compile. To resolve the problem, remove the whole build folder namedly
asepritethen start it all over executing
- In case you want to build older version of Aseprite, take a look at Releases section then find a corresponding target version of Aseprite you look for.
Aseprite is cool. It is free if you build it by yourself like you did above, or you can purchase it at official website to avoid spending effort in manual build process.
This automated build script gathers information from Aseprite's INSTALL.md on how to build, and sum it up together as automated script you're using it here.
MIT, Wasin Thonkaew