Channels
doorman
infrastructure
random
zercurity
community-feeds
fleet-dev
code-review
queryhub
apple-silicon
carving
tls
fim
goquery
zentral
aws
querycon
golang
zeek
file-carving
fuzzing
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
darkbytes
process-auditing
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
general
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
windows
Title
a
asparamancer
08/27/2019, 3:50 PMI've been trying to build an msi for windows with a pre-written config. There seem to be references to a windows provisioning file (and it's available on the readthedocs.io) but then some of the files it references are no longer there. Has the process for building a windows msi changed, and is it documented anywhere?
m
Mike Myers
08/28/2019, 4:52 AMI think the MSI-building script needs to be updated, but in the interim there's a way to build the package using CMake, and I just opened this PR about it https://github.com/osquery/osquery/pull/5731
And https://github.com/osquery/osquery/pull/5733 is my attempt to fix the PS1 script (pending review), if Ed wants to try that
a
asparamancer
08/28/2019, 1:36 PMthank you @Mike Myers will give it a try later and let you know, and very speedy!
a
Arpful
08/28/2019, 11:09 PMThe struggle was REAL. lol.
Download the Wix Toolkit.
Create a link between C:\wix311 and where your actual Wix311 folder is. This will save you as it expects your Wix311 folder to be outside the default install location. Install "Make" too. Get all your flags in order and give it a shot. The PS1 always failed for me during certain phases of it.
m
Mike Myers
08/29/2019, 8:37 PMWhat component expects the Wix311 folder to be outside the default? In my setup, I let Chocolatey install it to where it wanted to. It was just that I had to add it to the PATH system env variable.
If you know where
make_windows_package.ps1👍 1