On Tue, Sep 18, 2012 at 2:48 PM, Felix Petriconi
<
felix.p...@mevis.de> wrote:
> Hi,
Hello,
> I am trying to get the Ruby installation running as native 64 bit
> application. So far I was capable of getting Ruby and the DevKit build and
> running smooth together with mingw64 4.7.1.
>
Nice!
Can you tell us which version of Ruby? have you tried the automated
builds instead?
Please note that Ruby 1.9.3 still lacks some backports for better x64
support, 2.0 on the other hand have all those and pass all tests.
> As well I was capable of getting certain GEMs and some of the, like Cucumber
> build fine with the DevKit. Great so far (thanks to the work the
> contributors to the rubyinstaller has done!)
>
> Then I tried to install nokogiri and now I am stuck.
> I already compiled libiconv and libxml2 (hopefully successful.) But I assume
> that I did something wrong during that process because I get error message
> that libxml2/parser.h cannot be found even I pass it as extra parameter with
> --with-xml2-include pointing to the include folder, etc when I try to
> install the nokogiri GEM.
>
> Has here someone a recipe of how to build it correctly so that it works
> together with the DevKit?
>
You will need libiconv and zlib Knapsack packages (search the group)
Once you have it those in the PATH (see Knapsack announcement on env
variables usage) you can clone Nokogiri repository and build locally.
Nokogiri uses mini_portile to build a static version of libxml2 and
libxslt. Perhaps a Knapsack recipe can be provided to avoid the manual
build process...
>
> As a side note, I saw that the innosetup task in inno.rake uses the
> "ProgramFiles" environment variable. But the "Inno Setup 5" on a Win7 64
> system is located in "ProgramFiles(x86)" path.
>
Thanks, we haven't modified the InnoSetup scripts to handle x64 installers yet.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry