diskofish
14th July 2008 18:25 UTC
makensisw - compiles, makesnsis - does not
Makensw: Compiles sucesfully.
Makensis: does not compile, a plugin DLL is not loaded
Processing plugin dlls: "C:\Program Files\NSIS\Plugins\*.dll"
- AdvSplash::show
- Banner::destroy
- Banner::getWindow
- Banner::show
- BgImage::AddImage
- BgImage::AddText
- BgImage::Clear
- BgImage::Destroy
- BgImage::Redraw
- BgImage::SetBg
- BgImage::SetReturn
- BgImage::Sound
- Dialer::AttemptConnect
- Dialer::AutodialHangup
- Dialer::AutodialOnline
- Dialer::AutodialUnattended
- Dialer::GetConnectedState
- FontName::name
- FontName::version
- InstallOptions::dialog
- InstallOptions::initDialog
- InstallOptions::show
- LangDLL::LangDialog
- Math::Script
- NSISdl::download
- NSISdl::download_quiet
- Splash::show
- StartMenu::Init
- StartMenu::Select
- StartMenu::Show
- System::Alloc
- System::Call
- System::Copy
- System::Free
- System::Get
- System::Int64Op
- System::Store
- TypeLib::GetLibVersion
- TypeLib::Register
- TypeLib::UnRegister
- UserInfo::GetAccountType
- UserInfo::GetName
- UserInfo::GetOriginalAccountType
- VPatch::vpatchfile
- nsDialogs::Create
- nsDialogs::CreateItem
- nsDialogs::GetUserData
- nsDialogs::OnBack
- nsDialogs::OnChange
- nsDialogs::OnClick
- nsDialogs::OnNotify
- nsDialogs::SelectFileDialog
- nsDialogs::SelectFolderDialog
- nsDialogs::SetUserData
- nsDialogs::Show
- nsExec::Exec
- nsExec::ExecToLog
- nsExec::ExecToStack
....
Invalid command: FindProcDLL::FindProc
Error in script
---
Anyone have any ideas why it isn't loading FindProcDLL.dll? I even copied it to the working folder.
kichik
14th July 2008 18:37 UTC
It doesn't look in the working folder. It looks in ${NSISDIR}\Plguins.
diskofish
14th July 2008 18:57 UTC
Kichik,
Right, is there any way with the command line to add the search dir? Here is what's in the plugins dir. What I don't get is why it would be different from the GUI than the CLI.
Here's whats in my plugins folder. The DLL is in there.
Directory of C:\Program Files\NSIS\Plugins
07/14/2008 01:55 PM <DIR> .
07/14/2008 01:55 PM <DIR> ..
07/14/2007 11:12 AM 6,144 AdvSplash.dll
07/14/2007 11:12 AM 4,096 Banner.dll
07/14/2007 11:12 AM 7,168 BgImage.dll
07/14/2007 11:12 AM 3,584 Dialer.dll
06/02/2004 08:31 PM 31,744 FindProcDLL.dll <-- the DLL it doesn't seem to be loading
02/10/2004 09:53 AM 8,704 FontName.dll
07/14/2007 11:12 AM 14,336 InstallOptions.dll
07/14/2007 11:12 AM 5,120 LangDLL.dll
07/14/2007 11:12 AM 67,584 Math.dll
07/14/2007 11:12 AM 7,168 nsDialogs.dll
07/14/2007 11:12 AM 6,144 nsExec.dll
07/14/2007 11:12 AM 14,848 NSISdl.dll
07/14/2008 01:55 PM 0 result.txt
07/14/2007 11:12 AM 4,096 Splash.dll
07/14/2007 11:12 AM 7,168 StartMenu.dll
07/14/2007 11:12 AM 10,240 System.dll
07/14/2007 11:12 AM 3,584 TypeLib.dll
07/14/2007 11:12 AM 4,096 UserInfo.dll
07/14/2007 11:12 AM 7,680 VPatch.dll
19 File(s) 213,504 bytes
2 Dir(s) 255,848,202,240 bytes free
kichik
14th July 2008 19:02 UTC
!addpluginsdir
diskofish
14th July 2008 19:22 UTC
Originally posted by kichik
!addpluginsdir
Kichik, thanks for the help. It works now.
I tried the
!addplugindir macro (no s), and created a folder called C:\Program Files\NSIS\Plugins_3rdParty and it worked.
I think it should load whatever you put in the plugins folder, but oh well.
LoRd_MuldeR
14th July 2008 22:26 UTC
Originally posted by diskofish
Kichik, thanks for the help. It works now.
I think it should load whatever you put in the plugins folder, but oh well.
From all me experience NSIS
will load plugin DLL's from the "${NSISDIR}\Plugins" folder. Putting custom plugins there works fine for me. NSIS only won't search the working directory (the directory where your .nsi script is located) for plugins, unless you add it via !addpluginsdir preprocessor command...