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

VS2022 Win10 build fix #5806

Merged
merged 1 commit into from
Jun 29, 2024
Merged

Conversation

vovodroid
Copy link
Contributor

  • use DEPS variable for both deps and slicer build
  • use installed WinSDK version
  • echo real cmake command line

- use DEPS variable for both deps and slicer build
- use installed WinSDK version
- echo real cmake command line
echo cmake .. -G "Visual Studio 17 2022" -A x64 -DBBL_RELEASE_TO_PUBLIC=1 -DCMAKE_PREFIX_PATH="%DEPS%/usr/local" -DCMAKE_INSTALL_PREFIX="./OrcaSlicer" -DCMAKE_BUILD_TYPE=%build_type%
cmake .. -G "Visual Studio 17 2022" -A x64 -DBBL_RELEASE_TO_PUBLIC=1 -DCMAKE_PREFIX_PATH="%DEPS%/usr/local" -DCMAKE_INSTALL_PREFIX="./OrcaSlicer" -DCMAKE_BUILD_TYPE=%build_type% -DWIN10SDK_PATH="C:/Program Files (x86)/Windows Kits/10/Include/10.0.22000.0"
echo on
cmake .. -G "Visual Studio 17 2022" -A x64 -DBBL_RELEASE_TO_PUBLIC=1 -DCMAKE_PREFIX_PATH="%DEPS%/usr/local" -DCMAKE_INSTALL_PREFIX="./OrcaSlicer" -DCMAKE_BUILD_TYPE=%build_type% -DWIN10SDK_PATH="%WindowsSdkDir%Include\%WindowsSDKVersion%\"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the Windows SDK path/version being gotten from? If you are pulling it from the ENV variables set by CMake for the deps build, remember that the slicer can be build independently of the deps and vice versa

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's from x64 Native tool window environment, so it's set before BAT file is run.

Copy link
Contributor

@Ocraftyone Ocraftyone Jun 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only problem is if you don't run from that environment. Maybe check if the variables are initialized and if not set the current values as default?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually build instruction clearly says Run build_release.bat in x64 Native Tools Command Prompt for VS 2019 (applied to 2022 as well I guess).

@Ocraftyone
Copy link
Contributor

I understand the convenience having the command echo itself rather than having the command written out in the script twice, but I personally like the look of not having the user path before the command. I do have to admit that is just me being very nitpicky though 😄

@vovodroid
Copy link
Contributor Author

I personally like the look of not having the user path before the command.

It was included into echo before this PR, so I just eliminated copy-paste errors.

Copy link
Owner

@SoftFever SoftFever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice change
Thank you

@SoftFever SoftFever merged commit 409004d into SoftFever:main Jun 29, 2024
12 checks passed
@vovodroid vovodroid deleted the vs2022-build-fix-pr branch June 29, 2024 16:41
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.

None yet

3 participants