Page 2 of 2

Re: TwineCompile with MSbuild, but not with IDE

Posted: Tue Mar 02, 2021 11:23 am
by zzattack
Awesome, thanks. Which property does -prog- map to? Far as I can tell this is undocumented still. If not, where should I be looking?

Re: TwineCompile with MSbuild, but not with IDE

Posted: Tue Mar 02, 2021 2:17 pm
by jomitech
It's not published as an MSBuild property out of the box, so you need to make some tweaks to make it available. The easiest way is to modify TCTargets104.targets to add it directly to the TCCompileFileList task.

For example:
<TCCompileFileList
Condition="('$(FileToCompile)'=='' Or '$(TCChildBuild)'!='true') And '$(TC_HasFiles)'=='True'"
Threads="$(TC_Threads)"
DisableCaching="$(TC_DisableCaching)"
InjectHeader="$(BCC_PCHInject)"
AllocateFiles="$(TC_AllocateFiles2)"
StopOnErrors="$(TC_StopOnErrors)"
FileAliases="$(TC_FileAliases)"
Make="$(TC_Make)"
Priority="$(TC_Priority)"
Affinity="$(TC_Affinity)"
MaxCache="$(TC_MaxCache)"
PermanentCache="$(TC_PCache)"
ProjectDirectory="$(MSBuildProjectDirectory)"
UseClang="$(USING_CLANG)"
DisableProgress="$(TC_DisableProgress)"
/>

And then you can invoke the compile and set the TC_DisableProgress property to true or false.

Re: TwineCompile with MSbuild, but not with IDE

Posted: Tue Mar 02, 2021 3:10 pm
by zzattack
Excellent, thank you, works perfectly. I noticed multiple TCCompileFileList entries in this XML, simply adding the DisableProgress attribute to each did the trick.
I hope this will become available by default in the Targets file, as I can see myself overwriting this file with new installers without realizing it.

Re: TwineCompile with MSbuild, but not with IDE

Posted: Thu Jan 13, 2022 9:32 am
by zzattack
This no longer appears to work with the TcTargets110.targets file. Do we have to change something?

Re: TwineCompile with MSbuild, but not with IDE

Posted: Mon Jan 17, 2022 11:29 am
by jomitech
Unfortunately, we removed the -prog- flag from the MSBuild action because we thought it was not being used any longer. We'll add it back in the next release and make it part of the targets files as well.