Re: [ANNOUNCEMENT] Updated: binutils-20021117-1

[egor duda <deo at logos-m dot ru>]

Hi!

Tuesday, 19 November, 2002 Christopher Faylor cygwin@cygwin.com wrote:

CF> I've made a new version of binutils available for download.  This is
CF> just a refresh from sources.redhat.com.  A notable change is the
CF> addition of Egor Duda's --enable-runtime-pseudo-reloc option which
CF> allows almost transparent linking of dll's without the need of a def
CF> file.  However, this option requires functionality in the cygwin DLL
CF> which is not yet present.  Stay tuned.

Ok, it's time to revive a discussion about implementation of
pseudo-relocations in runtime. So far, there were 3 propositions:

1. Implement everything in application (in crt0.o)
Benefits: Will work with any version of cygwin1.dll. All problems with
lack of support from runtime are detected during application linking.
(Possibly) common code with mingw.
Drawbacks: Will require rebuilding application in case we'll want
change something.

2. Implement everything in cygwin1.dll. In this case application is
about to have an external reference to _pei386_runtime_relocator.
Benefits: Easy to change relocation semantics without relinking
application.
Drawbacks: GUI window popping up when "new" application is loaded with
"old" runtime. Lack of support is detected only at application
startup.

3. Implement actual relocation in dll, and call it from crt0 via
cygwin_internal(). Check dll api version and print error message if
runtime is too old.
Benefits: Easy to change relocation semantics without relinking
application.
Drawbacks: Lack of support is detected only at application
startup.
Question: How can one distinguish console application from GUI one?
What is the best wording for the error message?

My own preference list (from most preferable to least preferable) is:
1st, then 3rd, then 2nd.

Comments?

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19