From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24848 invoked by alias); 30 May 2014 16:47:18 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 24838 invoked by uid 89); 30 May 2014 16:47:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: vms173023pub.verizon.net Received: from vms173023pub.verizon.net (HELO vms173023pub.verizon.net) (206.46.173.23) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 May 2014 16:47:16 +0000 Received: from [192.168.1.231] ([unknown] [74.104.179.122]) by vms173023.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N6E00J20BXDNVK0@vms173023.mailsrvcs.net> for cygwin@cygwin.com; Fri, 30 May 2014 11:47:06 -0500 (CDT) Message-id: <5388B5E1.4050209@cygwin.com> Date: Fri, 30 May 2014 17:40:00 -0000 From: "Larry Hall (Cygwin)" Reply-to: cygwin@cygwin.com User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-version: 1.0 To: cygwin@cygwin.com Subject: Re: Building cpan module that links with proprietary libs References: <5387E20D.7090806@cygwin.com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-SW-Source: 2014-05/txt/msg00535.txt.bz2 On 05/30/2014 04: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? What I'm suggesting is not all that different than using Windows native platform or other libraries with Cygwin. So yes, what I'm suggesting will work and is the typical approach taken to use C++ libraries built by a different compiler. It's a pain but it works. In this case, you just have to wrap the class methods you want to use in C functions, declare then 'extern "C"', __cdecl, and __declspec(dllexport) (if you decide to make your "library" a DLL). Build that with VS and include the .lib at the end of your invocation of 'gcc'. Simple. :-) -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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