From: PaulC <paulch@...>
Date: 2001-02-08T15:38:16+09:00
Subject: [ruby-talk:10548] Re: Linking statically with xmlparse - how?


Florian,

This may not be the most efficient solution however I believe
that the following should build a fully static ruby executable
with all the the extension modules linked statically -

- Unpack xmlparse into the ext directory
- touch xmlparse/MANIFEST (extml.rb checks for this)
- If your expat libs/headers are not in a standard location edit
  $CFLAGS/$LDFLAGS in xmlparse/extconf.rb
- From the main ruby directory
  ./configure --disable-shared --with-static-linked-ext ; make

There is probably an easier solution however this should work

Paul

"Florian v. Walter" <florian.walter@curry.de> wrote in message
news:3A812E59.471F60F9@curry.de...
> Hi,
>
> I'd like to assemble a completely statically linked version of Ruby
> 1.6.2 together with all extension modules and the XMLParser module
> from http://www.yoshidam.net/Ruby.html#xmlparser.
>
> I have managed to successfully compile a statically linked version of
> Ruby by uncommenting the related statements in ext/Setup as advised in
> the README.
>
> Now I'm stuck with integrating the XMLParser into the compilation
> procedure. In the README of XMLParser there is a mention of the
> possibility of statically compiling it in the Ruby executable but no
> further instructions how to do so.
>
> While I'm trying further any help would be very appreciated.
> Thanks!
>
> Florian.
>
> --
> Florian v. Walter (mailto:fwal@curry.de)
> CURRY. SMILE @ WORK.
> Curry Communication GmbH, Behringstrasse 28a, 22765 Hamburg
> Tel.: +49.40.398344.00, Fax: +49.40.398344.09
> -- Please do not send HTML or RTF emails and large attachments. --