It is not (only) using EU::MM that is the problem, it is what it produces once you get the incantations correct. The makefiles it produces are unintelligible(* see below for an example).

I agree. Which is why I use Module::Build and avoid all that tedious mucking about with make files completely.

I have projects that use compilers other than a C compiler...how do you integrate those into this mess?

With M::B I just write new dependencies, actions, etc. in a nice subclass.

The directory structure imposed by these tools does not accommodate me. Storing source files in a directory called ./lib?

For perl files this doesn't bother me at all personally. However, if it did, I'd just tweak M::B so it looked somewhere else. For non Perl files I can stick them in whatever directories I like and tweak M::B appropriately.

Trying to force fit all these into the directory structures required by these build tools is insanity.

With EU::MM it can be a pain I agree. With M::B I've found it quite pleasant.

And from what I have seen of the alternatives to EU::MM, be it M::B, or M::I and others, they simply add extra layers on top of the underlying problems. You simply end up with the same unintelligible mess of a make file, but you are now an extra layer (or two) removed from how it is produced.

For M::B at least this is untrue. There is no Makefile. The installation process is handled by a pure perl program that is very tweakable.

I'm curious - what do you use for your automated build/install processes?

In reply to Re^7: Programming Department by adrianh
in thread Programming Department by danambroseUK

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.