Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:csbuild:Perl
perl-ExtUtils-Depends
perl-ExtUtils-Depends.spec
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File perl-ExtUtils-Depends.spec of Package perl-ExtUtils-Depends
# # - ExtUtils-Depends - # %define real_name ExtUtils-Depends %define perl_vendorlib %(eval "`perl -V:installvendorlib`"; echo $installvendorlib) %define perl_vendorarch %(eval "`perl -V:installvendorarch`"; echo $installvendorarch) %define perl_archlib %(eval "`perl -V:archlib`"; echo $archlib) %define perl_privlib %(eval "`perl -V:privlib`"; echo $privlib) %define maketest 0 Name: perl-%{real_name} Summary: ExtUtils::Depends - Easily build XS extensions that depend on XS extensions Version: 0.302 Release: 1 Source: http://search.cpan.org/CPAN/authors/id/A/AM/AMBS/Benchmark/%{real_name}-%{version}.tar.gz License: Artistic Group: Development/Libraries/Perl AutoReqProv: on Url: http://www.cpan.org Buildroot: %{_tmppath}/%{name}-%{version}-%(id -u -n) Buildarch: noarch %description This module tries to make it easy to build Perl extensions that use functions and typemaps provided by other perl extensions. This means that a perl extension is treated like a shared library that provides also a C and an XS interface besides the perl one. This works as long as the base extension is loaded with the RTLD_GLOBAL flag (usually done with a sub dl_load_flags {0x01} in the main .pm file) if you need to use functions defined in the module. The basic scheme of operation is to collect information about a module in the instance, and then store that data in the Perl library where it may be retrieved later. The object can also reformat this information into the data structures required by ExtUtils::MakeMaker's WriteMakefile function. When creating a new Depends object, you give it a name, which is the name of the module you are building. You can also specify the names of modules on which this module depends. These dependencies will be loaded automatically, and their typemaps, header files, etc merged with your new object's stuff. When you store the data for your object, the list of dependencies are stored with it, so that another module depending on your needn't know on exactly which modules yours depends. %prep %setup -q -n %{real_name}-%{version} chmod -R u+w %{_builddir}/%{real_name}-%{version} %clean [ "%{buildroot}" != "/" ] && rm -rf %{buildroot} %build grep -rsl '^#!.*perl' . | grep -v '.bak$' |xargs --no-run-if-empty \ %__perl -MExtUtils::MakeMaker -e 'MY->fixin(@ARGV)' CFLAGS="$RPM_OPT_FLAGS" %{__perl} Makefile.PL `%{__perl} -MExtUtils::MakeMaker -e ' print qq|PREFIX=%{buildroot}%{_prefix}| if \$ExtUtils::MakeMaker::VERSION =~ /5\. 9[1-6]|6\.0[0-5]/ '` %{__make} %check %if %maketest %{__make} test %endif %install %if 0%{?suse_version} %perl_make_install %perl_process_packlist %else make DESTDIR=$RPM_BUILD_ROOT install_vendor find $RPM_BUILD_ROOT/usr -type f -name perllocal.pod |xargs -i rm -f {} find $RPM_BUILD_ROOT/usr -type d -depth -exec rmdir {} \; 2>/dev/null %endif find %{buildroot} -name "perllocal.pod" -o -name ".packlist" -o -name "*.bs" |xargs -i rm -f {} %files %defattr(-, root, root) %doc Changes README MANIFEST %doc %{_mandir}/man?/* %dir %{perl_vendorlib}/ExtUtils %{perl_vendorlib}/ExtUtils/Depends.pm %if 0%{?suse_version} /var/adm/perl-modules/%{name} %endif %changelog * Sat Feb 27 2010 Holger Manthey <holger.manthey@bertelsmann.de> - Initial build.
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor