H.Merijn Brand wrote:

>Change 24806 by [EMAIL PROTECTED] on 2005/06/12 09:54:07
>
>       Subject: improve static build for win32/Makefile
>       From: vadim <[EMAIL PROTECTED]>
>       Date: Sun, 12 Jun 2005 14:09:11 -0400
>       Message-Id: <[EMAIL PROTECTED]>
>
I guess it serves me right for not being around at weekends, but I wish 
this hadn't been committed in my absence.  Did you try this on Win32 
before committing?

I've long meant to have a look at a problem with the static build stuff 
in win32/makefile.mk but have never had time to get around to it.  The 
problem is that $(PERLDLL) depends on Extensions_static, which is a 
pseudo-target -- there is no file of that name -- hence make always 
considers it to be out-of-date.

Now the win32/Makefile has the same problem :(

Thus, when running "nmake test" after having done "nmake", nmake feels 
the need to rebuild static extensions, and hence the Perl DLL, and hence 
does a full relink of everything else too.

This is a real PITA at the best of times, but also has the unfortunate 
side-effect that the build no longer works unattended because the relink 
during "nmake test" causes xcopy to ask a question about overwriting the 
Perl DLL.

Thus, my last overnight smoke was hung and I had to kill it just now.

No more blead smokes from Win32 land until this is fixed, and I don't 
really have time right now.



------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are 
confidential and intended for the addressee(s) only.  If you have received this 
message in error or there are any problems, please notify the sender 
immediately.  The unauthorized use, disclosure, copying or alteration of this 
message is strictly forbidden.  Note that any views or opinions presented in 
this email are solely those of the author and do not necessarily represent 
those of Radan Computational Ltd.  The recipient(s) of this message should 
check it and any attached files for viruses: Radan Computational will accept no 
liability for any damage caused by any virus transmitted by this email.

Reply via email to