JomiTech Forums

The TwineCompile license does permit the use of TwineCompile in a build server. That's why I said you can just copy the files right over - it will work correctly.

I would recommend just building the files directly into your docker image instead of installing TwineCompile every time. You can get them from the TwineCompile Program Files directory that's created when installing off Get it. There isn't really any overhead for using the trial, except for the trial...

You can transfer the necessary files (jtmake.exe, mtbcc32.exe etc..) into your Docker image and use them without transferring any licenses. The license is linked to the IDE plugin, which I'm guessing you won't be using in the Docker image. Let me know if that works for you, or feel free to provide a...

You can use the command to view the available command-line commands. Use to set a default directory.

What compiler are you using in your projects? Classic, CLANG Win32, CLANG Win64, Win64 Modern?

No side effects, -ide120 is the correct way to invoke any 12.x project builds with jtmake.

That is complicated. We'll have to work out a better solution for updating GetIt-based installations.

After the installer has started, just kill the IDE. The installer should remain running and will be able to complete the installation with no issues.

The fix for this issue is now available. Re-download TwineCompile via GetIt to get the new 5.8.1 release that fixes the issue.

Thanks for reporting this issue. We will be issuing a fixed version within a couple of days.