JomiTech Forums

Thanks for reporting this. Can you use a backup copy of jtmake, but just rename it? So for XE4 use it jtmake-xe4.exe, and for anything newer jtmake.exe?

Unfortunately, TwineCompile does not support being invoked multiple times in parallel as you have discovered. The rationale is that TwineCompile will be using all the available CPU resources anyway, so there is no advantage to supporting it. Can you change your build process to execute the build ste...

This fix was already put in place for 13.0 - so it's available in GetIt for the latest IDE version. I don't know if we'll update it for 12.x, there have only been a handful of installations impacted by this issue.

Thanks for using TwineCompile. Glad to hear that it's helping you so much.

Please download the following file and extract into the TwineCompile Program Files directory to resolve the issues with the conflicted unit names from DDetours.

https://jomitech.com/downloads/TwineCom ... gin123.zip

The simplest way to integrate TwineCompile into a build process is to replace the MSBuild process with jtmake.exe, which is a command-line tool bundled with TwineCompile that essentially invokes MSBuild for a project or project group, and uses TwineCompile to build the C++ files. It is possible to g...

Here is a fix for this issue. Please download and extract into the TwineCompile Program Files directory:

https://jomitech.com/downloads/IntlChars582.zip

Remove the -B from the command-line. -B tells jtmake to do a full build, discarding all previous compiled state and compiling all the projects from scratch. For example:

Ahh, that makes sense. This was a known issue with 5.9 - basically the in-memory changes to the project were not being passed into the MSBuild process, so the version information was not updated. Download the following file and extract into the TwineCompile Program Files directory to resolve the iss...

That makes sense - there are some issues with the way CLANG interacts with TwineCompile and the IDE (CLANG emits UTF-8 by default, but TwineCompile operates under ISO-8859-1)

Unfortunately, jtmake doesn't support that right now. We'll definitely take it under advisement as a potential future feature. Thanks for mentioning it.