[Date Prev][Date Next]
MinGW and Client Libraries
- To: OpenLDAP-software@OpenLDAP.org
- Subject: MinGW and Client Libraries
- From: Douglas Abbink <email@example.com>
- Date: Fri, 24 Jun 2005 10:12:26 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=B1mW/aP75VnnHQ8PikY9/dddWAu43mjzqSqrcHJLdpFbVwt+ICHkxuoxXe3Tv2PCZK59SRALiY9/exRtjDI8pk7f1kQbvP+/0Q89b5aHtteXGscMlQwxH/3dpF1CLUTQ8u7jAsPEXowZ5rJ770w+UlnjLd+NWnRI64nRCft5tAQ= ;
I have done repeated searches through the archives and
have not been able to find the answer I need.
I am working on porting a Linux App to WIN32. The
Linux project is currently using OpenLDAP 2.2.17 for
client access. What I need is to get the client
libraries libldap and liblber into either static or
dynamic libraries I can link to using MSVC 2003 (7.1).
I have been able to compile the whole openLDAP server
using MinGW, MSYS and a version of Lucas Bergman's
script (all other attempts, like what is described in
the FAQ, fail at one point or another). But I have no
idea how to get the client libraries in a form MSVC
What I would like to know is:
Are there special flags to produce static or dynamic
libraries, Or, can the .a files produced by MinGW be
converted to .lib files that MSVC understands, or, is
there some other way to get a hold of these libraries?
I have seen similar questions (about getting windows
builds) asked in the archives, but don't find many
answers. Is it just that I cannot find the answers in
the archives, or has no one found a good way to
compile the 2.2.x system on Windows?
Note: An older version of my companies software was
done on 2.1.x before I got here but the specs are now
to use the 2.2.x libraries.
Rekindle the Rivalries. Sign up for Fantasy Football