Yes, for app development they are independent.
They didn't even have to live in the same repository, but since they are
usually used together we chose to have them in the same repo. That makes it
easier to catch bugs earlier and to make sure that Controls and Layouts always
cooperate properly.
Hi all.
I trying to build a GDB (with python suport) for the ARM target on Windows
host (with MinGW/MSYS),
but without of result. It is failed on libiconv v1.14 building (a wrong
-DINSTALLDIR escaping without quotes in libcharset sub-dir).
I use this WIKI:
Thanks for your clarification, guys.
Saether, I have noticed that almost everywhere in documentation these
modules are referred together, That is what was leading me to a
premature conclusion about dependency. So, it happens to be some kind
of semantic dependency, not binary/linker one.
Any
Hi all,
It has been a while since I followed Qt mailing list last time, but I
noticed that folks at Digia is working on an Android Material Design port
of QtQuick controls.
We've hacked a set of PoC Material components last month at MOPCON
http://mopcon.org/2014/ 2014; not sure if it helps, but
There is no need to change config files. Just type
make module-qtquickcontrols
from the meta repo. That should make QtQuick Controls + QtQuick Layouts + all
dependent libraries.
IMHO, QtQuick Layouts (+Controls) are available by default, and if you don't
need QtQuick Controls on your device,
On 10 Dec 2014, at 10:47, Dmitry Volosnykh dmitry.volosn...@gmail.com wrote:
Thanks for your clarification, guys.
Saether, I have noticed that almost everywhere in documentation these
modules are referred together, That is what was leading me to a
premature conclusion about dependency.
Hi everybody,
Qt 5.4 has just been released. For details check the blog post at
http://blog.qt.digia.com/blog/2014/12/10/qt-5-4-released/
In addition to Qt 5.4, we also released Qt Creator 3.3, see
http://blog.qt.digia.com/blog/2014/12/10/qt-creator-3-3-0-released/
And a new version of Qt for
Oops, now all builds without errors. Just need to use make.exe from MSYS,
instead of mingw32-make from MinGW. It is my stupid mistake.
2014-12-10 12:31 GMT+03:00 Denis Shienkov denis.shien...@gmail.com:
Hi all.
I trying to build a GDB (with python suport) for the ARM target on Windows
host
On Mon, 08 Dec 2014 08:58:57 +, Heikkinen Jani wrote:
We have Qt5.4.0 final packages available for your testing here:
Tried to build from the source tarballs on my OpenSuSE 13.1 box, but
after some while my make runs into pkg-config issues.
Well maybe my system is not properly set up for
Yeah, that's an unfortunate bug that slipped in. It is documented as a known
issue and tracked in QTBUG-43205
Simon
Original Message
From: Uwe Rathmann
Sent: Wednesday, December 10, 2014 12:14
To: development@qt-project.org
Subject: Re: [Development] Qt 5.4.0 final packages to be tested
On Wed, Dec 10, 2014 at 9:31 AM, Denis Shienkov
denis.shien...@gmail.com wrote:
Hi all.
I trying to build a GDB (with python suport) for the ARM target on Windows
host (with MinGW/MSYS),
but without of result. It is failed on libiconv v1.14 building (a wrong
-DINSTALLDIR escaping without
On Wed, 10 Dec 2014 11:20:17 +, Hausmann Simon wrote:
Yeah, that's an unfortunate bug that slipped in. It is documented as a
known issue and tracked in QTBUG-43205
According to http://qt-project.org/wiki/Qt540-KnownIssues I had the
impression, that installing dbus headers would fix the
On Wednesday 10. December 2014 12.05.26 Uwe Rathmann wrote:
On Wed, 10 Dec 2014 11:20:17 +, Hausmann Simon wrote:
Yeah, that's an unfortunate bug that slipped in. It is documented as a
known issue and tracked in QTBUG-43205
According to http://qt-project.org/wiki/Qt540-KnownIssues I
Hi all,
I'm trying to upgrade to Qt 5.4 and Qt Creator 3.3 using the online installer.
However, when I select Update components or Package manager, the
installer gets stuck at Preparing meta information download...
Looking at
Hallo Simon,
The easiest workaround is to get pkg-config to work for you.
well pkg-config is not broken, because I did something specific on my
box, it is the distro itself, that doesn't seem to provide a valid pkg-
config system. Maybe it is OpenSuSE 13.1 only, but it could also be an
issue
On Wed, 10 Dec 2014 13:47:33 +0100, Simon Hausmann wrote:
Oh, and the fourth option is to disable dbus with -no-dbus, but I don't
know if your setup allows for that :)
dbus is indeed not necessary for almost all of my use cases and I started
trying this option. Now it took me to:
make[5]:
On Wednesday 10. December 2014 14.22.52 Uwe Rathmann wrote:
On Wed, 10 Dec 2014 13:47:33 +0100, Simon Hausmann wrote:
Oh, and the fourth option is to disable dbus with -no-dbus, but I don't
know if your setup allows for that :)
dbus is indeed not necessary for almost all of my use cases
On Wednesday 10 December 2014 17:14:19 Simon Hausmann wrote:
On Wednesday 10. December 2014 13.26.57 Uwe Rathmann wrote:
The easiest workaround is to get pkg-config to work for you.
well pkg-config is not broken, because I did something specific on my
box, it is the distro itself, that
On Wed, 10 Dec 2014 17:13:31 +0100, Simon Hausmann wrote:
Yeah, configure should check for that and skip the kms plugin build if
it can't find it via pkg-config - that seems like a bug.
But everything what is needed is available on my system - it's only, that
the build doesn't find it.
With
On Wed, 10 Dec 2014 17:14:19 +0100, Simon Hausmann wrote:
( What raises the question, why configure comes to the conclusion to
enable pkg-config on my box ).
Even though you passed -no-pkg-config you mean?
No, without any option:
By default, configure determines whether to use pkg-config
On Wednesday 10 December 2014 12:05:26 Uwe Rathmann wrote:
On Wed, 10 Dec 2014 11:20:17 +, Hausmann Simon wrote:
Yeah, that's an unfortunate bug that slipped in. It is documented as a
known issue and tracked in QTBUG-43205
According to http://qt-project.org/wiki/Qt540-KnownIssues I
On Wednesday 10 December 2014 17:00:49 Uwe Rathmann wrote:
By default, configure determines whether to use pkg-config or not with
some heuristics ...
Yeah, I'm fixing that for 5.5. The logic is hard to understand, since the -pkg-
config option may not enable fully.
--
Thiago Macieira -
Dear Thiago and Ulf,
Thank you for your responses.
@Ulf
Ulf, thank you for pointing at related bug. It seems to me that you've
already fix the issue, haven't you? Is it correct that the solution is to
add 1 year to qml date object when the year is less than 0?
On Tue, Dec 9, 2014 at 11:25 AM,
Dear all
My well-intentioned changes to unbreak the building of the OS X builds for
5.4.0 have apparently had unexpected consequences. After reviewing the
situation, I've created https://codereview.qt-project.org/101843 to fix the
issues (note: updates for Windows pending). Once that one is in
On Wednesday 10 December 2014 17:42:06 Thiago Macieira wrote:
Explanation:
* runtime: dynamically open libdbus-1 at runtime
* linked: link to libdbus-1
* configure1: check at configure time if libdbus-1 is present in the
system and then enable runtime mode
* configure2: check at
On 11 Dec 2014, at 08:30, Thiago Macieira thiago.macie...@intel.com wrote:
On Wednesday 10 December 2014 17:42:06 Thiago Macieira wrote:
Explanation:
* runtime: dynamically open libdbus-1 at runtime
* linked: link to libdbus-1
* configure1: check at configure time if libdbus-1 is
26 matches
Mail list logo
