-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating a custom NSIS include #1231
Comments
LogicLib.nsh is not required to be added since it is already added by default. inetc is a part of installation since 13.3.0. base64 should be added explicitly, but you should not use one from https://github.com/nmoinvaz/nsis-base64 because it is not UNICODE build. But I guess you can try it. Build resources dir is added as
Did you get compilation error or build was successful? |
Build was successful. It installs successfully too and runs just fine. MixPanel isn't receiving the data though. I ended up using this Base64 script instead: http://nsis.sourceforge.net/Base64 I think next steps are:
Do you know how to go about doing those two things? Can I If I can see what the MixPanel response is I should be fine to go ahead and modify the parameters to meet their needs. From what I can tell, the call already matches the requirements of their documentation. |
To debug you can use |
I see that it is not correctly used in the script. result is not checked. To check result, in our scripts we use
i.e. write result from stack to var |
So I included a message box like this this:
And nothing pops up during installation. So I assume that needs to be figured out before moving on to check MixPanel's return value (although I did add in the Messagebox for the MixPanel call as well. |
I cannot check yet in code, but please try to move !include "mp.nsh" inside your macro |
Same issue, no Messagebox. Trying with only
The installer pops up with "Installing, Please Wait..." and the progress bar, but no Messagebox. Maybe there's something wrong with my package.json that's preventing installer.nsh from being included? Here's the
|
I will check tomorrow CET. |
Adding |
So I'm stuck now because when I do
the Do I need to add the extra files to the |
I was able to make progress but had to duplicate all of the macros with Has the same error as the person in #1239 where I had to turn off Right now I'm getting Will post back when I try again later tonight. |
I managed to get this to work with the I ended up using a different method to create a GUID:
and used this CharStrip to get rid of the brackets and the dashes. |
@sklink include dir fixed in the 13.6.0 |
@sklink 13.6.0 allows you to disable Unicode (#1165 (comment)), so you can use dll from https://github.com/nmoinvaz/nsis-base64 |
Thank you, this worked! Note to future people:
|
I'm trying to integrate this for install / uninstall analytics: https://github.com/nmoinvaz/nsis-mp
From what I've gathered so far,
build
in an includedir, so I can just add the file to thebuild
folder and write!include "mp.nsh"
to the top ofbuild/installer.nsh
and it'll include their script.Next I see that
nsis-mp
requires:LogicLib
script: http://nsis.sourceforge.net/LogicLibinetc
plugin: http://nsis.sourceforge.net/Inetc_plug-inbase64
plugin: https://github.com/nmoinvaz/nsis-base64The docs say
LogicLib.nsh
ships with NSIS so no problem there, just using!include "LogicLib.nsh"
at the top of themp.nsh
document. However, it seems the others need to be added.I cannot find
!addplugindir
anywhere in theelectron-builder
code and I don't know whether those plugins are already available withinelectron-builder
. Do I need to modify the main script to add these plugins or is there a method of doing it in thebuild/installer.nsh
file? (if it even needs to be done at all)The final step has been to create the custom macros in
build/installer.nsh
:I've been unable to figure out how to debug a NSIS installation. That alone will help me make progress. I'll update this as I make progress, but any help is appreciated. I can only afford a small donation but I'll throw one your way right away.
The text was updated successfully, but these errors were encountered: