--------------enig141AA794C345C3AE6E9CF5AC
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Vincent Fourmond wrote:
>> I guess I am just trying to gauge the chances of a qt ruby gem being b=
uilt?
>=20
>   If I understood right, you're looking for a gem that would also
> include Qt4 libraries, is it right ? There would be no legal problem in=

> distributing it, but I think it will be rather tricky to make. I hope
> I'm wrong.
>=20

I'm fairly sure that the wx gem comes / used to come (no idea about the
changes with the SWIG rewrite) with wx linked into it. I'm not quite
sure that it's the best solution (people might want to use a custom wx
version), but if the build configuration was sane, it's probably good
enough for most purposes people will need and the ones that can make a
custom wx build can as well make a custom wxRuby from it.

Digressions aside, I don't think this would be technically infeasible
for Qt. Either Qt is designed (on Windows) to be statically linked into
an executable, in which case doing so for a Ruby extension library
shouldn't be a problem, or to be provided as a separate runtime DLL, in
which case dropping in this DLL into Ruby's bin directory should solve
the problem on any NT-based version of Windows - and I think rubygems
already lets you install an executable, so making this the DLL for
qtruby-mswin32 shouldn't be a problem.

David Vallner


--------------enig141AA794C345C3AE6E9CF5AC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFUmYAy6MhrS8astoRAuoiAJ4/LZ9tR0Q8njvBBEgS0lAmsNNTgACeLSaL
n03ZPCa0FjayCY+i5OOefCQ=
=ewsC
-----END PGP SIGNATURE-----

--------------enig141AA794C345C3AE6E9CF5AC--