JomiTech Forums

The latest TwineCompile (installed via GetIt) for RAD Studio 11 fails to compile my clang64 project (which was created with RAD Studio 10.4) with the error message F1009, cannot open input file project-path-and-name.@@@
However, TwineCompile deletes and recreates this file successfully and it appears to be valid.

Note that TwineCompile 5.2.3.319 / RAD Studio 10.4 which are installed in parallel on the same machine can build the same project flawlessly.

Thanks for any suggestions!

This is a very weird error, since it's obviously creating this file. Do you get this error if you just compile a single unit or project, or does it only happen if you build the entire project group?

Thanks for the reply, I found the problem:
it happens if the path to the project contains a white-space. And yes, it also fails if I try to compile a single unit.

I just tried with a new default VCL project: if I place it inside the folder
"Z:\Test Project" it fails with that F1009, if I place it inside "Z:\TestProject" it works.

In case of my original issue it's my private component library, located in
"Z:\gc_include\packages\GoldenCode Components" ...

A fix will be highly appreciated

Hi supporters - same applies to me!
The last versions of TwineComplie did a very good job - but now the same projects cannot be compiled since there is more than one blank in the project-path.
Please fix this issue in the near feature.

Yes, there was a path issue with the C++Builder 11 support. This has now been fixed. Please download the latest build from GetIt or from My Center and reinstall.

In order to update from GetIt, do I need to uninstall en reinstall TwineCompile, or should I simply wait untill an update is option comes available?

Just uninstall and re-install from GetIt. There won't be an update show up in GetIt.

If the GetIt package does not refresh for you, you can download the update here (it will be available for a few days): http://jomitech.com/downloads/TwineCompile530Update.zip

uninstalling and re-installing did not work, but the link you provided did work. Thanks!

Thanks, Jon! Another job well done, now I can check out C++ Builder 11 - it doesn't make sense to even start up this dev suite without a working TwineCompile...