Automated script to create latest release (whatever it will be either development snapshot commit, beta, or release) of Aseprite for macOS
Update : Added support x64 Architecture build for SKIA on MacOS
Project is updated against aseprite v.1.2.10 build workflow.
You need
For Xcode, you need to install it by downloading here. After successfully installed, execute xcode-select --install
to install its toolchain, then finally follow along as dialog popup shows up.
Now you're ready to use this script.
Just execute bash aseprite.sh
. Then open Aseprite
application.
If the script asks for root password, enter it. This is to be able to execute command to properly set environment path variable. It's safe, the script never try to do anything beside trying to build the app successfully.
In case you want to install aseprite to different path, or your xcode-select
is not set properly, you can use either --sdk-root
and --target
to properly set things up before building.
--sdk-root
To set your latest macOS SDK root as part of Xcode toolchain. By default it will query current prefix-value from xcode-select
and append it with /Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
. But in case, it doesn't work or xcode-select
didn't do the work, you can use this option to manually specify it.
--target
To set you target path to install aseprite. By default it will be at /Applications
but some users might want it differently. In case you use this parameter, please see #3.
So for example, you will execute
bash aseprite.sh --sdk-root /Volumes/Slave/Applications/Xcode8.3/Xcode.app/Contents/Developer --target ~/slave/Applications
note if you use --target
, please see #3.
Normal, barebone version with no parameters.
bash aseprite.sh
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
The script will proceed with following
.app
bundle at ~/Applications
Aseprite.app
is 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.
CC
or CXX
environment 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 cmake
still keeps the old configurations used in successful compile. To resolve the problem, remove the whole build folder namedly aseprite
then start it all over again. 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 here.
MIT, Wasin Thonkaew