JomiTech Forums

Thanks for pointing this out. We upgraded the project to the latest IDE and forgot to change the RTL/runtime packages options.

That is very weird. I personally haven't ever seen that before. Is preamble a project name or something related to your project? Normally the PCH files have a defined name that comes from the project file.

Thanks for the detailed information. This clearly points to some sort of issue with the way TwineCompile is invoking CLANG. Can you send the complete output of the IDE's Build output window (from an IDE compile) and the twfiles.@@@ file (from a TwineCompile compile) to support@jomitech.com? This wil...

This is very interesting. The compiler is definitely crashing with an access violation. Can you try two separate things:

1. Turn off file caching in the TwineCompile options and try compiling that file.

2. Compile the project on the command-line using MSBuild directly (without TwineCompile).

The following resources are provided for instructions on detailed TwineCompile features such as manually registering the IDE plugin, building projects on the command-line or using build systems like MSBuild.

http://jomitech.com/TwineCompile.pdf

http://jomitech.com/TwineCompile.txt

We don't have a publicly available changelog at this time unfortunately. The 5.2.2 changes are as follows: - Fixed some issues with PCH handling in C++Builder 10.4 and 10.3 - Revised error/warning color handling on the message view - Fixed issues with loading Borland assemblies when using TwineCompi...

Can you send the entire contents of the console output tab in the Compile Window to contact@jomitech.com? The error you mentioned comes from the compile step, but the lines are indicating a linker error.

Sorry for this error you are encountering. Unfortunately, Embarcadero made several core breaking changes between the patches and updates in the 10.4 release, so we have been forced to only support the very latest version - 10.4.1 (10.4 Update 1). Please upgrade to C++Builder to 10.4 Update 1, rather...

I have a fix that may solve this issue. Please download the following file and extract it into the TwineCompile Program Files directory.

http://jomitech.com/downloads/JTBuildInterface104.zip

This is a new file. We split the loading functionality into two DLLs now, so that the first can load and configure the appropriate paths for the second one to be able to load (JTBuildInterface104.dll has references to the Borland*.dll files, so cannot be loaded if those references can't be found).