[RQt-devel] qtbase builds on windows

[Michael Lawrence]

On Fri, Dec 24, 2010 at 9:48 AM, Nicholas Lewin-Koh <
lewin-koh.nicholas at gene.com> wrote:

> Hi Guys,
> Sorry I have been on vacation and avoiding my email. I can build a binary
> and send it around but here are the instructions;
>
> Needed:
> qtsdk
> cmake
> rtools
> and optionally msys. Note that if you are not using msys (bash shell for
> windows) you probably need to change the -G "msys" (or something) in
> Makefile.win in the src directory.
> Rtools, and Qt bin directoey with dlls need to be in your path. Also make
> sure there are no other copies of the qt dll in your path, as we were
> pulling our hair out over a link error till we discovered that miktex has
> the qt dll in its bin directory duh. I will do a little work over the break
> and see if I can update the make file to work with the dos cmd shell instead
> of msys. As micheal said I don't think a static build with qt is possible
> without a lot of work to export everything from the dlls and link it
> statically. I vaguely remember fiddling with that once, and I think it is
> possible to convert dlls to static libraries,


Might not be too hard:
http://www.download3000.com/download_397.html


> but until we find out how to cure alzheimers, that will remain another void
> in my vacuous head. Or at least till I feel like putting down my wood
> working tools and doing some coding ;P
>
> Happy holidays to all! and I will see about the binary as a christmas
> present ;)
>
> Nicholas
>
>
>
> On Wed, Dec 22, 2010 at 8:53 PM, Michael Lawrence <
> lawrence.michael at gene.com> wrote:
>
>> Static build does not seem feasible for Qt. Qt does not provide static
>> libs, so, as I understand it, it's not possible to statically link with it.
>> Would have to build Qt ourselves. The current idea is to place the DLL's in
>> the lib directory of the package at build time and then set the PATH
>> environment variable to the lib directory when the package is loaded. This
>> still seems open to weird Windows conflicts, but the user should not have to
>> install anything.
>>
>> GTK+ apparently explicitly loads modules at runtime, so static linking
>> simply does not work. So I'll have to use the same strategy for RGtk2.
>>
>> I'll get the binary from Nicholas and then you guys can try it out; just
>> need Qt installed.
>>
>> Michael
>>
>>
>> On Wed, Dec 22, 2010 at 8:42 PM, Hadley Wickham <hadley at rice.edu> wrote:
>>
>>> Awesome!  And it's a static build, right? So end-users just need the
>>> package, and no other dependencies?  (Does that make it huge?)
>>>
>>> Hadley
>>>
>>> On Wed, Dec 22, 2010 at 9:32 PM, Michael Lawrence
>>> <lawrence.michael at gene.com> wrote:
>>> > Just wanted to announce that Nicholas and I figured out how to get
>>> qtbase to
>>> > build on Windows yesterday. The necessary changes have been committed.
>>> Maybe
>>> > Nicholas can run a R CMD builld --binary to get a binary for us to
>>> > distribute until we work things out with CRAN. Building the binary
>>> requires
>>> > the same setup as building other R packages, with the obvious initial
>>> > requirements of Qt and cmake.
>>> >
>>> > Michael
>>> >
>>> > _______________________________________________
>>> > Qtinterfaces-devel mailing list
>>> > Qtinterfaces-devel at lists.r-forge.r-project.org
>>> >
>>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/qtinterfaces-devel
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Assistant Professor / Dobelman Family Junior Chair
>>> Department of Statistics / Rice University
>>> http://had.co.nz/
>>>
>>
>>
>
>
> --
> "The bear and the goat were married and lived together until the end of
> their days. Either the goat went mad or the bear became sane."
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/qtinterfaces-devel/attachments/20101224/4d0840b0/attachment.htm>