| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
For: RT #116479
|
| | |
|
| | |
|
| |
|
|
| |
on other OSes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Near the start of link(), $output gets set to a blib\arch\auto path.
A little later that gets copied into $spec{output}, but $spec{manifest}
is left unset so it gets set later to a $spec{builddir} path, which is
not what $spec{output} was set to earlier.
The manifest file is always created alongside the DLL, so the correct
fix is simply to append '.manifest' to the DLL path to find the manifest.
(EU-MM does that too.)
Patch taken from [cpan #35943] which reported the same problem. The other
concern raised there, about the VC version being checked to deduce the
existence of the manifest file rather than testing that directly, has
long since been incorporated already and also explains why this problem
has not been seen recently: the faulty attempt to embed the manifest has
not been attempted ever since the existence test was added because it was
also failing and hence no 'mt' command was being run. [cpan #35943] is
thus resolved by this change too.
Bump $VERSION in all ExtUtils::CBuilder files (to 0.280208) to keep them
all in sync as before.
|
| |
|
|
|
|
| |
Correct the test for the existence of the manifest file.
Bump $VERSION in all ExtUtils::CBuilder files (to 0.280207) to keep them
all in sync, as is currently the case.
|
| |
|
|
|
| |
Apparently, 'make distclean' tries to use it in confusing and
counterproducive ways. Easier to remove it than fix the other.
|
| |
|
|
|
| |
Adds a documentation note about support. Adds a README.patching
file with instructions for bumping versions, Changes, etc.
|
| |
|
|
|
| |
Also updates release instructions with a reminder to
update Maintainers.pl
|
| |
|
|
|
| |
Adds Makefile.PL, LICENSE, etc. and updates Changes for
work in blead from 5.14.0
|
| |
|
|
|
|
| |
[dagolden bumped $VERSION and added ambs to the AUTHORS file]
Signed-off-by: David Golden <dagolden@cpan.org>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Since ExtUtils::CBuilder 0.27_04 (bleadperl commit 06e8058f27e4),
CFLAGS and LDFLAGS from the environment have overridden the Config.pm
ccflags and ldflags settings. This can cause binary incompatibilities
between the core Perl and extensions built with EU::CBuilder.
Append to the Config.pm values rather than overriding them.
|
| |
|
|
|
|
|
|
|
| |
catfile() with an empty string as a first argument does *not*
produce an absolute path on VMS (and probably only does so by
accident elsewhere). For purposes of the test, it seems that
any absolute path would do, so this could probably be done
portably, but on the eve of 5.14 let's make a separate code
path for VMS and leave everyone else as is for now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On VMS only, the /DEFINE and /INCLUDE qualifiers are parsed off the
local copy of $Config{ccflags} and consumed in the process. This is
necessary because you're only allowed one of each of these clauses
in the compile command, so to add whatever has been requested for a
specific compile, we have to combine them with whatever Perl was
built with.
But since they are consumed, multiple compiles on the same EU::CB
object were only using the correct flags for the first one. Even
calling the have_compiler() check before compile() would make the
latter miss the defines and includes that were used to build Perl.
The solution is add a platform override that resets the local copy
of $Config{ccflags} from its original in %Config every time a
compiler operation is initiated.
Fixes smoke failures in ExtUtils::ParseXS.
|
| |
|
|
|
| |
Since the variable was empty, the include of ::Platform::MSVC failed
and it fell back to ::Base which tried to use "-o" as a parameter.
|
| | |
|
| | |
|
| |
|
|
|
| |
It used to use the same paths for temporary files in all tests. This blew up
randomly when the tests were run in parallel.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Remove the tests that try to send actual compile and link commands
to the shell and predict what their output will be. That can't
be done portably in the base class -- that's what the overrides
are for. Testing that properties get populated correctly and so
forth should be reasonably portable, though there is no guarantee
some of these won't be overridden as well (but leave them in for
now).
|
| |
|
|
|
|
|
|
|
| |
# New Ticket Created by (Peter J. Acklam)
# Please include the string: [perl #81888]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81888 >
Signed-off-by: Abigail <abigail@abigail.be>
|
| |
|
|
|
|
|
| |
The tempdir() function has the rather confusing default of *not* cleaning up
("because of issues with backwards compatibility") so one needs the CLEANUP
flag. (The analogous newdir() method in the OO interface doesn't suffer this
gotcha.)
|
| | |
|
| | |
|
| | |
|
|
|
ExtUtils::CBuilder now has blead as its upstream repository. The
distribution has been moved to the dist/ directory consistent with
this change.
|
