[Development] ELF Can run much platform

[Koehne Kai]

> Subject: Re:RE: [Development] ELF Can run much platform
>
>
> I didn't descript my question clearly. My question is, in another way, following.
> The file qt-sdk-linux-x86-opensource-2009.02.bin can run any platform, such as redhat5, redhat6,
> ubuntu12, and so on. How does it can do that?

It uses a statically compiled Qt. See e.g. http://doc.qt.digia.com/qtifw-1.2/ifw-getting-started.html . Also it's probably safest to compile the binary on the oldest distribution you want to support , but I'm not sure which distribution was specifically used for the file above ...

Regards

Kai

------------------ Original ------------------
From:  "Koehne Kai"<Kai.Koehne at digia.com>;
Date:  Sat, Dec 15, 2012 04:59 PM
To:  "ugiwgh"<ugiwgh at gmail.com>; "development"<development at qt-project.org>;
Subject:  RE: [Development] ELF Can run much platform

> Subject: [Development] ELF Can run much platform
>
> A Qt installing file can run much more linux platform. I'm very interest this.
> Any one can give me some tips? Any help will be appreciated.

I'm not sure I understand your question. Do you want to create a binary using the Qt libs that can be downloaded and executed on a lot of distributions & versions? Then you've several options:

- compile against LSB SDK 4.1 , which however still supports only Qt 4.2 (pretty outdated). It also requires your users to install the lsb package.
- use the Qt version of your choice (e.g. Qt 4.8), but ship the libraries yourself. To minimize external dependencies from the Qt libraries I'd suggest using the binary builds of Qt provided by the qt-project instead, which have been configured to be portable.

Anyway, it seems your question would have been better asked in qt-interest at qt-project.org, since this list is about the development _of_ Qt, not development _with_ Qt.

Regards

Kai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121216/171ddee9/attachment.html>