From: Jason Tishler <jason@tishler.net>
To: cygwin@cygwin.com
Subject: Re: Python and PIL and rebase, oh my!
Date: Fri, 10 May 2002 06:20:00 -0000 [thread overview]
Message-ID: <20020510123021.GC2124@tishler.net> (raw)
In-Reply-To: <3CDAFAAB.3070405@ece.gatech.edu>
On Thu, May 09, 2002 at 06:39:39PM -0400, Charles Wilson wrote:
> #3) ------------------------------
> rebase: We really need to get this into setup ASAP.
I know, I know... [Hangs head in shame again.] Sigh...
> The current
> version (as posted on the mailing list) has the following interesting
> property:
> $ cygcheck rebase.exe
> Found: .\rebase.exe
> .\rebase.exe
> D:\cygwin\bin\cygwin1.dll
> D:\WINNT\System32\KERNEL32.dll
> D:\WINNT\System32\NTDLL.DLL
> D:\WINNT\System32\IMAGEHLP.DLL
> D:\WINNT\System32\MSVCRT.DLL
>
> I dunno about you, but depending on both cygwin1.dll and MSVCRT.dll
> bothers me. But, we need IMAGEHLP.DLL -- so rebase.exe has to be a
> mingw app.
Oops!
> There's only one problem: it calls
> cygwin_conv_to_win32_path. Now, I know the setup codebase includes its
> own versions of those functions, so that'd probably help wean rebase.exe
> away from cygwin1.dll...
Actually, I have had a Mingw version of this stand-alone version of
rebase.exe for a while. I just uploaded it to my web site:
http://www.tishler.net/jason/software/rebase/
and moved the (deprecated) Cygwin version to:
http://www.tishler.net/jason/software/rebase/deprecated/
Now that I can use STL in Cygwin's setup.exe, I'm hoping to start making
head way with rebase/setup.exe integration.
Jason
--
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/
prev parent reply other threads:[~2002-05-10 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 16:19 Charles Wilson
2002-05-10 6:20 ` Jason Tishler [this message]
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=20020510123021.GC2124@tishler.net \
--to=jason@tishler.net \
--cc=cygwin@cygwin.com \
/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).