X-Spam-Check-By: sourceware.org
Message-ID: <4487A2CC.3090205@cygwin.com>
Date: Thu, 08 Jun 2006 00:08:44 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051223 Fedora/1.5-0.2.fc4.remi Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: <kein Betreff>
References: <605176809 AT web DOT de> <44863AE9 DOT 6060700 AT cygwin DOT com> <44872778 DOT 8020409 AT web DOT de>
In-Reply-To: <44872778.8020409@web.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Reformatted top-post.

> Larry Hall (Cygwin) wrote:
>> Maurice Hüllein wrote:
>>> I'm currently developing a c++ plugin for a windows simulator 
>>> environment, which accepts plugins in form of a dll. For doing so my 
>>> dll needs to include a library of this simulator program which is 
>>> only supported
>>> in ".a" format. I solved this problem by cross compiling the dll from 
>>> cygwin for the windows platform.
>>>
>>> But now there is another problem. My .dll-project needs to use 
>>> external libraries which are only supported
>>> in windows .lib format. So theres the issue that my VC Express 
>>> compiler can not use the .a library and the
>>> cross compiler can not handle the .lib. I already read that even if 
>>> both, the .a and .lib, are static libraries there are 
>>> incompatibilities because of the used compiler.
>>> I would prefer to disclaim the bypass of using cygwin and a cross 
>>> compiler at all. So is there any way of
>>> converting the .a library in a native windows .lib?
>>
>>
>> The incompatibilities you refer to are the result of differences in 
>> different
>> "vendors" C++ formats, not in the differences between library formats.
>> Actually a static .a and .lib have the same format.  But the former
>> restriction overshadows the latter non-issue.  You'll need to wrap your
>> library in C-callable interfaces if you really want to get this to work.
>> Perhaps the very recently update SWIG library will be helpful for you?
Serethos wrote:
 > Thx for your answer. But I called the guys from the SWIG mailing list
 > and they stated that
 > my problem can not be solved with SWIG. It would only be useful if I
 > wished to use a
 > e.g. c-program for another language.
 > Any other ideas?
 >

Off the top of my head, no.  Well, other than manually creating C-callable
interfaces yourself.  But I'll bet there's a project out there that would
help you do this if you poke around.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/