Hello
On 14/06/2010 00:53, David Golden wrote:
> 2010/6/13 Alberto Simões :
>> For windows, I need to create the .bat files, and I hope Module::Build
>> does that automatically for script files.
>
> It happens in make_executable which is called by process_script_files,
> which is ultimately calle
2010/6/14 Alberto Simões :
> Unfortunately Build --debug is too laconic :) it just hows ACTION_code.
> There isn't any way to force a more in-depth trace?
Only the normal perl approaches. (e.g. "perl -D" with a debugging perl)
(Though I'd welcome patches that improve the instrumentation using --
Hello
Unfortunately Build --debug is too laconic :) it just hows ACTION_code.
There isn't any way to force a more in-depth trace?
Thank you
Alberto
On 14/06/2010 00:53, David Golden wrote:
> 2010/6/13 Alberto Simões :
>> For windows, I need to create the .bat files, and I hope Module::Build
>> d
2010/6/13 Alberto Simões :
> For windows, I need to create the .bat files, and I hope Module::Build
> does that automatically for script files.
It happens in make_executable which is called by process_script_files,
which is ultimately called by ACTION_code (I think).
If you run "Build --debug" on
Hello.
Sorry for being so boring, but I am trying to prepare a kind of
complicated module (with a C library and a bunch of particularities) and
as I am still newbie on Module::Build, things get.. complicated.
I am preparing some script files in the beginning of the install action
(or fake install
