in reply to Re^5: nmake error
in thread nmake error

Sorry. Your now deep into the quagmire that is M::M generated makefiles. I cannot help you there as I refuse to touch that stuff--it either works or it doesn't as far as I am concerned.

That command line is a good example of the mess that gets generated. You have one call to perl nested inside backticks, inside another call to perl.

The purpose of the nested call is to extract the dirname from "blib\bin"?

Which then gets prepended to the string "my_code/images/wellness/well_56.jpg"?

And all of that to copy a file. What a mess.

I really do hope that Mr. Schwern manages to kick M::M into the bit bucket and replace it with something that takes a rational approach to solving the problem of cross-platform building.

Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.

Replies are listed 'Best First'.
Re^7: nmake error
by William G. Davis (Friar) on Dec 28, 2004 at 08:09 UTC
    "Module::Build is the official heir apparent to MakeMaker and we encourage people to work on M::B rather than spending time improving MakeMaker." - ExtUtils::MakeMaker::FAQ.
[reply]

      While Module::Build does a nice job with modules, it really doesn't do a good job with applications. Simple things like creating a directory that is specified by the user and copying images/templates/configuration info/data files, are just a pain in the tail. So until Application::Install gets written, lots of us will be using MakeMaker.

      g_White
[reply]

        MakeMaker is pretty bad for installing applications too, unfortunately.

[reply]

In Section Seekers of Perl Wisdom