Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easily configurable system header locations on Windows. #18

Open
mheinsen opened this issue Dec 1, 2016 · 2 comments
Open

Easily configurable system header locations on Windows. #18

mheinsen opened this issue Dec 1, 2016 · 2 comments
Assignees

Comments

@mheinsen
Copy link
Contributor

mheinsen commented Dec 1, 2016

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

@mheinsen mheinsen self-assigned this Dec 1, 2016
@mheinsen
Copy link
Contributor Author

mheinsen commented Dec 1, 2016

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.

@mheinsen
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant