Am 14.03.2006 um 05:29 schrieb Edward Moy:
On Mar 13, 2006, at 4:38 AM, Dominic Dunlop wrote:
On 2006–03–13, at 12:53, Manfred Bergmann wrote:
I use some Perl Modules in some of my application, accessed
through Camelbones.
I have notices that some Perl Modules use compiled C-Code, e.g.
HT
Am 13.03.2006 um 23:38 schrieb Dominic Dunlop:
On 2006–03–13, at 12:53, Manfred Bergmann wrote:
I use some Perl Modules in some of my application, accessed
through Camelbones.
I have notices that some Perl Modules use compiled C-Code, e.g.
HTML-Parser.
Now how does it work to build these m
On 2006–03–13, at 19:29, Edward Moy wrote:
Nope, we build perl universal, much like README.macosx (though
without the SDK stuff). Then we strip out the architecture we
don't need to save space on the final hardware. We also strip out
the -arch flags from Config.pm because most users only
On Mar 13, 2006, at 4:38 AM, Dominic Dunlop wrote:
On 2006–03–13, at 12:53, Manfred Bergmann wrote:
I use some Perl Modules in some of my application, accessed
through Camelbones.
I have notices that some Perl Modules use compiled C-Code, e.g.
HTML-Parser.
Now how does it work to build thes
On 2006–03–13, at 12:53, Manfred Bergmann wrote:
I use some Perl Modules in some of my application, accessed through
Camelbones.
I have notices that some Perl Modules use compiled C-Code, e.g.
HTML-Parser.
Now how does it work to build these modules as Universal Binaries?
The README.macosx
Hi there.
I use some Perl Modules in some of my application, accessed through
Camelbones.
I have notices that some Perl Modules use compiled C-Code, e.g. HTML-
Parser.
Now how does it work to build these modules as Universal Binaries?
Although my application is build as Universal Binary and I
