Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Wed, 3 May 2000 10:33:41 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: Status of availability of features which allow correct and seamless support of DLLs in current GNU-Win32 releases
Message-ID: <20000503103341.E6787@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com
References: <200005031210.IAA08335@envy.delorie.com> <15725.000503@is.lg.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <15725.000503@is.lg.ua>; from paul-ml@is.lg.ua on Wed, May 03, 2000 at 05:24:23PM +0300

On Wed, May 03, 2000 at 05:24:23PM +0300, Paul Sokolovsky wrote:
>Hello DJ,
>
>Wednesday, May 03, 2000, 3:10:44 PM, you wrote:
>
>
>>> DD> You can't put them in the .def file yourself?
>>>
>>>     If I will put data symbols in defs myself for every X-Server,
>>> GNOME, KDE, etc. which I'm going to port, I will hardly port single.
>>> Which is exactly the current situation ;-)
>
>DD> An automated porting effort using DLLs with data is going to be hard
>DD> anyway.  Either way, you *must* modify the sources to understand that
>DD> the data is coming from the DLL, or it won't work.
>
>    Ha, that's the effect of stereotypes! It is at runtime, at the point of
>specific variable access the decision on how to access it should be
>unavoidably made: either access var directly or via extra level of
>inderection.

Um.  This sort of needs to be done at the time of the compilation or assembly.
Otherwise you have to give the linker understanding of x86 (or whaterver)
opcodes.

Do you think if it was really this easy, it wouldn't have been done this
way already?  Microsoft would have done this long ago.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com