At 11:23 Uhr -0800 09.02.2001, Peter Prymmer wrote:
>Thomas,
>
>Does adding some code that looks like:
>
>if ($^O eq 'MacOS') {
>
> #...
>
>}
>
>to the installperl script help with any of the missing stuff?
>
>Peter Prymmer
>
>On Fri, 9 Feb 2001, Thomas Wegner wrote:
>
>> [snip]
>> >
>> >A scan of ":macperl_src:perl:macos:ext:Mac" compared to
>> >":macperl_src:perl:lib:Mac" shows, that
>> >
>> >AETE,
>> >Apps,
>> >DCon,
>> >ExtUtils,
>> >ImageCompression,
>> >SAT
>> >
>> >are not built and/or installed. All files in
>> >":macperl_src:perl:macos:lib" are not installed, too.
>>
>> In an update to the Update thread :), I'd like to add the following
>> as a result of a second scan:
>>
>> -Mac:: Apps::Launch doesn't get installed.
>>
>> -Mac::Navigation and Mac::Notification don't get built and installed
>>
Short answer: I don't know :). I have no idea what this script does and where/whether
it gets called.
A look at my build log shows two "For dir in ..." loops, one for a 'Build of all', and
one for a 'Build of install' for the ":macperl_src:perl:macos:ext:Mac" modules. The
'dirs' definition in the makefile ":macperl_src:perl:macos:ext:Mac:Makefile.mk"
controls which modules get processed in the for loop. Actually, the extension modules
DCon, ImageCompression, Navigation, Notification and SAT are not included in that
definition list. This explains why they don't get built and installed.
Mac::AETE::*, Mac:: Apps::Launch and ExtUtils are standard Perl modules and need not
to be built. I really don't know why they don't get installed.
The modules in ":macperl_src:perl:macos:lib" are also plain Perl modules (Config.pm,
ExtUtils::Miniperl.pm, ExtUtils::MM_MacOS.pm and re.pm) and should be installed, I
guess, although an older module re.pm already exists in ":macperl_src:perl:lib:".
Best regards,
--Thomas
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
