-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aseprite only CLI #1279
Comments
Hi @JosefKuchar, that's not possible at this moment but I'd like to make that possible in a near future. Related to #139 |
What needs to change to make this happen? I'm happy to help |
@jacksarick I think it's a pretty big change for someone that want to contribute for the very first time. I would prefer smaller bug fixes first and then trying to contribute to something big. Anyway, for some reference, the basic idea is that this statement must be completely ignored from the compilation process (and all the dependencies should be ignored too/not linked, i.e. UI library isn't needed, etc.) |
New |
This was originated for aseprite#1279 (CLI-only Aseprite) which can be achieved with LAF_BACKEND=none anyway. In this way we simplify the development process, and checking for the availability of the GUI can be done in run-time through App::isGui() or Context::isUIAvailable().
Hello,
Can I compile aseprite without GUI, only CLI tools ?
Thx
The text was updated successfully, but these errors were encountered: