You really need the MacPerl book, which has a chapter on building MacPerl and MacPerl extensions. At 17.35 -0400 1998.07.06, Benjamin Garrett wrote: >1) Do I have to use xsubpp to create the .pm file? Or can I create it >myself? It seems like if I create an .xs file and the .pm file to >bootstrap the library, it should work fine. Yeah, you can just create a .pm and .xs file by hand. >2) Additionally, what do I need to do with the .h files that specify the C >interface? It seems like they are "#include" 'd into the .xs file, but are >they really necessary, since it seems like the .xs file has all of the >information necessary for MacPerl to use the library functions? As long as the information is in there somewhere ... maybe I misunderstand the question, but if everything in the .h file is in the .xs file already, then fine. If not, then include it. >3) Finally, my shared library simply needs to go in the Extensions folder >inside the System Folder, right? Nope. Examine where the shared libraries for GD and Mac::Files, etc., go. Yours would probably go in: :site_perl:(?:MacPPC|MacCFM68K):auto:Some:Module:Module Where the last name "Module" is yoru shared library. Hope this helps. Get the book if you don't have it, it is most likely going to be invaluable in building the extensions. -- Chris Nandor mailto:pudge@pobox.com http://pudge.net/ MacPerl: Power and Ease (ISBN 1881957322), http://www.ptf.com/macperl/ %PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6']) ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch