mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #277] Check to see if VS2019 works for building on windows. #224
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#224
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AdrianKoshka on GitHub (Apr 3, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/277
@noisyshape commented on GitHub (Apr 10, 2019):
clean_build.bat has a hard coded cmake generator string for VS2017 and there is no Qt library specifically for VS2019 yet. Changing
"Visual Studio 15 2017 Win64"to"Visual Studio 16 2019"allows for a successful build. I'm running the binaries as both client and server and they seem to be fine.@AdrianKoshka commented on GitHub (Apr 10, 2019):
You do get a clean build? Odd, I remember changing that and only getting errors.
@noisyshape commented on GitHub (Apr 10, 2019):
I get 3 warnings, but I think they're the same warnings I get with VS2017. The only other change I made was setting the Qt version to 5.12.2. Try building again off of master and post the errors if you get any.
@AdrianKoshka commented on GitHub (Apr 10, 2019):
Ah, I was building off tag
v2.1.2.@AdrianKoshka commented on GitHub (Apr 10, 2019):
A PR to update
clean_build.batto compile against vs2019 would be appreciated, if you want to that is.@noisyshape commented on GitHub (Apr 10, 2019):
Done. It looks like the Appveyor is getting a bad argument, however.
@AdrianKoshka commented on GitHub (Apr 10, 2019):
Appveyor has been broken for PRs.