Set path for Wix Toolset in windows runner #27149

hibearpanda · 2021-01-11T01:20:41Z

hibearpanda
Jan 11, 2021

I am trying to automate building a Windows MSI Installer for an electron application using Wix.

I can see from looking here that the Wix Toolsets are included in the windows-latest runner.

However, it seems like electron-wix-msi requires having candle.exe and light.exe available in the path. Without the candle.exe and light.exe available in the path, my build step will fail with the following message:

Screenshot 2021-01-11 at 9.19.49 AM1704×472 88.3 KB

My research also lead to this post, but the answer there uses add-path which has since been deprecated.

I have 2 questions:

What is path to the wix toolset binaries? How can I access this in the run step? ($wix, ${env.wix}?)
How can I add-path to the wix toolset so that it will be available at a later run step?

Appreciate any help I can get!

Answered by hibearpanda

Jan 12, 2021

Hi @thomasshaped,

Thanks for replying. I was able to figure out how to add path but for some reason could not add the wix binaries to the path without hardcoding the path, instead of using env.wix. I have included a gist of list of my latest workflow here, but in summary:

Worked

      - name: Set path for candle and light
        run: echo "C:\Program Files (x86)\WiX Toolset v3.11\bin" >> $GITHUB_PATH
        shell: bash

Did not work:

      - name: Set path for candle and light
        env:
          WIX_PATH: ${{ env.wix }}
        run: echo "$env:WIX_PATH" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append

      - name: Set path for candle and light
        env:
          WI…

View full answer

otter-computer · 2021-01-11T14:38:47Z

otter-computer
Jan 11, 2021

Hi @hibearpanda, welcome to the GitHub Support Community!

The ::add-path command has been replaced with an environment file, so you’d add something to your path using this syntax: echo "/your/path/here" >> $GITHUB_PATH

docs.github.com

Workflow commands for GitHub Actions - GitHub Docs

//docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions

That said, I believe the wix toolset should already be installed by default and available in the path at env.wix, so this is rather strange. Would you be able to share a link to your workflow, or copy paste it in a public gist or something so I can take a look at exactly what it does?

0 replies

hibearpanda · 2021-01-12T01:32:52Z

hibearpanda
Jan 12, 2021
Author

Hi @thomasshaped,

Thanks for replying. I was able to figure out how to add path but for some reason could not add the wix binaries to the path without hardcoding the path, instead of using env.wix. I have included a gist of list of my latest workflow here, but in summary:

Worked

      - name: Set path for candle and light
        run: echo "C:\Program Files (x86)\WiX Toolset v3.11\bin" >> $GITHUB_PATH
        shell: bash

Did not work:

      - name: Set path for candle and light
        env:
          WIX_PATH: ${{ env.wix }}
        run: echo "$env:WIX_PATH" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append

      - name: Set path for candle and light
        env:
          WIX_PATH: ${{ env.wix }}
        run: echo "$env:WIX_PATH\bin" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append

1 reply

erkstruwe Dec 8, 2023

It actually works using the WIX environment variable, too:

- name: Add WiX toolkit to PATH
  shell: bash
  run: echo "${WIX}bin" >> $GITHUB_PATH

otter-computer · 2021-01-12T12:30:13Z

otter-computer
Jan 12, 2021

Oh nice, good to see you got it working! I also did some testing yesterday with some of my team members and ended up getting it to work via this method (though I don’t think this is a nice way to do it, it feels rather hacky):

      - run: |
          $env:Path += ";C:\Program Files (x86)\WiX Toolset v3.11\bin"
          light.exe

It’s still very strange that they’re not available by default nor via using the preset env. Perhaps this is something to do with the specific env reference syntax differences between different shells used as I see you’ve managed to get it to work specifically when using bash.

I think I’m going to ask up the chain to see if they have any advice on this, but for now I’m at least glad you’ve managed to find solution!

0 replies

hibearpanda · 2021-01-12T13:31:21Z

hibearpanda
Jan 12, 2021
Author

Yea, it is a bit strange that it was not available in the path. Certainly stranger that it’s not (seemingly) available with env.wix. I would have preferred to construct that path with env.wix so it isn’t hard coded but alas I have to move on.

Appreciate your help and for asking around!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Set path for Wix Toolset in windows runner #27149

{{title}}

Replies: 4 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

GitHub Community

Set path for Wix Toolset in windows runner #27149

hibearpanda Jan 11, 2021

Replies: 4 comments · 1 reply

otter-computer Jan 11, 2021

Workflow commands for GitHub Actions - GitHub Docs

hibearpanda Jan 12, 2021 Author

erkstruwe Dec 8, 2023

otter-computer Jan 12, 2021

hibearpanda Jan 12, 2021 Author

hibearpanda
Jan 11, 2021

Replies: 4 comments 1 reply

otter-computer
Jan 11, 2021

hibearpanda
Jan 12, 2021
Author

otter-computer
Jan 12, 2021

hibearpanda
Jan 12, 2021
Author