no msi about windows_exporter HOT 4 CLOSED

Hi @frankie64!
The installer is built using the installer/build.ps1 script. You can use that to build it locally, and check the AppVeyor configuration for some notes on how it is called.
Alternatively, you can start wmi_exporter with a number of flags on the commandline to customize its behavior. Try wmi_exporter.exe -help to get a listing of the available flags.

Hope this helps!

from windows_exporter.

Hi Carl,

thx for quick answer. I try to create a wmi_exporter. the build.ps1 stop after a while mit errormessage: wmi_exporter.wxs(36) : error LGHT0103 : The system cannot find the file 'Work\wmi_exporter.exe'.
in folder installer\Work I found a folder not a file wmi_exporter.exe.

do you have an idea?
~Frank

from windows_exporter.

Hi,
Hm, that is odd. How did you invoke build.ps1? In our automated builds, we do this:
.\installer\build.ps1 -PathToExecutable .\wmi_exporter.exe -Version $Version -Arch amd64

This assumes that the PathToExecutable parameter points to an existing .exe file, which you get from your go build.

from windows_exporter.

Hi,

Sorry, I missunderstand the Paramter PathToExecutable. I give him only the Path ;-(

thx
Frank

from windows_exporter.