Repository navigation
WIP: gypify msi build - #530
piscisaureus wants to merge 1 commit into
Conversation
dd981d0 to
4220fa3
Compare
|
I got stuck on finding a good way of incorporating code signing (signtool.exe) into the build. |
|
@piscisaureus what's the problem? it can't just be a separate, intermediate target prior to wix? |
That's the way to go indeed. However I didn't find a way to integrate this windows-only step nicely without affecting all the other platform builds.
|
|
Any progress here, or should I close this as stale? |
There was a problem hiding this comment.
If WIX is not there in the dictionary we will get NoneType doesn't have ... error. It's better to fail with KeyError in that case.
|
@piscisaureus ... What do you want to do with this one? |
|
It seemed like a neat idea to put all (windows) build steps inside gyp files, instead of spread out over gyp, a windows batch file, WiX. But I got stuck because I couldn't figure out how to do certain steps with gyp (e.g. signing the Currently I'm not working on this - feel free to close if you think it's not a priority. |
|
@nodejs/build |
|
/cc @nodejs/platform-windows |
|
Not sure if this a priority, though it's an interesting idea 😄 The main reason for using gyp is to generate projects for different platforms / build systems. Since MSI is 100% Windows-specific, dealing with Wix/MSBuild files directly actually seems easier to me. |
|
Marked as stalled. If there's no activity in the next few weeks I'll go ahead and close. |
|
Closing due to lack of activity. |
Does not work yet