Wix command not recognised (Wix toolset 3.11.2 is installed)

@Michael_Oborne I’m trying to make a Mission Planner MSI but Wix is playing funny buggers.
The build went fine in VS. I built Mission Planner and Wix solutions.

When I install Wix toolset 3.11.2 using the exe from here,

The 'Mission Planner/msi/install bash script errs, saying ‘wix’ is not a valid command. I made sure to add the Wix install folder to my path, but looking in the install folder, there is no executable called ‘wix’.

I tried installing Wix with dotnet tool. That installs 5.0.1. Now the bash script identifies the ‘wix’ command, but it throws unexpected argument ‘…/bin/release’

Am I missing something?

Bonus question:
In the meantime I made an installer using WinRAR, which works great, but I’m guessing this only works because I already have the SiK radio drivers installed. Would it not work on a fresh computer, or would the WinRAR installer grab those drivers too?

Thanks in advance!
Patrick

in Mission Planner source root run build.bat
then go to msi folder
run installer.bat
run create.bat

Hmm, when I run ‘installer.bat’ after running ‘build.bat’ it still says ‘wix.exe’ is not recognized as an internal or external command,
operable program or batch file.’ , and never creates ‘create.bat’

This is a screenshot of the terminal after running ‘build.bat’, does this provide any insight?

did you add wix to the path ?

C:\Program Files (x86)\WiX Toolset v3.14\bin\x86

I’ve put that folder in the path, but there’s no executable called Wix in that folder

I installed 3.11.2. should I use 3.14?

3.14 yes
If wix.exe is not found the build did not built it.
With the path set try build again.

I cleaned and built again with C:\Program Files (x86)\WiX Toolset v3.14\bin\x86 in the path, and it still didn’t work, but then I noticed that the output from building the wix solution in VS had the following lines:

 Build started: Project: wix, Configuration: Release Any CPU ------
1>wix -> C:\Users\Patrick\Documents\MissionPlanner\Msi\net472\wix.exe
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

So I added that to my path, and now everything works! I built an MSI and installed it, and it works great, thanks for your help!