Adapt to new project location.

Change-Id: I13de0363d36095faa2554c5b41cdb7fb3e7c42f2
Reviewed-by: hjk <qthjk@ovi.com>
This commit is contained in:
Eike Ziller
2011-10-24 14:46:55 +02:00
parent 7270633f86
commit cfb8417dec
+6 -7
View File
@@ -59,12 +59,11 @@
\section1 Submitting Code
To submit code to Qt, you must understand the tools and mechanics as well as
To submit code to Qt Creator, you must understand the tools and mechanics as well as
the philosophy behind Qt development. For more information about how to set up
the development environment for working on a Qt library and how to submit code
and documentation for inclusion to Qt, see
\l{http://developer.qt.nokia.com/wiki/Qt_Contribution_Guidelines}
{Guidelines for Contributions to the Qt Framework}.
the development environment for working on Qt Creator and how to submit code
and documentation for inclusion, see
\l{http://wiki.qt-project.org/index.php/Main_Page}{Guidelines for Contributions to the Qt Project}.
\section1 Binary and Source Compatibility
@@ -96,7 +95,7 @@
\o Do not reimplement methods (not even inlines,
nor protected or private methods).
\o Check
\l {http://developer.qt.nokia.com/wiki/Binary_Compatibility_Workarounds}{Binary Compatibility Workarounds}
\l {http://wiki.qt-project.org/index.php/Binary_Compatibility_Workarounds}{Binary Compatibility Workarounds}
for ways to preserve binary compatibility.
\endlist
@@ -497,7 +496,7 @@
\section2 Namespacing
Read \l {http://developer.qt.nokia.com/wiki/Qt_In_Namespace}{Qt In Namespace}
Read \l {http://wiki.qt-project.org/index.php/Qt_In_Namespace}{Qt In Namespace}
and keep in mind that all of Qt Creator is \e{namespace aware} code.
The namespacing policy within Qt Creator is as follows: