Hi
> 6. Rename the handle() to platformXXX() since it's easy to educate
> that anything that has platform in it is out of reach of app
> developers.
> Status: In progress, I am atm, marking handle() as obsolete and as an
> alias to platformXXX().
But since when did the word handle() mean anything
Hi,
Can the proponents of triaging expand on the concept of triaging and what
circumstances might lead someone to become a Triager (we have a group, project
role and permission level ready to apply to the concept)?
In recent weeks, there have been some changes to JIRA with an aim towards
loweri
On 05/25/2012 06:15 PM, ext Girish Ramakrishnan wrote:
> Hi,
> Here's the current status of the proposed plan of action for QPA api.
>
> 1. We drop _qpa completely. So, it would become qplatformbackingstore.h
> Status: Done
>
> 2. We teach syncqt that qplatform* is special and we move them all to
I thought I'd unravel the mystery man a bit.
My Qt history is quite fresh. I started off in late '09 in Brisbane office.
Back then the active focus was on qtmobility project. As a first task
I started working in the bearer management.
Once the biggest fires were off I scratched the initial Service
A workround: You can change qtbase\mkspecs\qconfig.pri after configure is
done.
From:
> CONFIG+= debug shared rtti sse2 qpa
To:
> CONFIG+= debug *build_all* shared rtti sse2 qpa
Then everything should build well. I am using this hack for a long time.
After the build done, you can change to bac
Loaden said:
> >
> > Generating Code...
> > link /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> > /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> > /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib" /NOLOGO /DYNAMICBASE
> > /NXCOMPAT /DEBUG /DLL /MANIFEST
> > /MANIFESTFILE:"deb
I'm as interested to see insightful review comments as a bulk of contribution.
Put another way, anyone can press the +1 button. The comments that go with a -1
inform how good a reviewer somebody is.
--
Subject to local law, communications with Accenture and its a
I can confirm the first issue (debug only plugins built) for source packages.
A workaround is to run "nmake release" in the source after building normally.
There seems to be an intended feature to build debug AND release for the Qt
DLLs, but debug OR release for executables. However it is uninten
First of all, I just want to say thanks for the quite unexpected
amount of replies to my mail. They will take a little time to absorb,
but I still feel I have relevant comments on some of the issues - once
the "heatwave" in Denmark has passed (apparently my brain fries at
temperatures above 22 C)
>
> Generating Code...
> link /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib"
> /LIBPATH:"d:\qpSOFT\Projects\BuildQt5-x64\qtbase\lib" /NOLOGO /DYNAMICBASE
> /NXCOMPAT /DEBUG /DLL /MANIFEST
> /MANIFESTFILE:"debug\declarative_locationd.in
:(
The erroe message:
> QtDBus: created headers.pri file
> No suitable compiler found in PATH. Aborting.
> *** qtbase/configure exited with non-zero status.
>
>
2012/5/28 Thiago Macieira
> On segunda-feira, 28 de maio de 2012 14.57.44, Loaden wrote:
> > Sorry, I make a big mistake, because I don
On segunda-feira, 28 de maio de 2012 14.57.44, Loaden wrote:
> Sorry, I make a big mistake, because I don't install .NET 4.0 first, Then
> Windows SDK 7.1 don't install the MSVC compiler, It's disabled becasue miss
> .NET 4.
> I will feedback after Re-install SDK 7.1.
> Sorry for the noise.
So the
12 matches
Mail list logo
