| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gui/styles/qcommonstyle.cpp
tools/assistant/lib/lib.pro
tools/assistant/lib/qhelp_global.cpp
tools/assistant/tools/assistant/assistant.qch
tools/assistant/tools/assistant/mainwindow.cpp
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-5148
Reviewed-by: Tom Cooksey
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moved duplicated and broken code for setting up the include and library
paths into the egl.prf feature file, which egl.pri and opengl.pro now
includes using the qmake feature system.
Task-number: QTBUG-5148
Reviewed-by: Tom Cooksey
|
| |
| |
| |
| | |
Does nothing if no declarative directories installed.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
introduce QMAKE_LIBS_OPENGL_ES1, QMAKE_LIBS_OPENGL_ES1CL and
QMAKE_LIBS_OPENGL_ES2 so we do not have to force users to copy/paste
around entire mkspecs just to change the OpenGL backend.
This should make the "-opengl es2" (and friends) configure option
work out of the box with any mkspec on Linux+WinCE.
Also removes a WinCE specific hack that is not required anymore.
Reviewed-by: Tom Cooksey
Reviewed-by: Trond Kjernåsen
Approved-by: Lars Knoll
|
| |
| |
| |
| |
| |
| | |
This is the same workaround as Janne did for QtWebkit.
Reviewed-by: Janne Koskinen
|
|\ \
| |/ |
|
| |
| |
| |
| | |
RevBy: mread
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
translations/assistant_adp_pl.ts
translations/assistant_adp_ru.ts
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using just -lQtUiTools instead of -lQtUiTools.lib will make qmake
attempt to autodetect whether or not the lib is static or dynamic,
which will not work since QtUiTools is not necessarily yet built.
Task-number: QT-1018
Reviewed-by: Janne Koskinen
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is required by the Helix plugin. As discussed with Dallas team/Fu Liz.
Reviewed-by: Shane Kearns
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Fix for applications not compiling containing #include<QtWebkit>
due to relative inclusion problem in Symbian build environment.
Task-number: QTBUG-4846
Reviewed-by: Iain
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tools/assistant/translations/translations_adp.pro
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The VCPROJ/SLN generator generates dependencies on the glue project,
so the glue must use the correct library for the dependencies to be
correct. The qtAddLibrary() would add the project 'default' to the
glue, which could end up adding a debug lib to the glue, so the
dependency checker wouldn't find the proper project.
We therefore force qtAddLibrary to only add d/_debug if we're not
using debug_and_release, or not in the glue part
Reviewed-by: Rohan McGovern
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/corelib/io/qdatastream.h
tools/assistant/translations/translations_adp.pro
tools/qdoc3/test/qt-build-docs.qdocconf
tools/qdoc3/test/qt-inc.qdocconf
tools/qdoc3/test/qt.qdocconf
translations/assistant_adp_de.ts
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It was decided on weekly telco that Symbian pkg and sis files can use
plain Qt name, since it is already clear that user is installing
"Qt for Symbian" version of Qt.
Task-number: QT-772
Reviewed-by: Miikka Heikkinen
|
|\ \
| |/
| |
| |
| | |
Conflicts:
src/corelib/io/qdatastream.h
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Phonon.
Both epoc32/include and $QTDIR/include/Phonon contain a file called videoplayer.h. Both of these directories are listed as SYSTEMINCLUDE paths in the generated MMP file, with the Phonon path coming first. This means that '#include <videoplayer.h>' picks up the Phonon header rather than (as intended) the Symbian one.
A new qmake variable, PREPEND_INCLUDEPATH, is defined, allowing the .pro file to specify that /epoc32/include should be the first SYSTEMINCLUDE.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Skipped addExclusiveBuilds function in debug_and_release.prf for all
Symbian platforms, as it doesn't work with Symbian toolchain.
Reviewed-by: Janne Anttila
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
Conflicts:
doc/src/qt4-intro.qdoc
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Prepending adds epoc32\include too early into generated
systeminclude path search order causing Webcore build
to break due to wrong animation.h header getting included.
Reviewed-by: Jason Barron
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new public classes in the 's60framework' sub-directory of QtGui
introduce a header file dependency to the middleware layer of the SDK
by including 'aknapp.h'.
Since the build system doesn't know if you have included QtGui or not,
the closest approximation is to append the middleware layer include
path in cases where the QT variable contains 'gui'
Reviewed-by: axis
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some changes was done on Mac to support Qt building statically
on Cocoa. Unfortunatly, the change lead to many visibility warnings
because, with the change, src/tools/bootstrap was made with symbols
hidden by default (-fvisibility=hidden). Then, when building the
tools (moc, rcc etc), visibility was public by default (for internal
classes used by Qt). This caused warnings. The change is now temporarily
reverted until Morten get a second chance to look at it.
Rev-By: prasanth
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This introduces an undocumented "phonon_compat" subdir and also adds
it to the INCLUDEPATH when QT += phonon is specified. With this, these
styles of #includes should be supported:
#include <Phonon>
#include <Phonon/Phonon>
#include <phonon>
#include <phonon/phonon>
#include <Phonon/MediaObject>
#include <phonon/mediaobject.h>
Still need to check if the headers get installed during "make
install". I couldn't find where in our code that is done.
BT: yes
Reviewed-By: Trust Me
|
| | |
| | |
| | |
| | | |
Reviewed-By: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Several script and webkit tests require increased maximum heap
in emulator, so just increase the maximum heap for all autotests.
Reviewed-by: Janne Koskinen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is fixed better in 4.6. Don't make merging harder than it has
to be.
This reverts commit 8a441f3cf8a2cbc92861b7c55dd4664da4e8130b.
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
Conflicts:
src/3rdparty/webkit/WebKit/qt/Api/qwebframe.cpp
src/gui/kernel/qwidget_x11.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a workaround for the fact that removing --export_all_vtbl from
the RVCT command line seems to cause problems when linking the static
s60main lib with apps built with GCCE (at least 4.3, haven't tested
earlier versions)
The root cause still needs to be found and fixed, after which this
workaround can hopefully be removed.
Problem observed on Symbian^3 release, RVCT 2.2 build 686,
GCC-E 2009q1-162 release from CodeSourcery.
Reviewed-by: axis
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
SBSv1 has also been updated to define the appropriate macros and add the
required library statements, so all that is needed is the STDCPP keyword
Reviewed-by: mread
|
|\ \ \
| |/ / |
|
| |/
| |
| |
| |
| | |
Add -all_load to make Objective-C categories work.
Enable hide_symbols to remove visibility issues.
|
|\ \
| |/ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This way we avoid having a lot of code in a static (and
unmaintainable) library. The s60main static library now currently has
only one task: to call main().
To move the initialization into QtGui also meant a change in how the
S60 framework is created, because we can no longer use the trick
where we create and start the the S60 event loop and then have the
framework call us back to start main(). The initialization now
follows the creation and destruction of QApplication, which is a lot
more in line with how other platforms do it.
Since S60 doesn't support creating the environment, and *then*
starting it (both are executed by the same call), we had to open up
the S60 framework construction classes and just mirror what they do.
This means that after QApplication construction is done, the S60
framework is initialized, but nothing will run yet and control will
return to main(), where the user can start the event loop himself.
One of the quirks of this approach is that the construction of the
S60 framework makes a new cleanup stack. This means that any active
traps will not be active anymore, and leaving without setting a new
trap will most likely panic. This shouldn't be a problem for us,
since Qt is never supposed to leave, but it means that if anyone uses
the cleanup stack without setting a new trap, they will receive a
panic.
It was considered to add a trap mark in QApplication construction and
then removing it on destruction, but it was dropped because leaving
from main() is still undefined (even if the old cleanup stack would
be restored in the destructor, we wouldn't be able to stop the
exception from unwinding the stack, and the cleanup stack would then
be unbalanced).
RevBy: Jason Barron
RevBy: Janne Anttila
AutoTest: QWidget passed with same failure count
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/plugins/qpluginbase.pri
tests/benchmarks/qgraphicsanchorlayout/tst_qgraphicsanchorlayout.cpp
tools/assistant/compat/mainwindow.cpp
tools/assistant/compat/mainwindow.ui
tools/assistant/tools/assistant/doc/assistant.qdocconf
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
The Symbian build system can't handle directories starting with a `.',
so qmake aborts if MOC_DIR and similar start with a `.'. However,
the check for this condition was faulty and would include any path
which contained a `.' anywhere.
Reviewed-by: Michael Goddard
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
This introduces a QAbstractVideoSurface interface for implementing arbitrary
video outputs, and a QVideoFrame type. Also included is the
QVideoSurfaceFormat class which is used to configure the input to a video
surface, and the QAbstractVideoBuffer class which allows QVideoFrames
to be constructed from non-native frame types.
Reviewed-by: Dmytro Poplavskiy
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Miikka Heikkinen
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.exe
examples/examples.pro
qmake/Makefile.unix
qmake/Makefile.win32
qmake/Makefile.win32-g++
qmake/Makefile.win32-g++-sh
qmake/qmake.pro
src/script/api/qscriptable.h
src/script/api/qscriptclasspropertyiterator.h
src/script/api/qscriptcontext.h
src/script/api/qscriptengineagent.cpp
src/script/api/qscriptstring.cpp
src/script/api/qscriptstring.h
src/script/api/qscriptvalueiterator.cpp
src/script/api/qscriptvalueiterator.h
src/script/qscriptclass.cpp
src/script/qscriptcontext.cpp
src/script/qscriptengine.cpp
src/script/qscriptengine_p.cpp
src/script/qscriptvalue.cpp
src/script/qscriptvalue_p.h
src/script/qscriptvalueimplfwd_p.h
src/script/script.pro
src/src.pro
tests/auto/auto.pro
tests/auto/qscriptv8testsuite/tst_qscriptv8testsuite.cpp
tools/configure/configureapp.cpp
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Reviewed-by: TrustMe
|