On Fri, Nov 26, 2004 at 04:26:24PM -0600, Craig A. Berry wrote: > At 8:58 PM +0000 11/26/04, Nicholas Clark wrote: > >is the right way to specify that this rule builds both. What's the VMS > >equivalent to: > > > >lib/Config.pm lib/Config_heavy.pl: config.sh miniperl$(EXE_EXT) configpm Porting/Glossary > > $(LDLIBPTH) ./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp > > sh mv-if-diff configpm.tmp $@ > > Multiple targets are allowed -- it just expands it into two separate > dependencies that are identical except for the target. So something > like the following oughta work: Thanks. Hopefully I got all the editing right in change 23554 ( http://public.activestate.com/cgi-bin/perlbrowse?patch=23554 ) Unfortunately the testdrive systems seem to be unreachable, so I couldn't actually test anything. > We could get fancier with the mv, but I don't know exactly what > mv-if-diff does. Will it update the timestamp on the target even if > it doesn't need to do the move? Is it important that the timestamp > on lib/Config.pm *not* be updated unless the move actually took place? Oops. I wasn't clear. That was based closely on the existing section of the Unix Makefile. I'd not checked carefully enough to see what VMS was doing for that step. It's only Unix that's doing that mv-if-diff Anyway, change 23554 is now in, and with luck won't break on VMS or Windows (or anything Unix for that matter) Nicholas ClarkThread Previous | Thread Next