On Mon, 1 Feb 1999, Jefferson R. Lowrey wrote: > >So if you really need this, it's time to buy a MacOS compiler if you > >don't already have one and pay attention to the "how to build an XS" > >thread. Or maybe, if you're lucky, Chris or Arved or someone else > >who can build XS will take pity. > > I think this is XS Lite installment I'm waiting for (or maybe have > misunderstood from the earlier) -- 'How do I build <generic>.XS that I got > from CPAN'. Mind you, this is not "How do I *port* <generic>.XS". > > Like I said, maybe I misunderstood the previous XS Lite installements, and > it did answer this question. If so, "in the parlance of the streets", "my > bad". I haven't covered "generic" CPAN XS, per se, but truth be told, we're basically there. If it's a single .xs file involved, you ought to be able to compile and link if you have PerlStub, MathLib, RunTimeLib and the appropriate C or C++ lib. Sometimes a library or two will be redundant, but I've been working towards describing a set that covers 99% of all cases. ToolBox stuff needs InterfaceLib also. The default *BuildRules files, as they exist right now, don't necessarily handle multiple source files quite right, so you have to fiddle with them. Math::Random is one of these. So until I cover this situation, one approach is to BuildProgram, let it fail, and extract the offending command from the *.makeout' file, edit it, and rerun it by itself. But that's what I'm really working towards: "generic" builds. If it's a question of porting, well, that's C or C++ knowledge - another matter entirely. Arved ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch