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

Temp fix for #4359 #4573

Merged
merged 4 commits into from
Nov 9, 2018
Merged

Temp fix for #4359 #4573

merged 4 commits into from
Nov 9, 2018

Conversation

Neumann-A
Copy link
Contributor

Fixes #4359 and also reenables the use of the llvm toolset in cmake if user wide integration has been installed

Neumann-A and others added 4 commits October 26, 2018 10:48
…oolset.

(e.g. cmake -G "VS" -TLLVM fails to even find compiler due to linker issues)
fixes microsoft#4359 but might have side effects for that toolset.
(e.g. not automatically adding dependencies)
@ras0219-msft ras0219-msft merged commit 4f7d4dc into microsoft:master Nov 9, 2018
@ras0219-msft
Copy link
Contributor

Thanks for the PR!

dantti pushed a commit to dantti/vcpkg that referenced this pull request Nov 9, 2018
* make user wide integration not burn everything if LLVM is used as a toolset.
(e.g. cmake -G "VS" -TLLVM fails to even find compiler due to linker issues)
fixes microsoft#4359 but might have side effects for that toolset.
(e.g. not automatically adding dependencies)

* remove whitespaces

* [vcpkg-integrate] Conform to MSBuild conventions for comparisons
@Neumann-A Neumann-A deleted the vcpkg_4359 branch June 3, 2019 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants