Pixi Windows failing in CI

[facontidavide]

@tony-p , any suggestion?

I am not sure what the error is

[tony-p]

From looking at the error message my best guess would be something has changed in the path or how to specify the temporary environment variable.

If I remember correctly this was needed on windows as the test executable and library were in different folders compared to the linux build.

When i get a chance I can try take a look if still stuck.

if you aren’t against it, it would probably be more robust to create a pixi.toml file in the repo so it can be used as pixi project and then CI wouldn’t have to try set it all up on the fly.

it would just live alongside the ros and conan files giving another way to interact with the project

[facontidavide]

go ahead with any modification that you consider appropriate

[tony-p]

I have made a start here #791

This fixes the issue you encountered, but I see it now has linux build issues. I get these issues with my ROS builds and is to do with the sqlite and zeromq not being added to the rpath properly (Conda environments lean very heavily on the rpath of binaries).

Locally on windows I get Json warnings/errors when building and the json tests fail.

I can hopefully look into these very soon unless you know some direct solutions to add to the cmake. I think adding the dependency libraries as public already helps ....

[tony-p]

Making the ${BTCPP_EXTRA_LIBRARIES} does solve the linking issue on linux. On the PR both windows builds fail due to ambiguous symbol errors for a number of the JSON conversions.

[tony-p]

@facontidavide The PR above fixes all pixi build related issues. However both the windows and pixi windows builds fail for the new json conversion so have created a new issue #793

[facontidavide]

thanks a lot!!!!