From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: Building cpan module that links with proprietary libs
Date: Fri, 30 May 2014 22:06:00 -0000 [thread overview]
Message-ID: <lmaqfj$utj$1@ger.gmane.org> (raw)
In-Reply-To: <CAEhDDbBjpJ0nPQ2cT5dEe4ZcR+XnASjj7FYbZ1iKJ4xqcTWWJg@mail.gmail.com>
On 5/30/2014 1:01 AM, Csaba Raduly wrote:
> On Fri, May 30, 2014 at 4:36 AM, Andrew DeFaria wrote:
>> On 5/29/2014 6:42 PM, Larry Hall (Cygwin) wrote:
>>> As a
>>> result, you will never get code compiled with g++ to link with these
>>> libraries. There is no common ABI among C++ compilers. Thus, the
>>> libraries
>>> and headers of one can't be used as input to the compiler of another, even
>>> on the same platform. This only works for C code. So you have to either
>>> build the proprietary libs with Cygwin's C++ compiler or write your own
>>> "shim" library that wraps the necessary calls and objects in a C API,
>>> compile that with VS, and link your program against the APIs in your
>>> library.
>
> @Larry: Would this work? I think MSVC produces obj and lib files in
> COFF; can Cygwin's toolchain understand that?
>
>>
>> Being as this code is proprietary I doubt that Perforce will release it to
>> me to compile but I will point them at this thread...'
>
> Maybe you can convince them to build a Cygwin version (not very likely).
I am in contact with Perforce about this. They think it's a wonderful
idea and they fully want me to let them know when I've managed to
accomplish this! ;-)
Needless to say, Cygwin, it's Perl and having a P4Perl available for it
is not necessarily in Perforce's business model. Most people just use
ActiveState. That said, with 5.18 I hear the backend moves to gcc and
they need to address that issue. Once addressed having a Cygwin version
may be easier for them to produce.
I, unfortunately, do not have a lot of time to dedicate to this as my
client wants me to work on others things. Using Cygwin's Perl is a
convenience for me but not a necessity, though I would love to have this
working.
--
Andrew DeFaria
http://defaria.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-30 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 4:25 Andrew DeFaria
2014-05-29 8:58 ` Csaba Raduly
2014-05-29 20:34 ` Andrew DeFaria
2014-05-30 6:49 ` Larry Hall (Cygwin)
2014-05-30 8:01 ` Andrew DeFaria
2014-05-30 11:27 ` Csaba Raduly
2014-05-30 17:40 ` Larry Hall (Cygwin)
2014-05-30 22:06 ` Andrew DeFaria [this message]
2014-05-30 16:47 ` Larry Hall (Cygwin)
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='lmaqfj$utj$1@ger.gmane.org' \
--to=andrew@defaria.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).