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

Add support for "-A" option #177

Closed
wants to merge 1 commit into from

Conversation

WopsS
Copy link
Contributor

@WopsS WopsS commented May 25, 2019

VS 2019 doesn't have the platform name in its name anymore, to generate the files for a specific platform you need to use "-A" option when invoking CMake.

VS 2019 doesn't have the platform name in its name anymore, to generate the files for a specific platform you need to use "-A" option when invoking CMake.
@d3x0r
Copy link
Contributor

d3x0r commented Oct 20, 2019

Nevermind; my error was solved by a reboot - inbetween updates...
Might still be useful :)

gjasny added a commit to gjasny/cmake-js that referenced this pull request Dec 13, 2019
The CMake Visual Studio 2019 Generator does not support the Win64
or ARM suffix on the generator name. Instead the generator platform
must be set explicitly via the platform parameter.

Before this patch the platform was not set at all which results
in CMake picking the host architecture. This obviously leads
to mismatches if a 32bit NodeJS is used on a 64bit Windows.

Right now the platform parameter is only applied for Visual
Studio 16 because cmake-js does not specify a minimum CMake
version. If at least CMake 3.1 (released December 2014)
would be required the platform selection code could be made
unconditional and thus forward-compatible with newer CMake
Visual Studio generators.

Thanks to @WopsS for cmake-js#177 which added platform parameter support.
gjasny added a commit to gjasny/cmake-js that referenced this pull request Dec 13, 2019
The CMake Visual Studio 2019 Generator does not support the Win64
or ARM suffix on the generator name. Instead the generator platform
must be set explicitly via the platform parameter.

Before this patch the platform was not set at all which results
in CMake picking the host architecture. This obviously leads
to mismatches if a 32bit NodeJS is used on a 64bit Windows.

Right now the platform parameter is only applied for Visual
Studio 16 because cmake-js does not specify a minimum CMake
version. If at least CMake 3.1 (released December 2014)
would be required the platform selection code could be made
unconditional and thus forward-compatible with newer CMake
Visual Studio generators.

Thanks to @WopsS for cmake-js#177 which added platform parameter support.
unbornchikken pushed a commit that referenced this pull request Feb 26, 2020
* Add support for "-A" option

VS 2019 doesn't have the platform name in its name anymore, to generate the files for a specific platform you need to use "-A" option when invoking CMake.

* Auto-detect VS2019 platform

The CMake Visual Studio 2019 Generator does not support the Win64
or ARM suffix on the generator name. Instead the generator platform
must be set explicitly via the platform parameter.

Before this patch the platform was not set at all which results
in CMake picking the host architecture. This obviously leads
to mismatches if a 32bit NodeJS is used on a 64bit Windows.

Right now the platform parameter is only applied for Visual
Studio 16 because cmake-js does not specify a minimum CMake
version. If at least CMake 3.1 (released December 2014)
would be required the platform selection code could be made
unconditional and thus forward-compatible with newer CMake
Visual Studio generators.

Thanks to @WopsS for #177 which added platform parameter support.

* Update documentation

Co-authored-by: Octavian Dima <WopsS@users.noreply.github.com>
@gjasny
Copy link
Contributor

gjasny commented Feb 26, 2020

This PR could get closed because PR #201 contained everything of it.

@WopsS WopsS closed this Feb 26, 2020
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

4 participants