Did you use h2xs? That makes life much easier.
If you have modules that exist only for testing purposes, stick them in t/lib and adjust the library path property in the test. You'll also have better luck if you stick with t/*.t files as Test::Harness expects.
To get your name right, you could either dig through the MakeMaker docs (which have improved in recent versions; feel free to upgrade), or stick with the normal convention of putting your module in the appropriate directory with the appropriate name under lib/. I recommend the latter.
In reply to Re: Makefile.PL even weirder on Windows
by chromatic
in thread Makefile.PL even weirder on Windows
by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |