Not all options are passed on to bcc64x.exe

[oliwe]

But Version Info is not pushed to the build executable via twinecompile. If I change the module version number (in project options->Application-> Version Info) and compile (make) without twinecomile the change is puhsed to the exe, if I enable twinecompile the change is not pushed to the exe. I also tested twinecompile with bcc64 -> same problem. It is just a minor problem - yes - but would be nice if it is fixed.

[jomitech]

If you run a build, does the updated module version number get linked into the executable?

[oliwe]

No - it is not linked in - if I check the executable properties "File Version" is not changed. Doing a "make" without TwineCompile will directly change the "File Version" to "Module Version Number".
(BTW I am changing "Module Version Number" always manually.)

[jomitech]

That is weird. Can you create a simple test project that reproduces this issue and send it to support@jomitech.com?

[oliwe]

Sorry for late reply.
I checked this issue again - it is still there.
Just create a new Windows VCL Application - C++ Builder.
If you increase the module version number (in project options->Application-> Version Info) and compile ("Make") without twinecomile the change is pushed to the exe, with twinecomile the change is not pushed to the exe.
I checked this in the Windows Explorer -> right click on exe -> Properties -> Details -> File version.
"Build" works with both (with and without TwineCompile), but for large projects you do not want always a time consuming build.
I tested the new toolchain Win64 modern and the old Win64 toolchain and got the error for both.

[jomitech]

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 issue.

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