From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Jason Tishler" <jason@tishler.net>
Cc: "Ralf Habacker" <Ralf.Habacker@freenet.de>,
"Cygwin" <cygwin@sources.redhat.com>
Subject: Re: rebase addon - Bas and Size listing of dll's without rebasing
Date: Thu, 03 Jan 2002 05:27:00 -0000 [thread overview]
Message-ID: <09e701c1945a$5adf84d0$0200a8c0@lifelesswks> (raw)
In-Reply-To: <20020103132835.GB1940@dothill.com>
----- Original Message -----
From: "Jason Tishler" <jason@tishler.net>
> > IMO we should be using bfd not the MS helper libraries - in the long
> > term. Otherwise one cannot do any of this as part of a cross compile
or
> > cross-manipulation toolkit.
>
> Good point.
>
> I'm willing to do the right thing, but that is going to take longer
given
> the ramp up necessary for me learn about binutils' configury/make,
bfd,
> etc. However, I would like to get a rebase solution into setup.exe
ASAP.
> Is a two prong approach acceptable? In the short term, add rebase to
> winsup/utils, integrate directly into setup.exe, etc. In the long
term,
> add rebase to binutils, integrate with ld, etc.
Yes. In fact it's probably a requirement, as setup.exe cannot get too
big.
Does the MS solution need .dll's not present on win95a ?
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-01-03 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 14:01 Ralf Habacker
2001-12-27 10:22 ` Jason Tishler
2001-12-27 18:34 ` Robert Collins
2002-01-03 5:24 ` Jason Tishler
2002-01-03 5:27 ` Robert Collins [this message]
2002-01-04 6:10 ` Jason Tishler
2001-12-28 5:48 ` Ralf Habacker
2001-12-28 10:24 ` Christopher Faylor
2001-12-29 3:22 ` Ralf Habacker
2002-01-03 9:25 ` Ralf Habacker
2002-01-03 13:42 ` Robert Collins
2002-01-04 6:18 ` Jason Tishler
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='09e701c1945a$5adf84d0$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=Ralf.Habacker@freenet.de \
--cc=cygwin@sources.redhat.com \
--cc=jason@tishler.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).