[maemo-developers] Non-experimental QT versioning in Autobuilder (was: QT Packages, Repositories and PR1.2)

[From: ianaré sévi]

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 not every app is so simple, since mine is more of a learning
experience. There would be unforeseen problems in trying to determine
this automagically. However the dev should be able to specify what to
build for.

- ianaré sévi



2010/5/24 Javier S. Pedro <maemo at javispedro.com>:
> 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 problem IMO being finger scrolling, for example).
>
> You mean a #define being X in 4.5 and Y in 4.6, with X != Y? This is probably
> the cause for the missing guarantees in current Maemo Qt versions ABI
> compatibility.
>
> As for runtime stuff (for ex. a flag that does nothing in 4.5 but is
> implemented in 4.6) packager would need to add forced depedencies on 4.6 if
> he does not want 4.5 users to install the package (much like the current
> problem I have with certain hildon-desktop atoms only implemented in
> PR1.1/PR1.2 but the package being marked as PR1.0 compatible
> by autobuilder -- because of course atom names are not symbols).
>
> Javier.
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>