From: "Fahd Abidi" <fabidi@ultsol.com>
To: "Andrew STUBBS" <andrew.stubbs@st.com>
Cc: <gdb@sourceware.org>
Subject: RE: trying to build gdb with renamed cygwin1.dll
Date: Mon, 30 Apr 2007 15:38:00 -0000 [thread overview]
Message-ID: <071DB0C788671B48940BC79F8B4930691181F5@ultsol01.tewks.ultsol.local> (raw)
I tried the -mno-cygwin option but got several compile errors. I didn't
want to debug the sources because of time constraints. That is why I
thought that compiling against a renamed cygwin1.dll might be an eaisier
solution.
Fahd
-----Original Message-----
From: Andrew STUBBS [mailto:andrew.stubbs@st.com]
Sent: Monday, April 30, 2007 11:30 AM
To: Fahd Abidi
Cc: gdb@sourceware.org
Subject: Re: trying to build gdb with renamed cygwin1.dll
Fahd Abidi wrote:
> My purpose is to try and build a gdb that so I can move it across
> different windows platforms with out worrying about newer or older
> versions of the cygwin dll interfering. I already looked at the MinGW
> option but the newer versions of gdb do not build against mingw32.
I don't know about the exact solution you had in mind, but ....
You might want to investigate the -mno-cygwin GCC option. This builds
"MinGW" binaries (Minimum GNU for Windows) which do not depend upon
anything not present in a standard Windows installation. This is how our
Windows tools are built.
Obviously there are issues with doing it this way - no automatic support
for Cygwin pathnames being the biggest - but most of these can be
overcome with little effort, and all overcome with more effort.
Andrew
next reply other threads:[~2007-04-30 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:38 Fahd Abidi [this message]
2007-04-30 15:49 ` Andrew STUBBS
2007-04-30 15:57 ` Brian Dessent
2007-04-30 16:15 ` Andrew STUBBS
-- strict thread matches above, loose matches on Subject: below --
2007-04-30 16:38 Fahd Abidi
2007-04-30 17:04 ` Andrew STUBBS
2007-04-30 20:12 ` Dave Korn
2007-04-30 20:18 ` Daniel Jacobowitz
2007-04-30 15:05 Fahd Abidi
2007-04-30 15:10 ` Bob Rossi
2007-04-30 15:13 ` Bob Rossi
2007-04-30 15:18 ` Andrew STUBBS
2007-04-30 15:32 ` Brian Dessent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=071DB0C788671B48940BC79F8B4930691181F5@ultsol01.tewks.ultsol.local \
--to=fabidi@ultsol.com \
--cc=andrew.stubbs@st.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox