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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=aR Pwu4wVoxo5/+R5Ga+36eaq0JH5PK3J9+JzkTANRxhcU2qMva4uLk6Hz7hTUfK6ZJ 1bbstCpC82EodMTfEKB/Us0RBDkJZQw18LKCI0j9nQmAdsqtasQQX28DG+l1pTX5 bPAn2vW2xx91DaWt6fYlbab5NuQTDurlof1GNMoTQ= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=nx2vF01n 3sHw7KjKSUMN8VOiuvg=; b=mBGgrmwdxhf5YemCz3fCWtYBfIy/06icNL8RQsKU CHfbeNsiymjeP1Jg1095e1Mp0qaNFY9lYMAKsg//aAIS68z5/GQe5JcAxnK+QIvG hHhynxJlaSxynIgN8LnFJTaQDU0r3ZwOVGvLN1Bk1RckbWUc6GmjNzYbgKGtefsd D8E= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.8 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wg0-f50.google.com MIME-Version: 1.0 X-Received: by 10.180.108.106 with SMTP id hj10mr3951544wib.53.1401436885650; Fri, 30 May 2014 01:01:25 -0700 (PDT) In-Reply-To: References: <5387E20D DOT 7090806 AT cygwin DOT com> Date: Fri, 30 May 2014 10:01:25 +0200 Message-ID: Subject: Re: Building cpan module that links with proprietary libs From: Csaba Raduly To: cygwin list Content-Type: text/plain; charset=ISO-8859-1 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). Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- 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