X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=KCrjkJvbgsZJztsn+iM1hNfvQMVq4O
	ljmszYPKaxmgZx/kCkxKYC3TtSqydzmhoczw9HeKN4tYjX/Lhr+aQx76b6WI1QBI
	KOfQlNgVtNDHCfLBAYXX0WU1xOlBYzyxBM00DKQyGNkr1TDvdPUGInUTIZiKLJpf
	NDkd2mw9S1hb0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=f2aBP4li8zQvvXMPwSsvizbp+ug=; b=DbL2
	MgHTl48izO2kQOVmD4AXgaKeK+OWn6jd6usJH3vVMxRr5FNlveT9XRKN20FGbudt
	YGuyCdJUcH2tZh88X3Gf2uXHTrKbt7LPty0XYBl6/+Hl8/lpq2XzVLFnEwifJ7Al
	Pq5l1NpS9vXNSUdFhij/fsCvYZXT1IIq4tAEt+4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_FSL_HELO_BARE_IP_2 autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: Building cpan module that links with proprietary libs
Date: Fri, 30 May 2014 13:42:22 -0700
Lines: 40
Message-ID: <lmaqfj$utj$1@ger.gmane.org>
References: <lm651o$5ss$1 AT ger DOT gmane DOT org>	<CAEhDDbCjo_wO7xP9i9rfgqM82Z6h+bL0HDrV8bxwtbUryV=pNg AT mail DOT gmail DOT com>	<lm7rtc$ofg$1 AT ger DOT gmane DOT org>	<5387E20D DOT 7090806 AT cygwin DOT com>	<lm8qrq$nm3$1 AT ger DOT gmane DOT org> <CAEhDDbBjpJ0nPQ2cT5dEe4ZcR+XnASjj7FYbZ1iKJ4xqcTWWJg AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
In-Reply-To: <CAEhDDbBjpJ0nPQ2cT5dEe4ZcR+XnASjj7FYbZ1iKJ4xqcTWWJg@mail.gmail.com>
X-IsSubscribed: yes

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