This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Linking VCC with cygwing Gcc

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.
>% 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.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]