Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Thu, 6 Jun 2002 23:17:08 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Linking VCC with cygwing Gcc
Message-ID: <20020607031708.GA23995@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5D01E8305096D3119D7D00508B5EBBF40A759D33 AT ntmsg0133 DOT corpmail DOT telstra DOT com DOT au> <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020606221720 DOT 01f8c670 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.0.20020606221720.01f8c670@pop.ma.ultranet.com>
User-Agent: Mutt/1.3.23.1i

On Thu, Jun 06, 2002 at 10:28:12PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>Yes but Pavel's question to you was, did you compile the code with the f()
>function in VC++ as "Debug" or "Release"?  You should compile it as release
>and compile the Cygwin main function with "gcc -o foo foo.c vcfoo.obj", where
>vcfoo.obj is your VC++ object file compiled as "Release".  I just tried your
>example here and it worked fine (note I'm using the VC++ compiler from the
>command line).  
>
>% cl -c -Id:/Program\ Files/Microsoft\ Visual\ Studio/VC98/Include/ vcfoo.c
>Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86
>Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
>
>vcfoo.c
>% gcc -o foo foo.c vcfoo.obj
>% foo
>Hello world
>
>
>This should be enough to verify for you that this can be done, no?

Btw, I don't think that it has been mentioned yet, but in this scenario,
the sources for foo.c have to be released with the program, since
foo.exe is a cygwin GPL'ed program.  The source for vclfoo.c doesn't
have to be released (IANAL) since it isn't using any cygwin routines.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/