Community
Participate
Working Groups
Build ID: 4.0.3 Steps To Reproduce: There seems to have been a regression in the Per Resource build configuration settings between 4.0.2 -> 4.0.3. The problem is that, if you view a file's properties and examine its tool options, they are now set to the toolchain default settings rather than the project / container settings. The problem appears to have been introduced in the change for bug 219684 on Tool.java (between revision 1.77.2.2 and 1.77.2.3)... More information:
Thanks for finding. It may be regression really. Could you please provide more detailed explanation how to reproduce your problem.
Basically trying to override one compiler Option at a file level, I right click on file -> Properties -> C/C++ Build -> Settings. The file doesn't (before doing this) have a resource config. When the dialog opens, the compiler options displayed are the tool chain defaults and not the currently set options values on the project. Reverting this change and the project level settings appear again - ready to be overriden.
Fixed in Head.
Created attachment 92490 [details] Patch for CDT 4 branch Thank Oleg! Just to confirm, apart from the generics changes, the only change of note was the one line change in Tool.java:getToolCommandFlags(IPath inputFileLocation, IPath outputFileLocation, SupplierBasedCdtVariableSubstitutor macroSubstitutor, IMacroContextInfoProvider provider)? It may be worth applying this to the cdt_4_0 branch for those pulling changes off there...
Your patch is applied in 4_0 branch.
