Skip to content

BLD: MSVC portability #31

@lucascolley

Description

@lucascolley

@steppi are you still having to add extra args to the build invocation to make things work with VS2022?

I could reproduce the same error you had previously, but not anymore. I added some extra components to my VS installation, which might have made the difference. Here's my full list of components:

Image

Image

If I had to guess, MSVC v142 - VS 2019 C++ x64/x86 build tool... might be it.


Either way, it seems desirable to make things maximally portable across VS installations. It was suggested at https://discord.com/channels/1082332781146800168/1360605502169681940/1363258900261900350 to apply a diff like

diff --git a/pixi.toml b/pixi.toml
index 2be7f18..09bb43d 100644
--- a/pixi.toml
+++ b/pixi.toml
@@ -16,6 +16,10 @@ cmake = ">=3.30.5,<4"
 cxx-compiler = ">=1.8.0,<2"
 make = ">=4.4.1,<5"

+[feature.build.target.win-64.dependencies]
+vs2019_win-64 = "*"
+vs2022_win-64 = "*"
+
 [feature.build.tasks.configure]
 cmd = [
   "cmake",

and perhaps use ninja?

(It was also explained there that cxx-compiler is an alias for vs2019_win-64 on windows, which explains why CMake was expecting VS2019 in some sense. Thus the addition of vs2022_win-64 would perhaps be sufficient.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions