public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Rick Miller" <rdmiller@execpc.com>
To: <gnu-win32@cygnus.com>, "Mumit Khan" <khan@xraylith.wisc.edu>
Subject: Re: egcs plans
Date: Sat, 27 Dec 1997 04:42:00 -0000	[thread overview]
Message-ID: <199712271241.GAA20593@core0.mx.execpc.com> (raw)

I might be able to help with the installation...  I've been using
InstallShield 5 Pro. but I haven't tried a "self extracting" thingamabob. 
I usually make a directory tree with "disk1", "disk2" etc. directories in
it so that it can be installed from there or put onto floppies.

I've done some pretty extensive scripting for the wierd ways my employer
likes to have its software installed and have some experience modifying the
registry from the install script.

I could probably learn to create whatever kind of install you're looking
for, except International... that's a different InstallShield "product".

Rick Miller
http://www.execpc.com/

----------
> From: Mumit Khan <khan@xraylith.wisc.edu>
> To: gnu-win32@cygnus.com
> Subject: egcs plans 
> Date: Friday, December 26, 1997 12:12 PM
> 
> Here're some near-future plans I have for egcs for cygwin32/mingw32.
> Comments welcome.
>   
>   - gcc-2.8.0 merge: Now that egcs has merged in 2.8.0 features and I
have
>     things running quite well, the next release will have the best of
both
>     worlds. Hopefully the new code to use the Win32 Registry will solve
>     some of the installation woes.
> 
>   - dlltool/ld/gas fixes from Mikey: Hopefully I can merge in the fixes 
>     from Mikey that allows one to link with MS LIB files. I don't
>     understand some of the changes yet, but I'll be in touch with Mikey
>     to clear things up.
> 
>   - (mingw32) dlltool enhancements Pedro Pedro A. Aranda Guti\irrez: This
>     allows synonyms and constants in .def files and obviates the need for
>     libmoldname.a, and hence multiple imports for crtdll.
> 
>   - (very tentative) Installer: I don't know if this is going to happen, 
>     but it sure would be nice. If you can help in this, please let me
know. 
>     I only have InstallShield Express, which is a pain to use when you
>     tons of directories, and doesn't support scripting.
> 
>   - unpacked tree via ftp? I'd really like to have the unpacked directory
>     hieararchy available via ftp, but I can't do it here due to resource
>     constraints. I'm sure someone else will volunteer ;-)
> 
> When? Definitely not before Jan 7 since I'll be few timezeones away (and 
> fortunately +22 degrees C) from my home machine. I can still remotely 
> build the snapshots and fix problems however. Looks like sometime around 
> Jan 15.
> 
> Why not just use FSF-2.8.0 when released instead of egcs? What benefits
> do you get over the soon-to-be-released gcc-2.8.0?
> 
>   - Crucial c++ fixes in egcs that affect the C++ code on PE-COFF.
>   - g77 is "integrated" into egcs. Some of the "experimental" 
>     features such as alias analysis are in egcs, but not in FSF. 
>   - other misc x86 optimizations that are not in FSF.
> 
> Happy Holidays to all.
> 
> Regards,
> Mumit -- khan@xraylith.wisc.edu
> http://www.xraylith.wisc.edu/~khan/
> 
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-12-27  4:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-27  4:42 Rick Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-12-26 10:12 Mumit Khan

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=199712271241.GAA20593@core0.mx.execpc.com \
    --to=rdmiller@execpc.com \
    --cc=gnu-win32@cygnus.com \
    --cc=khan@xraylith.wisc.edu \
    /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).