Just passing this on. Respond to the bug report if you have information:
--- You are receiving this mail because: ---
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1049
--- Comment #36 from Zoltan Herczeg 2011-12-21 12:16:19 ---
Hi all,
we had a discussi
On 12/21/2011 10:43 AM, ext Dave Mateer wrote:
> I didn't intend my post to take a defensive tone. Again, I *really*
> appreciate the framework and all the people working on it; Qt is
> top-notch! It just seemed like there was some discussion on these
> things and thought it might be helpful to hav
On Wed, Dec 21, 2011 at 5:38 PM, Nils Jeisecke wrote:
> neither in source nor out of source builds currently work on Mac OS X.
>
> Does the CI build on Mac OS at all?
Yup. Take a poke around http://testresults.qt-project.org/ - for
instance:
http://testresults.qt-project.org/ci/QtBase_master_Int
Thanks, Marius, et al ...
I didn't intend my post to take a defensive tone. Again, I *really*
appreciate the framework and all the people working on it; Qt is
top-notch! It just seemed like there was some discussion on these
things and thought it might be helpful to have an outsider position.
Mayb
Hi,
neither in source nor out of source builds currently work on Mac OS X.
Does the CI build on Mac OS at all?
Nils
On Wed, Dec 21, 2011 at 4:02 PM, Stephen Kelly wrote:
> On Wednesday, December 21, 2011 15:18:19 Nils Jeisecke wrote:
>
>> Hi,
>
>>
>
>> I'm also trying to get qt compiled on Mac
On 21/12/2011 07:23, ext Dave Mateer wrote:
> I don't know that my opinion matters much, as I'm just new on the
> list. But I will confirm that the challenges below (and that others
> have mentioned recently on this group) are very much the situation I
> find myself in. I have about five patches I
On Wed, Dec 21, 2011 at 5:16 PM, wrote:
> Am i mistaken here? I was under the impression, that qMalloc / qFree /
> qRealloc
> exist to keep public headers free from the need to include some system
> headers.
See the discussion on http://codereview.qt-project.org/#change,11562.
Short answer: p
On Wednesday 21 December 2011 07:26:42 Robin Burchell wrote:
> Hi,
>
> I've submitted two changes last night:
> - http://codereview.qt-project.org/#change,11562 - deprecating
> qMalloc/qFree/qRealloc
> - http://codereview.qt-project.org/#change,11563 - removing all uses
> of them from QtBase
>
>
On Wednesday, 21 de December de 2011 17.01.13, Holger Hans Peter Freyther
wrote:
> On 12/21/2011 07:26 AM, Robin Burchell wrote:
> > Hi,
> >
> > ways to accomplish this as the commit message notes, and it's rather
> > unfair to impose an additional function call on all uses of these for
> > somethi
On 12/21/2011 07:26 AM, Robin Burchell wrote:
> Hi,
> ways to accomplish this as the commit message notes, and it's rather
> unfair to impose an additional function call on all uses of these for
> something which isn't used in the majority of cases.
Hi,
my two cents here. If code is calling out
hi Andreas,
On Wed, Dec 21, 2011 at 4:21 PM, Andreas Holzammer
wrote:
> Many of them have trouble with memory allocation, if you have one point where
> you can
> change the allocation it is easy to bypass these problems.
Though, as you noted, you don't actually have one place to do this.
You ne
Hi Robin,
Am 21.12.2011 07:26, schrieb Robin Burchell:
> Hi,
>
> I've submitted two changes last night:
> - http://codereview.qt-project.org/#change,11562 - deprecating
> qMalloc/qFree/qRealloc
> - http://codereview.qt-project.org/#change,11563 - removing all uses
> of them from QtBase
>
> My ju
On Wednesday, December 21, 2011 15:18:19 Nils Jeisecke wrote:
> Hi,
>
> I'm also trying to get qt compiled on Mac OS X 10.6.
>
> Thanks to the updated configure line (wiki) the mkv8snapshot problem
> now seems to be solved (for me).
> I'm at a01861593c98cf85b975833c0f71315cc62f49ae of qt5.git.
A
Hi,
I'm also trying to get qt compiled on Mac OS X 10.6.
Thanks to the updated configure line (wiki) the mkv8snapshot problem
now seems to be solved (for me).
I'm at a01861593c98cf85b975833c0f71315cc62f49ae of qt5.git.
However it now stops here:
projects/qt/qt5/qttools/src/linguist/lupdate/qdec
> -Original Message-
> From: development-bounces+kai.koehne=nokia@qt-project.org
> [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
> Behalf Of ext Dave Mateer
> Sent: Wednesday, December 21, 2011 2:30 PM
> To: development@qt-project.org
> Subject: Re: [Development] .
On 12/21/2011 02:23 PM, ext Dave Mateer wrote:
> I don't know that my opinion matters much, as I'm just new on the
> list. But I will confirm that the challenges below (and that others
> have mentioned recently on this group) are very much the situation I
> find myself in. I have about five patches
Thank you for this information. I had actually tried that but was
still having the problem. The "secret sauce" for me was to add the
-no-v8 option to my configuration. Then I got past that problem. (I'm
still dealing with others at this point, but I think we're slowly
making progress!)
On Wed, Dec
I don't know that my opinion matters much, as I'm just new on the
list. But I will confirm that the challenges below (and that others
have mentioned recently on this group) are very much the situation I
find myself in. I have about five patches I would like to submit for
bugs in JIRA, mostly priori
Qt 5 for NaCl is now roughly on par with the Qt 4 port and I would like to
start the process of integrating it with the goal of continuing development
upstream in Qt 5. I probably won't have time to any further work until next
year, but here's a heads up for those interested.
The Qt 5 patch is
On 12/21/2011 01:51 AM, ext craig.sc...@csiro.au wrote:
> On 21/12/2011, at 6:16 PM, Alan Alpert wrote:
>> Even if it's an easy change, do we even want those patches via
>> JIRA? For trivial patches I don't think the CLA applies anyways,
>> for non-trivial patches there needs to be discussion and
20 matches
Mail list logo
