| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
it simply breaks too much (embedded builds in particular).
will come up with something better in master.
note however, that the .qm files do NOT return to the repository. the
release manager needs to run "make qm" before packaging, just like
Qt-from-git users who want translations do (i.e., almost nobody).
Reviewed-by: Jason McDonald
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
|
|
| |
so "qmake -r && make" worked fine ... but configure does not simply run
"qmake -r".
also, now we have to build lrelease even when we don't build the other
tools.
Reviewed-by: Jason McDonald
Reviewed-by: mariusSO
|
| |
|
|
| |
Reviewed-by: TrustMe
|
| |
|
|
|
|
|
|
| |
Instead of the multiple character-string replacements, just check for
the discrete -arch values that we want to find. This makes the code
clearer and should reduce the chance of subtle errors.
Reviewed-by: Jason McDonald
|
| |
|
|
| |
Reviewed-by:cduclos
|
| |
|
|
|
|
|
|
|
|
| |
The previous "fix" caused the effect of the line before the change to be
discarded, which breaks the mac binary package builds. When reviewing
changes, please read the lines of context given in the patch - they are
included for a reason.
Acked-by: Lincoln Ramsay
Acked-by: Rohan McGovern
|
| |
|
|
|
|
|
|
| |
The reason is the tha config.test ssl failed building. And the reason for
that was a bad makefile flag (i386_64).
Task-number: 253887
Reviewed-by: Trenton Schulz
|
| |
|
|
|
|
|
| |
STRING="${STRING/x86/i386}" actually replaces whole words only,
so we don't need to fixup x86_64 afterwards.
Reviewed-by: nrc
|
| |
|
|
|
|
|
|
|
| |
Store whether qt was built with qt3support enabled in .qmake.cache. We
need this info to decide if QT3_SUPPORT should be defined when we
include qimage_p.h. Otherwise we get data corruption issues since the
size of struct in Qt is larger than the one we include in libqdirectfb.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
|
|
|
|
|
|
| |
Reported downstream to Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525570
Reviewed-by: Alexis
Reviewed-by: Thiago
|
| |
|
|
|
|
|
|
|
|
|
| |
architechtures.
For example,
./configure -arch x86_64 -arch ppc requires D-Bus compiled for x86_64 and ppc
in order to enable it.
Task-number: 249881
Reviewed-by: nrc
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The nightly public snapshots contain bin/syncqt but do not
contain the include/ directory. Hence configure needs to
detect this case and run syncqt to create the include tree
so that configure actually passes
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| |
|
|
|
|
|
|
| |
The previous logic caused a license check when the eval
license file was missing.
Reviewed-by: Jason McDonald
Task-number: 251339
|
| |
|
|
|
|
|
|
| |
The eclipse integration is namespaced, but it still pulled in system plugins like the oxygen style through QT_BUILD_KEY_COMPAT check in QLibraryPrivate::isPlugin()
Task: 250185
Reviewed-by: dt <qtc-committer@nokia.com>
BT: yes
|
| |
|
|
|
|
|
| |
The previous version would get confused because the embedded package
also contains _x11 files.
Reviewed-by: Thiago
|
| |
|
|
|
|
| |
GCC uses i386, but configure has always used x86, which can lead to confusion.
Reviewed-by: nrc
|
| |
|
|
| |
Reviewed-by: TrustMe
|
| |
|
|
|
|
|
|
|
| |
Previously, it was entirely possible to successfully configure Qt/X11
without any X11 installed. The problems would only start showing up once
you stated building. This is not very useful if you're cross-compiling
and trying to setup the paths correctly.
Reviewed-by: Denis
|
| |
|
|
|
|
|
|
|
| |
The eclipse integration is namespaced, but it pulls in system plugins like the
oxygen style. This breaks as the (non-namespaced) style plugin does not find a
suitable QApplication instantiated (only a namespace one is there)
Reviewed-by: thiago
Task-number: 250185
|
| |
|
|
|
|
| |
Allow x86 x86_64 ppc ppc64, exit with an error message if something else is passed?
Reviewed-by: nrc
|
| |
|
