Re: LDAP running on Window CE device always returning LDAP_LOCAL_E

Hi John:

Thank you for responding to my posting. The linking arguments were
basically generated by the New Project wizard in embedded VC++:

Wldap32.lib /nologo /base:"0x00010000" /stack:0x10000,0x1000
/entry:"wWinMainCRTStartup" /incremental:yes /pdb:"emulatorDbg/LDAPTest.pdb"
/debug /out:"emulatorDbg/LDAPTest.exe"
/libpath:"D:\WINCE420\PUBLIC\COMMON\OAK\LIB\X86\DEBUG"
/subsystem:$(CESubsystem) /MACHINE:IX86

I added Wldap32.lib, libpath, and pdb. Everything else was generated. On
the compilation side, I did add two directives; _WINLDAP_ and _WINBER_.
Without these settings the declspec(dllimport) dressings get added to the
compilation and the linker cannot find the these within Wldap32.lib. So,
there appears to possibly be a difference between Win32 PC and Win32 CE,
where CE requires the "old style" definition? I don't see why that would
matter, but it is a difference. Is there any conditions in DllMain()
DLL_PROCESS_ATTACH that could circumvent LdapClientInitialize?

Since I am able to debug into the ldap functions, I am concluding that the
DLL did load. So, maybe there is a condition that skips this Initialization?

Thank you,

David.
"John Spaith [MS]" wrote:

> Sorry you've been having so many problems with this, David, and good
> detective work. You should obviously not have to call the ldap_startup()
> routine. ldap_startup() just calls LdapClientInitialize().
> LdapClientInitialize should automatically be called wldap32.dll is loaded
> during the DllMain() DLL_PROCESS_ATTACH processing.
>
> So the question becomes why isn't the DllMain() being processed? This I do
> not know. Is it possible you did something really funky with the linker
> when linking to this library?
>
> --
> John Spaith
> Software Design Engineer, Windows CE
> Microsoft Corporation
>
> Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. © 2003 Microsoft Corporation. All rights
> reserved.
>
.

Relevant Pages

  • undefined reference to __udivdi3 (gcc-4.3)
    ... the following error occurs during linking: ... Searching the archives brought up old issues with gcc-3.4 and not so old posting from 01/2008, but I could not find a solution include libgcc.a). ...
    (Linux-Kernel)
  • Re: New hawk pic for identification
    ... although sometimes the guessing is fun...... ... If I went thru the trouble of posting and linking to find out what ...
    (rec.birds)
  • Changing text field to Date
    ... I am linking to a text file and I need to change the date field "Posting ... decending). ...
    (microsoft.public.access.queries)
  • Re: samba file copy lag
    ... Ashok Shrestha wrote: ... None practical, but try posting (or linking to) tcpdump output, maybe ...
    (freebsd-hackers)
  • RE: confused connection-SQL7
    ... but you would have had to choose this server during the linking step ... Kevin McDonnell ... Microsoft Corporation ... This posting is provided AS IS with no warranties, ...
    (microsoft.public.sqlserver.connect)