At 6:49 Uhr +0000 24.03.2002, p kent wrote:
>I just posted this to Usenet. zlib, libjpeg, libpng and libgd were all
>pretty simple to compile, but GD required some mucking about. But it seems
>to work now.
>
>However, scratch that bit about libgd being in the same folder as GD -
>apparently that's not the case, and I can have just GD in there. Which is
>the right thing to happen. GD 1.38 compiles to a shared lib of 324k on my
>machine.
>
>If anyone want sources or binaries, just tell me where to post them.
Damned cool! I suggest CPAN, so everyone can access it, but that requires that
you register as a developer. See
http://www.cpan.org/modules/04pause.html
for details. You don't have to worry about the namespace, since you are not going
to introduce a new module. Just make a nice Mac binary package and upload it into
your directory. *** (see footnote)
Needless to say, please ensure that all tests pass, or you'll get lots of complains
via e-mail ;-). You should also ensure that your package installs correctly with
the installme.plx droplet.
You may want to include all sources (with your patches, if any) and Makefiles,
but to keep the distribution compact, strip everything else from the libjpg, libpng
etc. library distributions. However, this should be your decision.
After you've uploaded (CPAN or wherever), please make an entry on the MacPerl
porters page. I'm sure Chris will give you a password. Welcome to the club :-).
[snip]
>FWIW, I built libgd statically and dynamically. GD.pm only seemed happy
>when I made libgd dynamic. The bizarre thing is it looks like I have to
>do this:
>
>MacPerl
> site_perl
> MacPPC
> auto
> GD
> GD <- that's a shared library
> libgd <- so's that
When you build the GD (shared) lib so that it uses the shared lib libgd, then of
course libgd has to be in the same directory as GD, or in the system extension
folder. As long as it works, that shouldn't be a problem (my DtfSQL module
does it this way, too).
Thanks much for your work.
Best regards,
--Thomas
***
For uploading, I recommend that you take the FTP-upload/HTTP-commit route,
since it turns out to be the most reliable way for me (your mileage may differ,
though):
(a)
The upload server is ftp://pause.kbx.de/incoming/, you *don't* need your name
and password for this server, do it anonymously. (I don't know whether or not the
PAUSE document mentions this by now, but I had some trouble to figure that out.)
(b)
Then, go straight to http://pause.kbx.de/pause/authenquery, log in (here you'll
need your password), and then confirm the upload by checking your uploaded
file (you'll see what I mean when you are on that webpage :).
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
