2012/3/19 Bradley Smith :
>> "What is the minimum version of XCB required for Qt 5?"
>>
>> It appears that libxcb-1.5 and xcb-proto-1.6 are required. These releases
>> were announced Dec 3 2009 and Dec 2 2009 respectively.
>>
>> Does anyone have a way to determine how wide spread libxcb >= 1.5 has
marius.storm-ol...@nokia.com said:
> While it's not normal to do this type of dependency "lock" for upwards
> dependencies, i think in this case we should indeed do the extra checking.
> Not just because QtDeclarative is such an important tech for Qt5, but also
> because it's a very good test ca
>
> "What is the minimum version of XCB required for Qt 5?"
>
> It appears that libxcb-1.5 and xcb-proto-1.6 are required. These releases
> were announced Dec 3 2009 and Dec 2 2009 respectively.
>
> Does anyone have a way to determine how wide spread libxcb >= 1.5 has
> become in the last 15 mon
"What is the minimum version of XCB required for Qt 5?"
It appears that libxcb-1.5 and xcb-proto-1.6 are required. These releases
were announced Dec 3 2009 and Dec 2 2009 respectively.
Does anyone have a way to determine how wide spread libxcb >= 1.5 has
become in the last 15 months?
_
On 03/18/2012 03:23 AM, Robin Burchell wrote:
> On Sun, Mar 18, 2012 at 7:59 AM, Rick Stockton
> wrote:
<< SNIP >>
>> I can't think of a WORSE spectacle, for the reputation of Qt-Project,
>> than the Release of an Alpha Build in which large numbers of exerpienced
>> Qt users on Linux Linux _might
>>
>>
>>
>>Every Linux distro uses X.org, which uses XCB.
>>
>>
>>
>> Including openSUSE 11.1, but just any XCB is not enough. It needs to be
>>more recent than some version. For users with an incompatible version of
>>XCB, I think we can provide a better user experience than hitting
>>compiler er
On domingo, 18 de março de 2012 20.10.51, lars.kn...@nokia.com wrote:
> Solving the problem of old distro's is not that hard. All that's required
> is to link xcb statically into the platform plugin. This is something that
> can be done, it can even be made rather simply in the Qt build system.
No
On 3/18/12 9:05 PM, "ext Thiago Macieira"
wrote:
>On domingo, 18 de março de 2012 19.55.53, lars.kn...@nokia.com wrote:
>> * No more source incompatible changes to features/API that are new in Qt
>> 5, unless approved by the module's maintainer after a discussion on the
>> mailing list
>
>Does th
On 3/18/12 6:28 PM, "ext Bradley Smith" wrote:
>
>
>
>Every Linux distro uses X.org, which uses XCB.
>
>
>
> Including openSUSE 11.1, but just any XCB is not enough. It needs to be
>more recent than some version. For users with an incompatible version of
>XCB, I think we can provide a better use
None of the below changes the fact that the xlib plugin is unmaintained
and broken. Removing it is the right thing to do for exactly that reason.
If things don't work with an older xcb release, let's add a configure test
requiring a minimum version that works. I rather have configure bail out
with
On domingo, 18 de março de 2012 19.55.53, lars.kn...@nokia.com wrote:
> * No more source incompatible changes to features/API that are new in Qt
> 5, unless approved by the module's maintainer after a discussion on the
> mailing list
Does this include source-incompatible changes that restore compa
Hi everybody,
there are quite a few people meeting up in Oslo this week, and we'll try
to finish up the Qt 5 alpha there. For this reason I'd like everybody to
restrain themselves in what they submit to the master branch. The main
focus needs to be to get the alpha, so please focus on staging only
>
> Every Linux distro uses X.org, which uses XCB.
>
Including openSUSE 11.1, but just any XCB is not enough. It needs to be
more recent than some version. For users with an incompatible version of
XCB, I think we can provide a better user experience than hitting compiler
errors when buildi
>
> opensuse 11.1 was released in 2008. that's a lot more than 18 months.
>
Yes, openSUSE 11.1 was released Dec. 18, 2008, but it was updated as
recently as Jan 13, 2011. This makes the last supported update only a
little over 14 months old.
Yes, it is an old system, but it's not ancient. :)
_
On domingo, 18 de março de 2012 11.23.51, Robin Burchell wrote:
> > I can't think of a WORSE spectacle, for the reputation of Qt-Project,
> > than the Release of an Alpha Build in which large numbers of exerpienced
> > Qt users on Linux Linux might be unable to use the XCB plugin and show
> > a mai
Hi all,
I'm facing a really annoying issue with MacOs X and my Qt application.
I was on MacOs 10.5 and every things were fine. I was able to create bundle
for my application.
I update my system to MacOs 10.6, and install the QtSDK, but now when I
create app_bundle, it is not working.
QtCreator sen
On Sunday 18 March 2012 11:43:02 craig.sc...@csiro.au wrote:
> That's fine when you are only building an application to run on your
> machine, but for people who want to distribute Qt5 apps, this would be an
> undesirable solution. You'd end up having to ship the xcb libraries as well
> as those l
While it's not normal to do this type of dependency "lock" for upwards
dependencies, i think in this case we should indeed do the extra checking. Not
just because QtDeclarative is such an important tech for Qt5, but also because
it's a very good test case for QtBase.
The extra time used for che
On Sun, Mar 18, 2012 at 7:59 AM, Rick Stockton
wrote:
> (3) Wondering if my Distro was "too old", (and most of it's RPMs were
> built in April of 2011), I just upgraded to Mageia-2 "beta-2". I no
> longer get SIGSEGV, but I get a problem which _could_ be closely
> related: referencing an Undefined
http://codereview.qt-project.org/#change,20091
My negative review of the Change comes out of 3 facts:
(1) I have personally experienced the yet-to-be-documented problem, with
both widget and declarative-based example programs, in which the GUI
never appears: The program crashes with SIGSEGV, pro
20 matches
Mail list logo
