ExecAsUser requires StdUtils.nsh, which doesn't exist.
Opened this issue · 5 comments
I'm trying to update your Discord app and then implement BetterDiscord, but it won't even compile with the current pacman.
Removing this requirement (thus assuming it uses StdUtils.dll in the Plugins dir) makes the compilation go further but still fails with the log looking like this
First of ail, which package are you trying to update? Is it my DiscordPortable packaged with my Pac-Man Development Version or is it using the stable/standard version?
You also might want to check the following in the DiscordLauncher.ini file
[Activate]
ExecAsUser=true
If you're still having trouble I'd like for you to give me an archive (preferably in 7-zip format) of the DiscordPortable root folder.
I am using the latest DiscordPortable from your master branch.
All of my original attempts were originally made with the stable version that you've updated recently. However I just spent some time with the dev version, and after it converted the PAF-formatting to the PAC-dev formatting, the compilation failed with the same exact error as the stable branch:
(macro:!ECHO:3)
!include: could not find: "StdUtils.nsh"
Error in script "C:\Users\Snow\loc\sync\app\c\virt\PAF\PACManDev\etc\source\PortableAppsCompiler.nsi" on line 120 -- aborting creation process
ERROR: MakeNSIS exited with status code 1
Neither PAC nor eventhe PAF-Launcher includes StdUtils.nsh.
As for the DiscordPortable, its configuration is nearly untouched. I updated the base program files and configuration files to their latest versions, but that's when my progress came to a halt.
I just downloaded a fresh copy of each latest builds of my Discord Portable and both branches of Pac-Man. I ran Discord Portable under both variants of Pac-Man and each completed the compilation without any errors..
If what you say is true then you shouldn't have any issues with compiling it with either branches whatsoever on your end as well. However, as it happens a lot of the time, we forget what we've done in our journey of programming enlightenment and things elude our prefrontal cortex from time to time. In short—maybe you just forgot something you did. No big deal.
So to get to the bottom of this issue, I'd like to see your Discord Portable folder and it's contents in a 7-zip archive please. Upload this archive to your Google Drive or OneDrive or whatever cloud your prefer and grant me access to the archive so I can download it and review your work. If you're uncomfortable with that then I do not see what else I can do to help you any further.
EDIT:
If you navigate to the folder named Plugins in the Source directory in the standard Pac-Man or the folder Plugins in the etc directory in the Dev version you shall find that both variants of the Standard Utilities plugin is indeed included in Pac-Man.
..\PortableAppsCompiler\Other\Source\Plugins\StdUtils.dll
or
..\PortableAppsCompiler\etc\source\Plugins\StdUtils\StdUtils.dll
I'm sure with just a little troubleshooting on your part, you could have figured that out on your own. Stop being lazy.
Thanks for the kind comments, but you've only pointed out that the .dll is there. Searching further into that specific error with makensis.exe shows people getting it when the executable is on a non-ascii path. I moved everything to a new folder (C:\temp) and ran it again and it yielded then same error. The fact that a clean version runs fine on your end but not mine doesn't mean I "forgot to do X" . Instead, it's probably some Windows causing this to not run properly.
Is there something on Window's PATH envvar that could potentially be causing this? I had an issue with mediaautobuildsuite that caused it to call a separate Python installation, causing it to fail to build despite it running in a virtual MinGW64 environment within the program's folder. Temporarily renaming my primary Python folder allowed it to run flawlessly. Maybe it's a similar problem. Regardless, I don't know what the specific cause of this is, so I may just do a fresh Windows 11 upgrade to hopefully sort this all out.
@snowbie If you haven't already noticed I've updated my Discord Portable to incorporate BetterDiscord. Let me know if that works for you.