We you this feature when building workspace with virtual targets. The -g or -O2 are then set in build configuration options not in project options. This is useful when build virtual target over workspace with many projects.Can you be more precise? If you look at the C::B workspace its the same there w/o any extension: We have grouped targets using virtual targets there, too.
Options editable via global configuration Settings > Compiler and debugger ...
I see only this advance - dont need to create 2 targets anytarget_build and anytarget_release just anytarget and set global build configs.You can do this with macros now already...?! Maybe instead of misunderstanding you could post a simple patch that demonstrates what you've modified... I think I just don-'t get it...
When macro replacements are set then pass this via event sink to plugin thus give chance to handle not existing macros.We could do so, but we don't always know if a macro has actually been replaced or not due to recursion.
$if($(BUILD_CFG)==release){cmd /C "$(#pfx)\sign.bat $TARGET_OUTPUT_FILE"}
$if($BUILD_CFG==release){cmd /C "$(#pfx)\sign.bat $TARGET_OUTPUT_FILE"}
Well if that is true its a bug and we should fix it. What makes me wonder is if you shouldn't use something like:Quote$if($(BUILD_CFG)==release){cmd /C "$(#pfx)\sign.bat $TARGET_OUTPUT_FILE"}but this does not want to expand noway. The BUILD_CFG is custom variable with value release
$if("$(BUILD_CFG)"=="release"){cmd /C "$(#pfx)\sign.bat $TARGET_OUTPUT_FILE"}
("release"=="release"){cmd /C "c:\Work\IDEalCodeStudio\pfx\sign.bat ..\..\bin\release\epsdebugger.tdm.dll"}
Execution of '("release"=="release"){cmd /C "c:\Work\IDEalCodeStudio\pfx\sign.bat ..\..\bin\release\epsdebugger.tdm.dll"}' in 'C:\Work\IDEalCodeStudio\Plugins\TargetDeviceManager' failed.
Nothing to be done.