如何将C/C++程序转译成Delphi(十四)

7.2. Dynamic Linking

Dynamic Linking is used to link the DLL at runtime.

Handling Static and Dynamic Linking in the Jedi Environment

Because both static and dynamic linking have their strengths, we must be prepared to support both techniques in the Jedi units. However, static linking is the default.

To support multiple methods compiler symbols are used. The two compiler symbols that symbolize dynamic linking are as follows:

If Xxxx_DYNLINK is defined the DLL must be linked dynamically at startup (in the initialization section).

If Xxxx_LINKONREQUEST is defined the DLL is linked dynamically, not at startup, but as needed by the user. Xxxx is the name of the API, e.g. MAPI_DYNLINK or MAPI_LINKONREQUEST.

If neither symbol is defined, static linking is used.

Each import unit should implement the following functions:

Function XxxxInitAPI: Boolean;

Procedure XxxxFreeAPI;

Function XxxxCheckAPI: Boolean;

The functions XxxxInitAPI and XxxxFreeAPI are available for the user if the symbol Xxxx_LINKONREQUEST is defined. The User can call this function to load or free the DLL. XxxxInitAPI returns TRUE, if the DLL has been loaded successfully.

If Xxxx_DYNLINK is defined, but not Xxxx_LINKONREQUEST, these functions are used internally to load or unload the DLL in the initialization section, but they are not available for the user.

The function XxxxCheckAPI returnes TRUE if the API is available, so the return value is TRUE if the DLL has previously been loaded successfully using XxxxInitAPI. When static linking is used, the return value is always TRUE.

Here is an example of how to handle the symbols in a translation:

unit apisample;
interface
USES Windows,
     JediUtil;
// There are two conditional defines. One to use dynamic
// run time linking with linking on startup, the other
// to link upon request. In fact the only difference is
// that the library is not loaded in the initialization
// section if the upon-request symbol is defined.
// Both symbols start with the name of the api, e.g. TAPI.
// In this example it is APISAMPLE.
// APISAMPLE_DYNLINK signals that the API should be linked
// via LoadLibrary and GetProcAddress at startup.
// APISAMPLE_LINKONREQUEST signals that the libary should
// not be linked at startup, but via an initialization procedure.
// Since most of the stuff is the same for both we use
// APISAMPLE_DYNLINK as common symbol.
{$IFDEF APISAMPLE_LINKONREQUEST}
  {$DEFINE APISAMPLE_DYNLINK}
{$ENDIF}
{$IFDEF APISAMPLE_DYNLINK}
// Define function types and variables for dynamic linking
TYPE
  TApiSampleFunc1 = Function (lParam: LongInt): LongInt; stdcall;
  TApiSampleFunc2 = Function (wParam: Word): LongInt; stdcall;

VAR
  ApiSampleFunc1 : TApiSampleFunc1 = NIL;
  ApiSampleFunc2 : TApiSampleFunc2 = NIL;
{$ELSE}
// We don't use dynamic linking so we implement static linking
Function ApiSampleFunc1 (lParam: LongInt): LongInt; stdcall;
Function ApiSampleFunc2 (wParam: Word): LongInt; stdcall;
{$ENDIF}
//
// Linking Control functions
//
// The XxxxInitAPI function follows <ApiName>InitAPI
// naming convention and is only visible if
// Xxxxx_LINKONREQUEST is defined. The same is true
// for the XxxxxFreeAPI function which frees the
// library
{$IFDEF APISAMPLE_LINKONREQUEST}

Function ApiSampleInitAPI: Boolean;
Procedure ApiSampleFreeAPI;
{$ENDIF}

// The XxxxxCheckAPI function returns true if
// the API is available. With static linking
// the function always returns TRUE
Function ApiSampleCheckAPI: Boolean;
implementation
CONST APISampleDLL = 'APISAMPLE.DLL'; // Name of the DLL
{$IFDEF APISAMPLE_DYNLINK}
VAR hDLL : THandle = 0; // Handle to the lib. Only req. for
                          dyn.link.
Function ApiSampleInitAPI: Boolean;
begin
  Result := FALSE;
  // Load library if necessary
  If hDLL = 0 then hDLL := LoadLibrary (APISampleDLL);
  If JediCheckInstanceHandle (hDLL) then
 begin
    // Set pointers to functions
    @ApiSampleFunc1 := GetProcAddress (hDLL, 'ApiSampleFunc1');
  @ApiSampleFunc2 := GetProcAddress (hDLL, 'ApiSampleFunc2');
    // Everything ok, return true
    Result := TRUE;
  end
end;
Procedure ApiSampleFreeAPI;
begin
  If hDLL <> 0 then
    FreeLibrary (hDLL);
  hDLL := 0;
end;
{$ELSE}
Function ApiSampleFunc1; external APISampleDLL name 'ApiSampleFunc1';
Function ApiSampleFunc2; external APISampleDLL name 'ApiSampleFunc1';
{$ENDIF}
Function ApiSampleCheckAPI: Boolean;
begin
  {$IFDEF APISAMPLE_DYNLINK}
  Result := hDLL <> 0;
  {$ELSE}
  Result := TRUE;
  {$ENDIF}
end;
initialization
begin
  {$IFDEF APISAMPLE_DYNLINK}
    {$IFNDEF APISAMPLE_LINKONREQUEST}
  // Call Init if dynamic linking and not link on request 
  ApiSampleInitAPI
    {$ENDIF}
  {$ENDIF}
end;
finalization
begin
 {$IFDEF APISAMPLE_DYNLINK}
  ApiSampleInitAPI;  // Call free if dynamic linking
  {$ENDIF}
end;
end.

You can use the the JediCheckInstanceHandle function from the common Jedi-support unit to check an instance handle if necessary.


Back to contents

8. The Jedi Common Support Unit

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
提供的源码资源涵盖了Java应用等多个领域,每个领域都包含了丰富的实例和项目。这些源码都是基于各自平台的最新技术和标准编写,确保了在对应环境下能够无缝运行。同时,源码中配备了详细的注释和文档,帮助用户快速理解代码结构和实现逻辑。 适用人群: 适合毕业设计、课程设计作业。这些源码资源特别适合大学生群体。无论你是计算机相关专业的学生,还是对其他领域编程感兴趣的学生,这些资源都能为你提供宝贵的学习和实践机会。通过学习和运行这些源码,你可以掌握各平台开发的基础知识,提升编程能力和项目实战经验。 使用场景及目标: 在学习阶段,你可以利用这些源码资源进行课程实践、课外项目或毕业设计。通过分析和运行源码,你将深入了解各平台开发的技术细节和最佳实践,逐步培养起自己的项目开发和问题解决能力。此外,在求职或创业过程中,具备跨平台开发能力的大学生将更具竞争力。 其他说明: 为了确保源码资源的可运行性和易用性,特别注意了以下几点:首先,每份源码都提供了详细的运行环境和依赖说明,确保用户能够轻松搭建起开发环境;其次,源码中的注释和文档都非常完善,方便用户快速上手和理解代码;最后,我会定期更新这些源码资源,以适应各平台技术的最新发展和市场需求。 所有源码均经过严格测试,可以直接运行,可以放心下载使用。有任何使用问题欢迎随时与博主沟通,第一时间进行解答!

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值