Build.PL usage during module authoring

John M. Dlugosz has asked for the wisdom of the Perl Monks concerning the following question:

I used module-starter to create the structure. My initial code is working.

But I added another file in the same directory as the .pm file, that is "required" by the code at run time. The code is located along the lines of in MyProject/lib/Path/Name.pm.

The error is that the file is not found, and it's looking in MyProject/blib/lib.

I added the file to the MANIFEST. The basic instructions from the doc page is:

  perl Build.PL
  ./Build
  ./Build test
  ./Build install
[download]

So I tried running Build (without any argument) again, and it didn't do anything. Now ./Build test has been enough to re-run as I make changes to my .pm file, so it knows to copy that normally.

Can someone fill me in on what's (not) going on?

Comment on Build.PL usage during module authoring Download Code

Replies are listed 'Best First'.
Re: Build.PL usage during module authoring by Anonymous Monk on May 12, 2011 at 14:29 UTC
Can someone fill me in on what's (not) going on? I say, someone is playing a practical joke on you, they're remote controlling your terminal :) shell commands Read more... (694 Bytes) shell session Read more... (8 kB)	[reply] [d/l] [select]
Re^2: Build.PL usage during module authoring by John M. Dlugosz (Monsignor) on May 13, 2011 at 01:41 UTC
All I got out of that was that you run `perl Build` again. Read more... (2 kB) I can delete blib, and running `perl Build` will make it reappear. It contains the main .pm file, but not the other files I have in the original `lib` directory, even though the one I'm interested in is named in the Manifest. Maybe it only copies files with a .pm extension? Your example added another module to the tree, not an internal file that would be "required".	[reply] [d/l] [select]
Re^3: Build.PL usage during module authoring by Anonymous Monk on May 13, 2011 at 02:39 UTC
Maybe it only copies files with a .pm extension? Your example added another module to the tree, not an internal file that would be "required". Yes it does, and that is a good thing. Why? Because copying .pl files by default is an often overlooked and most surprising feature of ExtUtils::MakeMaker , new authors just don't expect it, and they forget to check blib Read more... (1250 Bytes) If you want Module::Build to do the same, you'll have to be proactive, one way is Module::Build::Cookbook#Adding new file types to the build process. Also, consider Module::Build::API#share_dir or AutoSplit Oh, and now is a good time to review How do I post a question effectively? :)	[reply] [d/l]
Re^4: Build.PL usage during module authoring by John M. Dlugosz (Monsignor) on May 13, 2011 at 02:53 UTC
Re^5: Build.PL usage during module authoring by Anonymous Monk on May 13, 2011 at 03:25 UTC