Doc: Use defines to hide info not related to Qt Quick projects

Change-Id: I70ee417aebcddd32ef9f6419e3000fdfd02c9707
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>

doc/src/qtquick/qtquick-profiler.qdoc

@@ -51,9 +51,11 @@
     Another typical cause for similar performance problems is creating,
     painting, or updating invisible items, which takes time in the GUI thread.
 
+    \if defined(qtcreator)
     Triggering long-running C++ functions, such as paint methods and signal
     handlers, also takes time in the GUI thread, but is more difficult to see in
     the QML Profiler, because it does not profile C++ code.
+    \endif
 
     To find excessive use of JavaScript, check the frame rate in animations and
     Scene Graph events, look for gaps, and check whether the application behaves
@@ -67,10 +69,12 @@
     are never visible to the users, because they are located outside the screen
     or hidden beneath other, visible elements.
 
+    \if defined(qtcreator)
     If frames get dropped even though JavaScript is not being run, and there are
     large, unexplained gaps in the timeline, check your custom QQuickItem
     implementations. You can use \l{Using Valgrind Code Analysis Tools}
     {Valgrind} or other general purpose profilers to analyze C++ code.
+    \endif
 
     \section1 Using QML Profiler
 
@@ -82,8 +86,10 @@
             for the project. For more information, see
             \l{Setting Up QML Debugging}.
 
+        \if defined(qtcreator)
         \li In the \uicontrol Projects mode, select a \l{glossary-buildandrun-kit}
             {kit} with Qt version 4.7.4 or later.
+       \endif
 
             \note To profile applications on \l{glossary-device}{devices}, you
             must install Qt 4.7.4 or later libraries on them.

doc/src/qtquick/qtquick-states.qdoc

@@ -143,7 +143,9 @@
             \endqml
         \endlist
 
+    \if defined(qtcreator)
     \include qtquick-states-scxml.qdocinc scxml state machines
+    \endif
 
     \section1 Animating Transitions Between States