Sherm Pendley <[EMAIL PROTECTED]> writes: > To most developers using Cocoa or Carbon, building a "fat" binary is > painless - it's a matter of checking the right box in Xcode. The > problem I'm facing is that for CamelBones, because of the way Perl > builds its modules, the transition will be far more painful than it > will be for most apps.
Why would it be painful to compile perl and its modules as a fat binaries? I see that perl's hints/darwin.sh override the $archname with this comment: # Since we can build fat, the archname doesn't need the processor type archname='darwin'; Has anybody ever tried to build a fat perl? --Gisle
