Windows binary install with pixi

[knmcguire]

Desired behavior

The current binary installation instructions still only mention using conda, while the source installation mention the use of pixi . How about we add a pixi.toml file with all the right versions of the pixi.toml file included_

Alternatives considered

You can also consider providing a zip folder with the packages prebuilt like ros2 is doing. But if you have the nice conda packages already, why not take advantage of it!

Implementation suggestion

Find a good spot to place the version specific toml files (perhaps a repo in gazebo-tooling). Or have one master pixi.toml file to rule them all like this one? Just need to know where would be the best place to host this so that it can be pointed at from the doc, so that we can change the text there.

Additional context

[azeey]

Thanks for the issue @knmcguire. We do have pixi.toml files in https://github.com/gazebo-tooling/release-tools/blob/master/conda/envs/noble_like/pixi.toml since that's what we're using in our CI now. Perhaps all we need is to update the documentation to use pixi

[knmcguire]

Ah yes, but that pixi file you pointed fo is only to recreate all the dependencies as Ubuntu noble to be able to build the packages from source right? It does not include the packaged conda packages of each of the gazebo libraries itself (like in this gist)?

I'm not sure if that can be added to the same pixi file as it might conflict between the installed and build, but that can perhaps be separated by an special "dev" environment.

[azeey]

Oh, for installing binaries, wouldn't you just do pixi add gz-sim? Not sure if we need a toml file for that

[knmcguire]

Oh yeah that is true. All the others are noted as dependencies ofcourse... then the installation instructions will be pretty much:

1. install pixi
2. pixi add gz-sim (with different versions
3. pixi run gz sim
4. done!

Btw, I saw that I unfortunately still had the issue where I had to open up the gui and server separately on Jetty (gz-sim 10). I thought that I saw it working with ionic so not sure what went wrong... probably worth a separate ticket, or shall I just add those to the binary install instructions?