JomiTech Forums

The next version of TwineCompile will support this with a new -Q option for jtmake. It will only emit progress information and the list of errors/warnings.

The next version of TwineCompile will append context information into the error/warning message stating the source file and project it's located in. For example:

Can you provide the entire output of the Console Output tab in the TwineCompile Compile Window? I'm guessing there's an error being emitted prior to mtbcc32 quitting.

This particular error should have had a project line above it, as this would have been part of the linker step, which runs for each project separately. Can you provide the whole output? (Send as a text file to support@jomitech.com). For C++ errors, I can see the parallel projects making it difficult...

The -parallel option does exactly what you are expecting it to do - it will compile multiple projects at the same time, allowing small projects to use all cores. This is what this option is for. The caveat is that it's only supported on C++Builder 11.0 (or newer) project groups. If you're compiling ...

Unfortunately, TwineCompile doesn't support switching the windows to be non-IDE floating windows. You'll either have to position the windows outside of the IDE (so they don't get covered up) and save the desktop, or just use the Tabs menu to bring it back to the front.

You can use the IDE's Tabs menu to bring the message window back to the front. It'll be listed near the bottom of the menu.

Alternatively, dock the window somewhere, then save the IDE desktop to make the dock position permanent.

Breaking the build steps up like this will prevent the right dependencies from loading correctly. To resolve this, open TCTargets121.targets, locate the TCPerformLink Target, and add this task right at the top: <TCInitTasks /> It should look like this: ... <Target Name="TCPerformLink" Depe...

Would it be possible to share why you need to see this information? For all builds, except for Win64 Modern, TwineCompile doesn't actually use a command-line build - it directly invokes the compiler DLL and passes the arguments into it, so there isn't a true 1-1 mapping available. If you're looking ...

Apologies for the delay in following up on this. Please download the following jtmake update and see if it resolves this issue for you: https://jomitech.com/downloads/jtmake.zip