Hi Autrijus, hi list,
I'm the Qt module maintainer and wanted to thank you for your astounding work!
People developing Perl/Qt applications were eager to have an easy way to
distribute their work, and you just offered that, in a so simple and handy
way that it's almost miraculous, thank you so much!
While testing pp with Qt for standalone executables, I found out that I needed
to use an almost-all-static version, where the Qt library and the Smoke
binding library needed to be statically built into the final XS library.
Now, such a special build would typically be stored in a separate hierarchy
and be fed to pp with the -I option...
But the problem is that pp doesn't use the perl convention, which is that -I
specified pathes have precedence over system-wide modules.
So my question is, would it be possible to have:
@@ -79,7 +79,7 @@
} @{opt(M) || []};
my %map;
- push @INC, @{opt(I) || []};
+ unshift @INC, @{opt(I) || []};
Module::ScanDeps::scan_deps(
rv => \%map,
so that custom, non-installed version of system modules can be used?
Cheers,
Germain
