Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3A117C5D.46F6034@studserv.uni-stuttgart.de>
Date: Tue, 14 Nov 2000 18:54:37 +0100
From: Tilman Utz <Tilman DOT Utz AT studserv DOT uni-stuttgart DOT de>
X-Mailer: Mozilla 4.7 [de] (Win98; I)
X-Accept-Language: de
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: included headers with mno-cygwin
References: <3A104F81 DOT 21719 DOT 133442D AT localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Paul Garceau schrieb:

>
> > What I discovered until now:
> > - I passed the -H option to the compiler to see what headers are
> > included. The output file is about 1.57 MByte large and I
> > couldn't read everything so far, but at a first glance, I saw the
> > following headers repeatedly being included:
> >
> >
> > /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-4/../../../../include/g++-
> > 3/iostream.h
>
>         Here are the most immediate problems I can see:
>
>         /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2-4, unless there is a
> symlink of some sort somewhere else, is no longer referenced by
> Cygwin.  I base this statement on the observation that the
> latest installation (setup.exe from sources.redhat.com) does not
> create any such directory/folder on a fresh install.
>
>         Not sure if this is because of original version you are using
> or not.  However, you might want to delete your cygwin
> directory/folder and start with a fresh install.  I don't know
> if the latest setup handles this...DJ?

err, strange thing, I installed my current version of cygwin on November
9th from the freesoftware mirror... but I can try again...

> > So i think
> > they shouldn't be included. The following seems to me as a
> > logical consequence of the above:
> >
> > - objdump -p executable-name | grep "DLL Name" produced the
> > following result:
> >                      DLL Name: KERNEL32.dll
> >                      DLL Name: cygwin1.dll
> >                      DLL Name: crtdll.dll
> >       or is ist ok, that it uses cygwin _and_ crtdll?
>
>         Yes, that is the only way it works for -mno-cygwin
> compile/linking.

but I thought, using the cygwin flag I wouldn't link against cygwin1.dll

>
> >
> > So, what I'd like to ask: If the above headers aren't mingw,
> > where may I get the corresponding mingw headers?
>
>         Afaik, the the .dlls you reference are provided by MS as part
> of any MS OS distribution and, individually, need to be
> referencable by the linker.
>
> > How can I make
> > the makefile not include cygwin<1.dll> headers?
>
>         As you did earlier, simply compile with -mno-cygwin.
> crtdll.dll and Kernel32.dll are required for win32api based
> builds using either cygwin or mingw.
>
>         If you need to build a mingw c++ app then,  for now, you would
> probably be better off downloading mingw-msvcrt distribution and
> then adding the g++ libs (g++-v3, as a general behavioural rule,
> works fine for mingw after you build and install the g++-v3
> libs).

        Sorry, that, I don't understand. Do you mean I should switch from
cygwin to mingw, if I want cygwin-dll independent executables (that's what
I intend), or just install the 'right' headers and libs, which are
included in the mingw distribution?

        I probably didn't make myself clear. I have this library, sources
with a makefile (actually this is generated by a configure script), which
needs for whatever reasons to be compiled with the gcc. As I intend to
write an application for win32, I tried to compile the lib with the
mno-cygwin flag, to become independent of cygwin.dll. I suceeded building
the library under cygwin without the flag, so the makefile seems to be
ok...

        Now I'm struggling hard to make the same with the flag, which
isn't easy, especially as I'm a 'newbie' on C++ and all the
Unix-cygwin-win32 stuff.

thanks,
Tilman


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com