> On 25 Feb 2015, at 7:20 am, Robin Burchell wrote:
>
> Hi,
>
> Since nobody else has replied to this yet, my understanding of what
> happened with license checks is roughly as follows. I was not
> involved, so YMMV - this is all just gained from observation of what's
> happened - someone else
On Wednesday 25 February 2015 00:44:49 Kevin Kofler wrote:
> Jeremy Whiting wrote:
> > One solution is to use/support XDG_*_DIRS environment variables on all
> > platforms. This has one advantage in that the same tools can be used on
> > all platforms to customize the paths given by the standard. T
Jeremy Whiting wrote:
> One solution is to use/support XDG_*_DIRS environment variables on all
> platforms. This has one advantage in that the same tools can be used on
> all platforms to customize the paths given by the standard. This is ok for
> developers working on software, but not the best id
Hi,
Since nobody else has replied to this yet, my understanding of what
happened with license checks is roughly as follows. I was not
involved, so YMMV - this is all just gained from observation of what's
happened - someone else please correct me if I'm wrong.
a) someone, somewhere, made a decisi
On Tuesday 24 February 2015 14:01:39 Adam Majer wrote:
> A signed tag automatically verifies the entire history as being
> authentic (up to the tag).
>
> - Adam
>
> PS. GPG signed releases would also be nice in addition to simple hash
> checksums. For example, one file with ALL hashes that is the
On Tue, Feb 24, 2015 at 12:54:48PM +, Hirvonen Olli wrote:
>Hi,
>
>We have installed a new read-only git mirror under qt.io domain
>(http://code.qt.io). The purpose of this git mirror is to act as a
>"authoritative" git mirror for Qt sources, and we plan to change links on
>
On Monday 23 February 2015 23:24:07 Jeremy Whiting wrote:
> A second solution is to add some API to QStandardPaths to modify the paths
> at run time. This would allow libraries to add paths to QStandardPaths'
> standard paths that it needs in its initialization methods. For example a
> library that
On Tuesday 24 February 2015 07:42:16 Gunnar Roth wrote:
> Hello,
> i am trying to build qt5.5 from git on windows . i do not want to make a
> deveolper build but want to build the code as i normally do. After creating
> the configure.exe, configureing and starting the build, qtcore build fails
> be
On Tuesday 24 February 2015 13:47:53 Sorvig Morten wrote:
> On OS X (and iOS): place the resources in he framework bundle for the
> component that owns them. Add public API to the component for accessing the
> resources.
Agreed. That means libraries that get installed as frameworks should simply
Hi,
the short and simple answer is no. The current version of the Qt Visual
Studio Add-In only supports Qt 5.x.
On 2/24/2015 15:42, Alessio Mochi wrote:
I would like know if exist an integration plugin for vs2013 that work
with qt 4.8.
Thanks.
__
I would like know if exist an integration plugin for vs2013 that work with qt
4.8.Thanks. ___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> On 24 Feb 2015, at 07:24, Jeremy Whiting wrote:
>
> Hello list,
>
> I discussed a bit with Thiago and some others on irc this evening and have
> realized that the QStandardPaths patch from [1] and discussion on [2] is
> trying to solve too many problems at once. I'll list the problems here
Hi,
We have installed a new read-only git mirror under qt.io domain
(http://code.qt.io). The purpose of this git mirror is to act as a
"authoritative" git mirror for Qt sources, and we plan to change links on our
own web pages to it where applicable. The new service does not have impact to
exi
> On Feb 20, 2015, at 10:04 AM, André Somers wrote:
>
> Bo Thorsen schreef op 20-2-2015 om 09:03:
>> Andrés question about how this would change the API is a lot more
>> interesting. I so far haven't seen a single case where someone has
>> described how access to lambdas might improve the API.
Thanks for answering Giuseppe, I appreciate it.
- Radjino
From: Giuseppe D'Angelo [dange...@gmail.com]
Sent: Tuesday, February 24, 2015 12:21 PM
To: Radjino Bholanath
Cc: development@qt-project.org
Subject: Re: [Development] Questions about code reviews and
Hi all,
We are happy to announce that Qt 5.4.1 & Qt Creator 3.3.1 is released today,
see http://blog.qt.io/blog/2015/02/24/qt-5-4-1-released/ &
http://blog.qt.io/blog/2015/02/24/qt-creator-3-3-1-released/
Big thanks to everyone who have helped to make the releases happen!
Br,
Jani
___
On 22 February 2015 at 18:02, Thiago Macieira
wrote:
> > No, there will be no more updates for < 1.0.1 after december. The
> lifespan
> > of 1.0.1 has not yet been set. They seem to be doing the work to make the
> > code more maintainable, then they'll probably have a longer lifespan.
>
> I meant
On 24 February 2015 at 11:53, Radjino Bholanath
wrote:
> 1. Do all developers (contributors and core developers) have to submit a code
> review for every change? I’m asking because many projects only review changes
> made by contributors.
The procedure is the same for everyone: all commits go t
Hi everyone,
I'm doing research on code reviews and static analysis tools at the SERG group
(http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of
Technology. Currently, we want to give an overview of the usage of code review
and static analysis tools in open source projects
Hi all!
Qt 5.5 branching is now complete. It means 'dev' branch is for Qt 5.6 release
and all changes targeted to Qt5.5 must be done in '5.5' branch. Ossi is still
taking re-targeting requests from 'dev' to '5.5' if some change currently in
'dev' should be in Qt 5.5.
Next milestone now is Qt
I now started all over, i can find qt-src\qtbase\include\QtCore now. But build fails with
cl -c -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -D_HAS_EXCEPTIONS=0 -MP -GR -GL -W3 -w34100 -w34189 -w44996 /Fd..\..\..\lib\Qt5BootstrapRTIL.pdb -DUNICODE
-DWIN32 -DQT_BOOTSTRAPPED -DQT_LITE_UNICODE -DQT
Yes, as i wrote "After creating the configure.exe, configuring [..]"
from the log:
Starting Qt configuring for win32-vs11-32
+ cd qtbase
+ C:\RTIL\Shared\Qt\5.5.0\qt-src\qtbase\configure.bat -top-level -prefix C:\RTIL\SharedBin\Qt\5.5.0\WIN32-VS11-32 -platform win32-msvc2012 -debug-and-rele
Hi,
there is https://bugreports.qt.io/browse/QTBUG-44434 describing the
issue, but there does not seem to be a conclusion yet. It is unlikely
that the issue is fixed by the merge or goes away magically; it would be
appreciated if the accessibilty experts could take a look.
Regards,
Friedemann
How did you configure it? Did you run configure.bat?
Regards,
Konstantin
2015-02-24 10:42 GMT+04:00 Gunnar Roth :
> Hello,
> i am trying to build qt5.5 from git on windows . i do not want to make a
> deveolper build but want to build the code as i normally do.
> After creating the configure.exe,
On Tuesday 24 February 2015 07:43:47 Heikkinen Jani wrote:
> Hi all,
>
> If I have understood correctly merge from 'dev' to '5.5' should solve this
> issue. Or does someone disagree?
It could be that a commit which somehow integrated to 5.5 is causing the
failure.
There is only a few commit in 5
25 matches
Mail list logo