pixi not being found at the expected location at development setup

Beginner Questions
, ,
1

Hi,
I was trying to set up my local ITK for development on a Windows 10 machine following
Contribute to ITK - ITK's documentation.

I installed pixi using the MSI provided in their GitHub release page. It turns out that Windows chose the location below:

C:/Users/{username}/AppData/Local/pixi/bin/pixi.exe

for that. Not the best one, but it works: pixi -h shows the help on a terminal.

However, when executing:

./Utilities/SetupForDevelopment.sh

ITK is unable to find the pixi executable:


Utilities/GitSetup/setup-precommit: line 29: C:/SDKs/ITK/itk-head/ITK/.git/hooks/pixi/bin/pixi.exe: No such file or directory

I am not sure to understand why ITK looks for pixi within ITK’s source code directory:
ITK/Utilities/GitSetup/setup-precommit at main · InsightSoftwareConsortium/ITK · GitHub

There is no CMake variable telling where it can find it otherwise.

Anybody that has succeeded doing this has any suggestion?

Thanks.

2

Hi Jon Haitz,

Per the documentation, pixi does not need to be installed separately. A local version gets installed by ./Utilities/SetupForDevelopment.sh (which calls the setup-precommit script) to bootstrap pre-commit.

Perhaps adding:

set -x

to the setup-precommit script adds more information?

3

Thanks for the suggestion, Matt.

Here the relevant trace:

+ Utilities/GitSetup/setup-precommit
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Utilities/GitSetup/setup-precommit: line 29: C:/SDKs/ITK/itk-head/ITK/.git/hooks/pixi/bin/pixi.exe: No such file or directory
+ echo 'Failed to setup pre-commit.'
Failed to setup pre-commit.
+ echo

+ SetupForDevelopment_VERSION=11
+ git config hooks.SetupForDevelopment 11

The curl certificate issue was visible before, but I thought it was not relevant. Maybe I am wrong?