Community
Participate
Working Groups
Build Identifier: 20110615-0604 There are no entries to create a MS SDK C project in the project wizard. Similarly, a wizard-created C++ project will ignore all .c files inside of it, proclaiming nothing to build. Is there a workaround to creating MS SDK-targeted C projects other than renaming all .c files to .cpp inside a wizard-created C++ project? Reproducible: Always
Created attachment 198757 [details] MS Toolchain C patch Similarly to the GCC toolchain, I split the C/C++ Compiler tool into C Compiler and C++ Compiler and added the C input type to C Compiler. That way paths, symbols and options can be set per language like the GCC toolchain. The options inside C++ Compiler retain the same ids which means projects will upgrade correctly (I tested it). Also added template associations to allow creating hello world projects with the toolchain.
Andrew, does this solution sound reasonable to you?
(In reply to comment #2) > Andrew, does this solution sound reasonable to you? This is certainly the way to go. And if you have much similarities between MS C and C++ tools I suggest to consider creating "base" MS C compiler tool and extend them from that "superClass", that would make maintenance easier.
Created attachment 198785 [details] MS Toolchain C patch, updated Thanks, I put the common things in an abstract tool. I tried that before but it didn't work properly, I think I didn't have the abstract tool at the top level. I'd like to commit that to 8.0 as well as master but it adds some new strings. I guess having untranslated strings is better than waiting a full year before being able to compile C.
(In reply to comment #4) > Created attachment 198785 [details] > I'd like to commit that to 8.0 as well as master but it adds some new strings. I > guess having untranslated strings is better than waiting a full year before > being able to compile C. What's a problem with that, why can't you externalize the strings in 8.0?
(In reply to comment #5) > What's a problem with that, why can't you externalize the strings in 8.0? I was under the impression that Babel couldn't have translations specific to service releases but I see there is 5.0.1.
Fixed in 8.0 and master.
