The PA.com installer (all versions that I've seen) generates a warning when compiled:
unknown variable/constant "{SectionMain}" detected, ignoringThis is caused by the following line in function LeaveDirectory:
SectionGetSize ${SectionMain} $1 ;=== Space Required for AppThis can be fixed by moving the Section above the Functions, and changing the Section header to read:
Section "!App Portable (required)" SectionMain
Is there a reason this hasn't been or shouldn't be done?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
There is (or at least was on last check) a bug in NSIS that causes a long 60 second+ wait when you move it above in certain instances on the installation end. Besides, it's just a warning.
Sometimes, the impossible can become possible, if you're awesome!
Ok, thanks. I'll play around with it and see if that's still the case.
I know it's just a warning, but I was taught to treat all warnings as errors unless they're the fault of the compiler so it was bugging me. If that wait still happens that would qualify as compiler error and placate the little professor that sits on my shoulder and yells at me when my code is sloppy.
formerly rayven01
It does indeed still seem to be an issue. With the section moved above the functions the installer pauses for a noticable while after you hit the 'Install' button.. so long that I actually hit 'Install' again and caused the installer to freak out and declare itself corrupt! Thanks for the tip, I probably wouldn't have tied the two things together otherwise.
formerly rayven01