This is the mail archive of the cygwin 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: Using -mno-cygwin flag


> * Dave Korn <qnir.xbea@negvzv.pbz> [2005-05-04 18:49:24 +0100]:
>
> ----Original Message----
>>From: Sam Steingold
>>Sent: 04 May 2005 18:32
>
>>> That's something to take up with the MinGW folks (www.mingw.org).
>> 
>> I am not quite clear on the exact relationship between cygwin and MinGW
>> project (I assumed that they are independent except that cygwin includes
>> parts of MinGW).  Why would I want to talk to them?
>
>   Because it is *their* compiler, *their* header files, *their*
> libraries, and in all regards *their* distribution of software that
> you are invoking when you use -mno-cygwin, so if you want changes to
> it, that's who you need to talk to.

but it came with cygwin - the cygwin team packaged their software and
distributed it with cygwin.
I consider this to be more of a packaging issue than a software issue.
I don't want mingw to change their product.
I want cygwin to package mingw somewhat differently.
actually, not even that.
I want cygwin to package some of its packages without unnecessary
dependencies.

>> Here is the rationale:
>
>> Supposed I am developing several different programs:
>> <A>: just my own C code, compiled with "gcc -mno-cygwin"
>> <B>: my own C + PCRE: I could compile it with "gcc -mno-cygwin", but
>>      PCRE requires cygwin - for no technical reason because actually
>>      PCRE compiles under win32 natively, without cygwin
>> <C>: my own C + PCRE + X: there is no way to build it without cygwin,
>>      because there is no native w32 port of X
>> 
>> Thus right now I can build a native w32 version of <A> but only cygwin
>> versions of <B> and <C>.
>
> No, that's nonsense.  Since you compile with "-mno-cygwin", you aren't
> making a cygwin version of <B>.  You're making a MinGW version of <B>.

But I cannot make a MinGW version of <B> because <B> requires PCRE and
cygwin comes with the PCRE version that requires cygwin1.dll

>> I want to be able to build a native w32 version of <B> also.
>
>   You just did.  You used "-mno-cygwin".  That gets you a native w32
> program.

I got a link error: no libpcre

>> To do that, I must install _also_ MinGW - with its idiosyncratic
>> installation system &c.
>
>   Well, duh.  If you want to USE MinGW, you have to INSTALL it.  That
> much is obvious.

I thought I did - when I installed the gcc-mingw cygwin package.

>   The point you're missing is that Cygwin is not responsible for mingw
> and is not going to spend a lot of time adding packages to its distro.

you already have the pcre package.
I want it to be built with "-mno-cygwin" to avoid an unnecessary
dependency.

Imagine that pcre were lined with "-lhuge" where libhuge.a were just a
huge library which did not add to the pcre's functionality.
do you think it would be a reasonable request to re-package pcre so that
it does not use that library?


-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://ffii.org/> <http://www.iris.org.il> <http://www.palestinefacts.org/>
<http://www.camera.org> <http://www.openvotingconsortium.org/>
Takeoffs are optional.  Landings are mandatory.

--
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/


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