trixom
16th April 2008 09:38 UTC

Howto create a 64bit custom plugin
Hi all,

I am trying to use a custom plugin from my nsis script that is called used for both 32 bit and 64 bit machines.

During installation on a 64 bit machine the plugin is not installed in the TEMP directory so it is not called (I have not determined why this is happening). The other default plugins (language and so on) are installed correctly.

My solution was to use two plugins for 32 and 64:

${If} ${RunningX64}
CUSTOM_PLUGIN_64::Run
${Else}
CUSTOM_PLUGIN_32::Run
${EndIf}

But because I am compiling the script on a 32 bit machine it fails during compiliation as the Run function in CUSTOM_PLUGIN.dll cannot be accessed.

1. Is this possible or do I need to create two installers...

2. Is there a way to disable the initial check so it doesnt fail the installation?

3. Another solution?

Thanks,

Tom

goldy1064
16th April 2008 16:18 UTC

Your installer should be a 32-bit process. Therefore, you cannot load a 64-bit DLL into your 32-bit process. You may only load a 64-bit plugin if you have managed to compile your installer as a 64-bit process, which I don't think NSIS supports out-of-box.

trixom
17th April 2008 13:23 UTC

It would be ok if I could figure out why my 32bit plugins don't show up in the temporary folder when installed on a 64bit system...

T.