This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Using Cygwin compiled libs in Visual Studio
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 4 Apr 2009 14:11:11 -0400
- Subject: Re: Using Cygwin compiled libs in Visual Studio
- References: <gqtmom$mki$1@ger.gmane.org> <49D26A62.40303@cygwin.com> <gr7vga$q7g$1@ger.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Sat, Apr 04, 2009 at 04:48:25PM +0100, Olumide wrote:
> I guess what I find surprising is that gcc can be used to produce Windows
> XP runnable code. Here's a typical compilation command generated by the
> build process:
>
> gcc -c -O2 -D_GNU_SOURCE -DWINDOWS_ABI -Wall -m32 -DF_INTERFACE_F2C
> -DNEED_F2CCO NV -DMAX_CPU_NUMBER=2 -DNUM_BUFFERS=\(2*2\) -DASMNAME=_cpotri
> -DASMFNAME=_cpotri _ -DNAME=cpotri_ -DCNAME=cpotri -DFUNDERSCORE=_
> -DNEEDFUNDERSCORE -DBUNDERSCORE=_ -DNEEDBUNDERSCORE -I../.. -DARCH_X86
> -DPENTIUMM -DL1_CODE_SIZE=32768 -DL1_CODE_ASSOCIATIVE=8
> -DL1_CODE_LINESIZE=64 -DL1_DATA_SIZE=32768 -DL1_DATA_ASSOCIATIVE=8
> -DL1_DATA_LINESIZE=64 -DL2_SIZE=1048576 -DL2_ASSOCIATIVE=8 -DL2_LINESIZE=64
> -DITB_SIZE=4096 -DITB_ASSOCIATIVE=4 -DITB_ENTRIES=128 -DDTB_SIZE=4096
> -DDTB_ASSOCIATIVE=4 -DDTB_ENTRIES=128 -DHAVE_CMOV -DHAVE_MMX -DHAVE_SSE
> -DHAVE_SSE2 -DHAVE_CFLUSH -DNUM_SHAREDCACHE=1 -DNUM_CORES=1 -DCORE_BANIAS
> -DCOMPLEX -UDOUBLE zpotri.c -o cpotri.o
Why is this surprising? Cygwin *is* Windows XP runnable code.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/