You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clang has different methods for finding system headers based on the environment used on Windows (e.g. mingw, msys, visual studio). At least for the case that we usually test with (mingw), we require PATH to be set correctly also (i.e. gcc.exe must be in the path, and the headers must be in the correct location relative to gcc.exe's location). Rather than require users to correctly setup their command line environment, and specify the correct target (if they are using something other than our expected default), it would be nice if these options and paths could be configured through the trace viewer's preferences.
There is more trouble here than first appears. To use the x86_64-windows-msvc target, SeeC must be updated to work correctly with MSVC's LINK. See #62.
At least for the MinGW targets, the location of gcc.exe can be set through seec-view's GUI now. However, it's only used when invoking the compiler from within seec-view.
From @mheinsen on March 17, 2016 8:37
Clang has different methods for finding system headers based on the environment used on Windows (e.g. mingw, msys, visual studio). At least for the case that we usually test with (mingw), we require PATH to be set correctly also (i.e. gcc.exe must be in the path, and the headers must be in the correct location relative to gcc.exe's location). Rather than require users to correctly setup their command line environment, and specify the correct target (if they are using something other than our expected default), it would be nice if these options and paths could be configured through the trace viewer's preferences.
Copied from original issue: mheinsen#58
The text was updated successfully, but these errors were encountered: