NSIS使用System::Call调用自定义dll中的导出函数

原创 2013年01月24日 19:46:29

看NSIS的说明中关于System的部分


D.3 Calling an external DLL using the System.dll plug-in

Some install processes are required to call functions contained inside third party DLLs. A prime example of this is when installing a Palm(TM) conduit.

Some background about System.dll
The System.dll plug-in (by Brainsucker) enables calling of external DLLs by providing the 'Call' function. There are a number of other functions provided by System.dll, but they will not be covered here. For more details about the other functions, lock the doors, take the phone off the hook, screw your head on *real* tight and head on over to the System readme.

Data Types
System.dll recognises the following data types:

  • v - void (generally for return)
  • i - int (includes char, byte, short, handles, pointers and so on)
  • l - long & large integer (known as int64)
  • t - text, string (LPCSTR, pointer to first character)
  • b - boolean (needs/returns 'true':'false') - by the fact this type is senseless -> usual integer can be used ('0':'1')
  • k - callback. See Callback section in system.html.
  • * - pointer specifier -> the proc needs the pointer to type, affects next char (parameter) [ex: '*i' - pointer to int]

Mapping System.dll variables to NSIS script variables
There's not much point in being able to call an external function if you can't get any data back. System.dll maps function variables to NSIS script variables in the following way:

NSIS $0..$9 become System.dll r0..r9 NSIS $R0..$R9 become System.dll r10..r19

Each parameter is specified by type, input and output. To skip input or output use a dot. Examples:

String (pointer to a characters array), input is 'happy calling':

t 'happy calling'

String (pointer to a characters array), input is taken from $5 and changes to the array made by the call are saved into $R8:

t r5R8

Pointer to an integer, value taken from $1 and put into $2:

*i r1r2

Pointer to a 64-bit integer, output pushed on stack, no input:

*l .s

Using System.dll::Call To call a function in a third party DLL, the Call function is used like this:

System::Call 'YourDllName::YourDllFunction(i, *i, t) i(r0, .r1, r2) .r3'

The '(r0, .r1, r2) .r3' section at the end are the parameters that are passed between your DLL and your NSIS script. As can be seen in this parameters list type and input/output can be seperated. Each block of "(parms list) return value" overrides and/or adds to the last one. In this case, the first block specifies the types and the second specifies input and output.

Before starting to code the NSIS script
Before you start to code any NSIS code, you need to know the full prototype of the function you are going to call. For the purposes of this example, we will use the 'CmGetHotSyncExecPath' function from the Palm 'CondMgr.dll'. This function is used to return the full path of 'HotSync.exe'.

Function Definition

int CmGetHotSyncExecPath(TCHAR *pPath, int *piSize);

where

  • pPath is a pointer to a character buffer. Upon return, this is the path & file name of the installed HotSync manager.
  • piSize is a pointer to an integer that specifies the size (in TCHAR's), of the buffer referenced by the pPath parameter.

return values:

  • 0: No error
  • -1: A non-specific error occurred
  • ERR_REGISTRY_ACCESS(-1006):Unable to access the Palm configuration entries
  • ERR_BUFFER_TOO_SMALL(-1010): The buffer is too small to hold the requested information
  • ERR_INVALID_POINTER(-1013):The specified pointer is not a valid pointer

Also, if the buffer is too small the value in *int is the size (in TCHARs) that the buffer should be.

This function definition maps to the following System.dll definition:

CmGetHotSyncExecPath(t, *i) i

i.e. It takes a text variable, a pointer to int, and returns an int value.

Using the external dll function
Now that we've sorted out what the function does, and how it maps to the System.dll format, we can use the function in a NSIS script.

First, you have to change the output directory to that where the DLL you want to use is. It may also work if the DLL is on the system path, but this hasn't been tested.

The following code fragment will install 'condmgr.dll' to a temporary directory, execute the CmGetHotSyncExecPath function and display returned data. Save this script

; **** snip ****
Function loadDll

  SetOutPath $TEMP\eInspect             ; create temp directory
  File bin\CondMgr.dll                  ; copy dll there
  StrCpy $1 ${NSIS_MAX_STRLEN}          ; assign memory to $0
  System::Call 'CondMgr::CmGetHotSyncExecPath(t, *i) i(.r0, r1r1).r2'
  DetailPrint 'Path: "$0"'
  DetailPrint "Path length: $1"
  DetailPrint "Return value: $2"

FunctionEnd
; **** snip ****

and this function produces the following output in the 'details' page:

Output folder: c:\windows\TEMP\eInspect
Extract: CondMgr.dll
Path: "C:\Dave\palm\Hotsync.exe"
Path length: 24
Return value: 0

Written by djc


总结

) dll的到处函数用extern "C" 形式的,不加WINAPI貌似不会出错,用def或者_declspc命令好像都行

)如果想调用后就卸载dll,注意参数 ? u

Function un.MyRemoveData
SetOutPath $INSTDIR
StrCpy $1 ${NSIS_MAX_STRLEN}
System::Call 'MiPlugin4NSIS::MiPIGetDataPath(t, *i) i(.r0, r1r1).r2 ? u'
IntCmp $2 0 +1 skiprmdir
RMDir /r "$0"
skiprmdir:
FunctionEnd
 'MiPlugin4NSIS::MiPIGetDataPath(t, *i) i(.r0, r1r1).r2 ? u'

 'MiPlugin4NSIS::MiPIGetDataPath(t, *i) i(.r0, r1r1).r2 ? u'

的解释

调用函数$INSTDIR目录中的MiPlugin4NSIS.dll的导出函数MiPIGetDataPath,函数参数类型为t(字符串), *i(int*),.r0(输出参数,放入$0中),r1r1(第二个参数为输入输出参数,已经放在了$1中),.r2(函数调用返回值放入$2中),? u(调用完成后立即卸载dll)

) 关于参数中的字符串。。。有人说是char*的,但是我的NSIS为Unicode版本的,经过测试字符串类型为wchar_t*。。。非Unicode版本为啥还需要测试


NSIS System Plug-in

Copyright © 2002 brainsucker (Nik Medved) Copyright © 2002-2016 NSIS Contributors Table of Content...
  • xringm
  • xringm
  • 2016年08月09日 11:27
  • 527

NSIS进阶教程(一)~(五)

这问是在学NSIS的时候发现的,一篇绝顶好文,当时没转过来,现在美化完程序了,想着不美化安装包也太不厚道了点。。。所以。。。 NSIS进阶教程(一) 来自:http://www.pylife.net...
  • taiyang1987912
  • taiyang1987912
  • 2014年10月27日 13:41
  • 25863

NSIS listbox使用技巧

1) 删除节点 ${NSD_LB_DelString} 存在bug,作者没有仔细研究windows message的要求。写成了这个样子SendMessage ${CONTROL} ${LB_DELE...
  • pkrobbie
  • pkrobbie
  • 2009年08月03日 13:50
  • 1471

NSIS System.dll调用其他dll(例调海康SDK取板卡序列号)

System::Call 'F:\Ds40xxSDK::InitDSPs() i().r0' ;初始化芯片,函数: int __stdcall InitDSPs() Sy...
  • z3642214
  • z3642214
  • 2011年10月15日 09:50
  • 1590

分析system_call中断处里过程

孙业毅 原创作品 转载请注明出处 《Linux内核分析》MOOC课程:http://mooc.study.163.com/course/USTC-1000029000 第五讲 扒开系统调用的三层...
  • sunyeyi
  • sunyeyi
  • 2015年04月05日 11:35
  • 1004

NSIS自定义dll扩展

NSIS是一个功能强大的安装卸载包制作工具,通过dll可以扩展很多功能,你也可以自定义一个dll,以下是具体步骤: 1.新建一个mfc dll(本例Hello.dll) 1.1 添加对nsis库的...
  • xwlyun
  • xwlyun
  • 2014年01月03日 10:43
  • 1801

NSIS学习笔记(二)-使用C++开发NSIS插件

Q 如何使用C++开发插件,示例 环境:VS2013Update4 参考资料[3]来做 S1:新建一个空的C++DLL项目,nsMessageBoxPlugin. S2:复制“C:\Program F...
  • lee353086
  • lee353086
  • 2015年06月03日 17:52
  • 4211

NSIS脚本源码分析: 如何判断CPU平台类型

做安装程序时,有时需要支持多个CPU平台。Windows下支持的CPU平台一般有三大类:x86, x64和ia64。其中,x86就是我们最常用的32位平台,x64则是64位的x86平台,ia64比较特...
  • jally
  • jally
  • 2010年01月12日 16:24
  • 2326

NSIS简介

NISI打包工具简单记录
  • csxiaoshui
  • csxiaoshui
  • 2015年05月07日 18:16
  • 5497

NSIS-DLL安装技巧

B.1 Introduction The Library header file can be used to setup dynamic link libraries (DLL) and ty...
  • qinwei4072880
  • qinwei4072880
  • 2014年09月05日 16:07
  • 1428
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:NSIS使用System::Call调用自定义dll中的导出函数
举报原因:
原因补充:

(最多只允许输入30个字)