Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3E1DEBB5.6040908@yahoo.com> Date: Thu, 09 Jan 2003 16:37:57 -0500 From: Earnie Boyd User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Wilson CC: Alexandre Duret-Lutz , cygwin@cygwin.com, libtool-patches@gnu.org, automake-patches@gnu.org, mingw-users@lists.sourceforge.net Subject: Re: [Mingw-users] Re: Solving the "relink exe's" libtool problem References: <3E19C657.1040904@ece.gatech.edu> <2003-01-09-17-11-09+16471+duret_g@lrde.epita.fr> <3E1DE146.8030901@ece.gatech.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Charles Wilson wrote: > > Hmmm...now there's a thought. Perhaps, perhaps... > > Said "stub" executable would have to do ALL of the things the script > does, and then pass that environment to its exec'ed target in .libs/ -- > does native windows provide an exec() command? Environment inheritance? > You'd probably need different source code for the stub, depending on > the platform... if buildhost == posixy, then exec() is our friend; > otherwise, nasty native Windows code... > Yes MSVCRT.DLL contains both exec and spawn sets of functions. Yes the parent environment is inherited by the child. So, the stub should be able to work for either environment. > Unfortunately, I can't work on that right now; my available time just > went to zero. :-( > Sorry to hear that. :( Earnie. -- 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/