Community
Participate
Working Groups
Some gcc options are picky about their input. Specifically the -include flag to preinclude header files is picky on Windows. If one specifies a Windows directory specification without quotes (e.g. -includeC:\temp\foobar.h) the command will fail. The command will work if it is quoted (e.g. -include"C:\temp\foobar.h") or in Unix style directory specification (e.g. -includeC:/temp/foobar.h). I'd like to see an option in the appropriate MBS options to validate file/directory specifications a bit more. Possible suggestions: - a "Quoted" Y/N option to force the user to use quotes or it won't be accepted, or automatically add quotes if not present - a "Independent Path Format" Y/N option that converts the path from the platform-specific entry into a platform independent forward slash equivalent automatically (or requires the user to do so).
A generic way of contributing validators for options is really what we need here.
