by Antonio Linares » Wed Nov 15, 2006 12:02 am
Bill,
We have been doing several tests and it looks as there are some troubles that we need to solve with the Harbour development team, so unfortunately we can not provide you a quick solution for this.
Basically this is what we have tested:
1. Copy buildce.bat to builddll.bat and modify it this way:
echo %1.obj %hdir%\obj\vc\maindll.obj > msvc.tmp
...
... link ... /DLL /ENTRY:DllEntryPoint
maindll.obj is not included in the Harbour for Pocket PC distribution, so we built it here. We may email it to you if you want to try it.
We are not exactly sure about link /ENTRY:DllEntryPoint flag behavior. Acording to Microsoft docs, it should not be needed as DllEntryPoint() may be called automatically, but that was not the case. So we need to force its call.
The DLL gets properly built and it loads fine, but the Harbour virtual machine is not properly initialized. So it seems there is a problem somewhere in the startup code of the DLL that we need to trace.