Hi Burak: 2009/4/10 Burak Gürsoy <burakgur...@gmx.net>: >> -----Original Message----- >> From: Paul LeoNerd Evans [mailto:leon...@leonerd.org.uk] >> Sent: Friday, April 10, 2009 6:17 PM >> To: Ovid >> Cc: module-authors@perl.org >> Subject: Re: "a lot of silliness" about Module::Build >> >> I find this too. Of all my modules, any of them that don't have XS code >> in them simply provide a dual Build.PL / Makefile.PL as written by >> M::B's create_makefile_pl => 'traditional' setting. > > I'm bundling a normal Makefile.PL for now but I think that I'll eventually > use that option. But I always use M::B to build distributions and never > duplicate that part in Makefile.PL. It's only there for compatibility > nothing else. > >> It only becomes even vaguely complicated on a few of my XS ones, where >> M::B expects to find lib/Foo/Bar.xs whereas EU::MM wants only Bar.xs >> >> This random inconsistency annoys me - IMHO M::B's behaviour here is >> much more preferable, for reasons of being able to find the code, of >> making the file unique in case I want more than one,... > > I've experienced the same issue in one of my modules, but that's easy to fix > by adding this: > > xs_files => { 'Bar.xs' => 'lib/Foo/Bar.xs' }, > > then you can use a regular Makefile.PL too. > When developing an XS module, I came to the same problem. But then I just gave up on MakeMaker, and instead made it a passthrough for M::B
I chose to do this so that I could put all my C code into its own src/ folder, and install from there. > > > > I think EUMM is okay to support for simple Perl-only modules, but things like "recommends" in Module::Build make it really attractive to me as a CPAN developer. So I use simple EUMM modules where possible, but otherwise if I need to have a slightly more complex build, I switch to Build.PL I think we should work to slowly phase out EUMM, since supporting it is undoubtedly a nightmare (writing Makefiles and calling those?!). M::B lets it all be done from Perl itself, and seems to be reaching a point where it's mature/stable enough for real widespread use. Plus being able to subclass it is tres cool. Just my two cents. Cheers, Jonathan (PAUSE: FREQUENCY)