Hi all,
I'm in the process of porting a Perl application to Mac OS X; this Perl
application in turn relies on one shared library (libiconv), it's Perl XS
Module, another shared library (libosp), and it's command line front end.
AFAICT, the Perl stuff gets it's file locations and such from the Comfig.pm
module, so I'm not particularly owrried about that. But the two other apps
-- both managed by autoconf, BTW -- are more problematic.
I intend to have it eventually be installable from a Package Maker package,
but I really would like the various shared libraries and header files be
installed in a sane location. Does anyone have any suggestions for how to
set autoconf's --prefix, --exec-prefix, etc. etc. so files are installed in
the correct, officially sanctioned, places?
In case anyone is curious, I'm porting the W3C HTML Validator
<URL:http://validator.w3.org/> to run in various modes (command line,
standalone (possibly with a Cocoa GUI ;D), and as a BBEdit plugin) on Mac
OS X. The Validator itself is written in Perl, but it relies on OpenSP
<URL:http://openjade.sf.net/> for SGML/XML parsing and POSIX iconv for
character encoding conversion.
I could probably just say "install fink" in a README, but I'd rather have
it all nicely "Double-Click" installable from Package Maker.
--
"I don't want to learn to manage my anger;
I want to FRANCHISE it!" -- Kevin Martin
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
