OK, I apologize. It seems that the problem lies elsewhere. The fact
that library initialization seems to be deferred until you do a
GetProcAddress() confused me. The problem is that function
GetModuleName() is stubbed out in WinCE (and Linux):
unit SysUtils.inc;
function GetModuleName(Module:
Am 12.06.2012 15:20 schrieb kyan alfasud...@gmail.com:
OK, I apologize. It seems that the problem lies elsewhere. The fact
that library initialization seems to be deferred until you do a
GetProcAddress() confused me.
It might't be that Windows (or CE only) initalizes a library only if you
use
Thank you for your reply Sven.
It might't be that Windows (or CE only) initalizes a library only if you use
GetProcAddress at least once... I have not tested that, but it might be an
idea. If that is the case we can not influence that.
No need to, it really doesn't matter since one has to do
On Tue, June 12, 2012 18:04, Sven Barth wrote:
Am 12.06.2012 15:20 schrieb kyan alfasud...@gmail.com:
.
.
The problem is that function
GetModuleName() is stubbed out in WinCE (and Linux):
unit SysUtils.inc;
function GetModuleName(Module: HMODULE): string;
begin
{$ifdef MSWINDOWS}
On 12.06.2012 18:27, Tomas Hajny wrote:
On Tue, June 12, 2012 18:04, Sven Barth wrote:
Am 12.06.2012 15:20 schrieb kyanalfasud...@gmail.com:
.
.
The problem is that function
GetModuleName() is stubbed out in WinCE (and Linux):
unit SysUtils.inc;
function GetModuleName(Module: HMODULE):
Hello all,
Does unit initialization in libraries (.dll files) work in arm/WinCE?
Somehow it seems that even code placed in the library initialization
begin end block isn't executed either. I found some bug reports (e.g.
0019404) suggesting that this didn't work for arm/Linux but it has
been added
Am 11.06.2012 12:25, schrieb kyan:
Does unit initialization in libraries (.dll files) work in arm/WinCE?
From the startup code of arm-wince I don't see why it should not work...
Somehow it seems that even code placed in the library initialization
begin end block isn't executed either.
How
