On Sun, May 23, 2010 at 6:25 PM, Javier S. Pedro ma...@javispedro.com wrote:
3. Qt Desktop guarantees that an application built under Qt 4.5 headers
is binary compatible with Qt 4.6 libs. I'd like to know if we can guarantee
that an application built under Qt 4.6 headers but using no Qt 4.5
Attila Csipa wrote:
A single #ifdef can break such a setup, and
these things might not be apparent at first (as some of the changes
involve property names and values, so might even compile with the wrong
version, but will simply not work as desired - the most common case
exhibiting this
If there was a way we could explicitly tell the autobuilder to build
for 4.5 or 4.6 that would be nice. Something in the deb config file
for example. I've tried various ways but eventually gave up. As I've
stated before my app builds and runs fine on qt 4.5 (madde) and 4.6
(qt creator).
I realize
Attila Csipa wrote:
In theory you just depend on the proper version of libqt4-dev, but it's
tricky as you might indirectly reference libs that are also newer in the
SDK/new PR so end up with a 4.6 dependency (or broken build)
Seems that we need to follow on this, as it is clearly desirable
On Sun, May 23, 2010 at 5:25 PM, Javier S. Pedro ma...@javispedro.com wrote:
3. Qt Desktop guarantees that an application built under Qt 4.5 headers
is binary compatible with Qt 4.6 libs. I'd like to know if we can guarantee
that an application built under Qt 4.6 headers but using no Qt 4.5
