Thanks for the reply. But what I need to do is replace the downloaded binary so that my cart gets embedded in there. How do I do that?
Also, my compiled version of TIC is much bigger (11MB) than the one you distribute (4MB). I used Visual Studio 2022. I've compiled plenty of things on Linux before but this is my first time compiling on Windows so I'm not familiar with the tools. Any ideas of options I should be using to make it smaller?
What is the binary that's downloaded? Just an exact copy of the TIC-80 executable? And same thing for Mac and Linux?
And what about HTML? The "htmllua" binary downloaded for that is only 343K. How do I make my own version of that?
Please consider changing this in the future. Honestly this is super disappointing to discover just now, almost 4 months into my project. There's no point in being able to customize the source code if it can't be used for exporting games.
The binary you download depends on OS you want to export to, but yes it's exact copy of tic executable, also we have version without editors in pro version.
Try to look at the https://github.com/nesbox/TIC-80/blob/main/.github/workflows/build.yml file where we have all the build configurations and options for all supported OS.
I know, it's disappointing, even for me and I'll try to improove this part in the future, sorry for that.
Hi all,
as a suggestion, I guess it won't be easy to implement but it would be nice to be able to include one more parameter in export commans, called URL.
If it's empty, it points to the tic80 repo to download the binaries (as currently), else TIC80 will get the binaries from URL entered. Even in local storage, if possible.
I think it would be something quite flexible although I don't know how difficult it is to program it.
Anyway, thanks for making TIC80!
Good ideas. I was also thinking, why not just clone the currently running executable? And then that made me realize something that IS really nice about the current setup, and that is that you can export on other systems. E.g. cloning would only work for the environment you're running. I don't have a Mac but the download-to-export system lets me create a Mac executable on Windows. That's pretty cool, and also makes me appreciate that it's more complicated than it seems. But at the very least, being able to export a custom build for the current environment you're running would just be really nice.
