in reply to Re: MakeMaker for testing only
in thread MakeMaker for testing only

I don't understand how I could dispense with the libscan sub. If I placed scripts, modules, cc files, and so on in the top-level directory (or in any subdirectory for that matter), won't they all be scanned by MakeMaker and get copied into blib when I do a make?

I tried echoing out the file names that are passed to my fake libscan, and all the *.cc, *.h, *.pm files are included. Before I filtered out the ones I didn't want, they appeared in the sections C_FILES, H_FILES, PM_TO_BLIB, etc. of my Makefile.

As I mentioned, this is a C++ main program with embedded perl, so I am not trying to install it like a perl module. I have my own installation scripts already. But perhaps there are ways to adapt the MakeMaker installation process to my needs. I'll look into it further.