public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: <kein Betreff>
Date: Thu, 08 Jun 2006 07:14:00 -0000	[thread overview]
Message-ID: <4487A2CC.3090205@cygwin.com> (raw)
In-Reply-To: <44872778.8020409@web.de>

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/

  reply	other threads:[~2006-06-08  7:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 20:21 Maurice Hüllein
2006-06-07  2:48 ` Larry Hall (Cygwin)
2006-06-07 22:35   ` Serethos
2006-06-08  7:14     ` Larry Hall (Cygwin) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-30 14:15 sabine.petry
1999-03-02  8:04 No Subject Anjlica Malla
     [not found] ` < 000901be64c6$90bd9b80$89055280@oemcomputer >
1999-03-04 15:14   ` <kein Betreff> Michael Hirmke
1999-03-31 19:45     ` Michael Hirmke
1998-05-27  2:28 No Subject Gilbert Mak
1998-05-28 18:15 ` <kein Betreff> Michael Hirmke
1998-01-27 22:46 (Kein "Betreff") Lothar Werzinger
1998-01-28 14:54 ` Vadim V. Sytnikov
1998-01-29  4:47 ` root
1998-01-21 22:08 No Subject Bruce N. Hunsaker
1998-01-25 14:40 ` <kein Betreff> Michael Hirmke
1997-09-30 19:03 No Subject Hyung Kuk Kang
1997-10-01 13:41 ` <kein Betreff> Michael Hirmke
1997-08-16 20:30 No Subject IGnatius T Foobar
1997-08-17  7:17 ` <kein Betreff> Michael Hirmke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4487A2CC.3090205@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).