JomiTech Forums

Yep, just for the record, I had to reinstall Codegear to get command line to compile without TC, but when it happened the same to another co-worker we realized that the reason was that we had replaced ilink32 and bcc32 in C++ Builder 2007 with the ones from C++ Builder 2010. That was something we bo...

Hi Jon, My compilation errors using bcc32 got solved after reinstalling C++ Builder (sigh). Enabling/Disabling compilation with Twinecompile works fine in 3.2 for me now with your suggested msbuild flags: Using TC ---------- msbuild Project.groupproj /target:Make /p:Configuration=Release NOT Using T...

Hi Jon, I have tried the option you mention and: 1.- I see that with those options it now uses BCC32 instead of mtbcc32 when compiling the code (GOOD) 2.- I get many compilation errors, apparently due to problems with RAD Studio lib paths (When disabling TC in the IDE it compiles fine). Anything els...

Yes, all our cbproj have included both Borland and TCTargets targets files since we started to use Twinecompile back in version 2.x <Import Project="$(MSBuildBinPath)\Borland.Cpp.Targets" /> <Import Project="C:\Program Files\JomiTech\TwineCompiler\TCTargets.targets" /> Previously...

Hi, When we were using TC 2.x we created 2 separate batch files to compiIe using or not TwineCompile Command line to compile using TC msbuild Project.groupproj /target:Make /p:CoreCompileDependsOnTargets="DccCompile;TCBuildFileList;TCCompile;TasmCompile;BrccCompile;" /p:Configuration=Relea...