aBothe
Different configurations have their own Import search paths?
This is more of a suggestion than something that needs to happen. I have noticed that configurations do not have their own search path for imports, but if possible I would like them to. It doesn't actually affect anything, it is just a little annoying to have both my Window search paths and my Linux ones added to the command line when I only need one set.
Sry, closed it by accident - well, weren't version(Windows/Posix) constraints thought to bypass this range of problems? :P
Sorry, I forgot that I opened this. :P
I wasn't talking about anything in actual code, but instead in the project settings for where the imports are located that get used for code completion(the include section under the build options). I had started a project file that I used for both Windows and Linux builds and just used different configurations for system settings(eg, Debug-Lunux, Debug-Windows, etc.). Despite having different configurations, there doesn't seem to be any separation of import locations between any of them and it just bunches them all together.
Like I said though, it isn't that big of a deal, but it would be nice to have some way to separate the locations of the import search paths between configurations. This is only a cosmetic issue.