Gabor Szabo wrote:
Hi,
I would like to create a list of modules that need compilations
as opposed to those that are pure perl
Is checking for a file with .xs .c or .h extension in the distribution
the correct
thing to do? Is there a better way to collect this information or
is it alrady
available somewhere?
This looks like an heuristic.. which leads us to Klortho #11953 ;-)
It would work for most modules, but would miss those that generates
the C and XS files on the fly, like Perl::API
» http://search.cpan.org/dist/Perl-API/
But I guess there aren't that much modules like this one.
In addition I would located modules that have dependecies that are not
available on CPAN. (e.g. most of the DBD::* modules are such
but DBD::SQLite is not such a module as it includes all the C code
of SQLite)
I keep track of external Perl modules in Module::ThirdParty
» http://search.cpan.org/dist/Module-ThirdParty/
But you would still need something for tracking modules that needs
external C libraries, but I think this should simply be included in
the module which tracks modules that need compilation, as a field
need_external_libs, and why not also a field with the names of
required libs.
--
Sébastien Aperghis-Tramoni
Close the world, txEn eht nepO.
