James,

> On Wed 13 Jun, Richard Proctor wrote:
> >
> > On Wed 13 Jun, James Taylor wrote:
> > >
> > > I would very much like to be able to use GD on RISC OS but don't
> > > know where to start when it comes to getting it working via Perl.
> > > Please could someone help me out. Thanks.
> >
> > On the plus side I have done it, one the minus I cant find where
> > I put it :-(

> Can you remember roughly what was required to get it to work?
> If it is a simple matter of downloading a Perl-only CPAN module
> then I can do it for myself, however, if it involves some C hacking
> I will have to rely on someone who knows what they are doing.

We are looking back four+ years ... I have to say I cant realy remember
It is unlikely to have been compilcated - if it was I would have kept it
(on my old system I got rather short of disc space and had to be
ruthless towards the end).  I might have compiled C - I can not remember.

> > The perl in question doesnt any longer use GD - its output
> > is now textual.

> Do I assume correctly, that by saying "perl" with a lower case P, you
> mean the executable, and that what you are saying here is that a new
> GD-aware perl would need to be compiled for this to work?

I have a perl program that works, it used to use GD, but I changed the format
of what it generated from graphical to textual - it was not very complicated.
This was a case of a picuture did not tell a thousand words all I had to output
was one of three words and a number!

> If there's any chance of getting GD to work on RISC OS, and therefore
> for me to be able not only to practise using GD from Perl, but also to
> write useful little graphics utilities on RISC OS, then I'd be very
> interested. I can't be the only RISC OS Perl programmer that would
> find GD on RISC OS an exciting prospect.

> Any further help would be much appreciated. Thanks.

> PS. I'm moving house this week and at some point will have to disconnect
> and pack the computer. As a result I won't have much time to play with
> all this until I get settled into the new place. Ironic how the timing
> of these things work isn't it. :-( Oh well...

Richard (at work)



Reply via email to