1N/A# Some quick tests to see if h2xs actually runs and creates files as 1N/A# expected. File contents include date stamps and/or usernames 1N/A# hence are not checked. File existence is checked with -e though. 1N/A# This test depends on File::Path::rmtree() to clean up with. 1N/A# We are now checking that the correct use $version; is present in 1N/A chdir 't' if -d 't'; 1N/A# use strict; # we are not really testing this 1N/A# Don't want its diagnostics getting in the way of ours. 1N/A# You might also wish to bail out if your perl platform does not 1N/A# do `$^X -e 'warn "Writing h2xst"' 2>&1`; duplicity. 1N/A# ok on unix, nt, VMS, ... 1N/A# ok on unix, nt, The extra \" are for VMS 1N/A# The >&1 would create a file named &1 on MPW (STDERR && STDOUT are 1N/A # -x overcomes MPW $Config{startperl} anomaly 1N/A# $name should differ from system header file names and must 1N/A# not already be found in the t/ subdirectory for perl. 1N/A"-f -n $name -b 5.6.1", "5.006001", <<"EOXSFILES", 1N/A"-f -n $name -b 5.5.3", "5.00503", <<"EOXSFILES", 1N/A # 1 test for running it, 1 test for the expected result, and 1 for each file 1N/A # And 1 more for our check for "bonus" files, 2 more for ExtUtil::Manifest. 1N/A # use the () to force list context and hence count the number of matches. 1N/A # h2xs warns about what it is writing hence the (possibly unportable) 1N/A # accomodate MPW # comment character prependage 1N/A #print "# expectation is >$expectation<\n"; 1N/A #print "# result is >$result<\n"; 1N/A # Was the output the list of files that were expected? 1N/A print "# These files are unexpectedly present:\n"; 1N/A # Aargh. Something wants to load a bit of regexp. And we have to chdir 1N/A # for ExtUtils::Manifest. Caught between a rock and a hard place, so this 1N/A # seems the least evil thing to do: