@@ -26,9 +26,11 @@ If you need to maintain a package written using ''ExtUtils::MakeMaker'' you may
...
@@ -26,9 +26,11 @@ If you need to maintain a package written using ''ExtUtils::MakeMaker'' you may
./Build test
./Build test
./Build install
./Build install
The similarity to the use of ''ExtUtils::MakeMaker'' above is intentional. For most simple projects both approaches require about the same effort and both are as easy to understand as the other. As soon as the project gets more involved ''Module::Build'' is the better choice. In addition to be based on Perl only it is also a more modern code base with better extensibility using more modern object oriented techniques.
The similarity to the use of ''ExtUtils::MakeMaker'' above is intentional. For most simple projects both approaches require about the same effort and both are as easy to understand as the other.
A large number of members of the Perl community use ''Module::Build'' in some form. It has become the de facto standard.
Ever since ''Module::Build'' became available there has been controversy as to which approach is better. As it turns out, having to rely on ''make'' is often not a curse but a blessing. ''make'' allows dry runs with ''make -n'' which ''Module::Build'' does not support. For all relevant platforms ''make'' is fundamental enough that there is at least one version of ''make'' available that supports all important modern features.
As the situation presents itself as of this writing there are plans to remove ''Module::Build'' from Perl core (sometime after version 5.020). ''ExtUtils::MakeMaker'' is now the preferred tool and is still used and maintained actively.