Thanks for this.

I got an iPod last week funnily enough so I might give it a go. I've gotta ask thoguh, is there a particular reason that it needs compiling before use? I've not tried it yet but I almost always get these things wrong. It'd be nice if the software was ready to run after downloading.

FuZion.

its not Andy's software that needs compiling, but rather the perl modules that are required to get the backend stuff working.

Regards

Mark

_________________
IceStar Media Ltd.

Quote:

Poster: Mark Date: 29-Mar-2006 7:24:52 its not Andy's software that needs compiling, but rather the perl modules that are required to get the backend stuff working. Regards Mark

I wish the user friendlyness of Amiga applications would remain the same. But it's too much to ask from the developers that port stuff to AmigaOS from Linux, because they have done a lot of work for the ports already. I wish there was another way.

Firbodi

_________________
MicroA1 G3, 512MB RAM, DVD-RW; and A1-SE G3,512MB RAM, CD-RW & DVD-ROM
Avatar: Perspolis, Capital of Achaemenid Empire 500 B.C.

andy:great!

keep the good work up!.

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

Quote:

Quote: Poster: Mark Date: 29-Mar-2006 7:24:52 its not Andy's software that needs compiling, but rather the perl modules that are required to get the backend stuff working. Regards Mark I wish the user friendlyness of Amiga applications would remain the same. But it's too much to ask from the developers that port stuff to AmigaOS from Linux, because they have done a lot of work for the ports already. I wish there was another way.

It's a dilema for me as to what to do with ported perl modules. (apod itself is not a port BTW).

The traditional perl way to install these is by using make, being a unix centric program, it expects all the typical devloper tools to be available even in a user install.

If I pre built the archives (as I have for perl_Reaction) then the various packlists that perl creates as it installs would be incorrect for the users install and so version checking and uninstalling becomes problematic (if upgrading or removeing a module).

Most of those archives aren't actually compiled BTW they are "just" installed by make.
(of course two of them are xs perl extentions and so are compiled c code [XML::parser and Unicode::String IIRC])

Tips: when running perl and make during the install process, make sure you have the latest versions of make and abc-shell, and up the stack to at least 200k.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

andy:but what about dooing an implementation where you just can use shared libs?...or do u need more to accomplish such? (ie..are we missing anything?`)

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@toaks

Perl is using dynamic loaded objects, allready. The two modules mentioned above as xs modules, are such. They aren't shared as such as each instance of perl loads it's own copy, but they are dynamicaly loaded, ie only those required are loaded at run time.

The isues are more about installation, than implementation.

It would be nice to have a complete shared library way of doing it, with a perl.library built from libperl and a very minimal perl excutable, but the way these link together makes this very difficult if not impossible.

But, even given that, you would still have this "unamigalike" installation of modules to contend with.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

thanks alot! :)

i simply love this piece of work!

fuskoSCN -aka- Torgeir Vee