<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Qt Creator on yozy//NET</title>
    <link>https://yozy.net/tags/qt-creator/</link>
    <description>Recent content in Qt Creator on yozy//NET</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jan 2018 11:57:28 +0100</lastBuildDate>
    <atom:link href="https://yozy.net/tags/qt-creator/feed.xml" rel="self" type="application/rss" />
    <item>
      <title>Qt Creator Hidden Gems</title>
      <link>https://yozy.net/2018/01/qt-creator-hidden-gems/</link>
      <pubDate>Tue, 02 Jan 2018 11:57:28 +0100</pubDate>
      <guid>https://yozy.net/2018/01/qt-creator-hidden-gems/</guid>
      <description>&lt;p&gt;When it comes to C++ IDEs I always reach for Qt Creator. I love its streamlined user interface which nevertheless exposes all screws and knobs if necessary.&lt;/p&gt;&#xA;&lt;p&gt;But mostly I like how it manages to surprise me with every update.&lt;/p&gt;&#xA;&lt;p&gt;Most recently I have updated to version 4.5.1 (from the 4.5 RC) and as I am hacking on the keyboard I see this:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/2018-01-02/qt-creator-output-param@2x.png&#34; alt=&#34;QtCreator detects output parameters&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Finally a work around the terrible decision to not explicitly mark function parameters used as a reference in C++.&lt;/p&gt;&#xA;&lt;p&gt;What&amp;rsquo;s more, Qt Creator does support &amp;ldquo;relative&amp;rdquo; text style for this highlight. One &lt;code&gt;saturation +0.30&lt;/code&gt; later I have:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/2018-01-02/qt-creator-output-param-hilight@2x.png&#34; alt=&#34;QtCreator can change text style relatively&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Can&amp;rsquo;t wait for what the 4.6 will bring!&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>Use QtCreator to develop OpenViBE in 2017 on Linux</title>
      <link>https://yozy.net/2017/11/use-qtcreator-to-develop-openvibe-in-2017-on-linux/</link>
      <pubDate>Sun, 19 Nov 2017 20:00:00 +0000</pubDate>
      <guid>https://yozy.net/2017/11/use-qtcreator-to-develop-openvibe-in-2017-on-linux/</guid>
      <description>&lt;p&gt;Note: This tutorial does not use the &lt;em&gt;meta&lt;/em&gt; repository. It uses the latest OpenViBE 2.0.0 repositories with the multi-repository build. It is based on QtCreator 4.4.1 (the currently latest stable release). It will work on the 4.5 version, however this one seems to not currently work very well on Linux.&lt;/p&gt;&#xA;&lt;p&gt;It is possible to simplify this installation a LOT if you only wish to build the OpenViBE component and wish to use the default SDK (Kernel, Modules, base plugins..) and Designer. In that case only take the part concerning the &lt;em&gt;extras&lt;/em&gt; repo and do not specify custom &lt;strong&gt;OPENVIBE_SDK_PATH&lt;/strong&gt; and &lt;strong&gt;DESIGNER_SDK_PATH&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This tutorial also does not use the build scripts!&lt;/p&gt;&#xA;&lt;p&gt;This post assumes that your final configuration will look like this:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;openvibe&lt;/strong&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;sdk&lt;/strong&gt; &lt;em&gt;git repository for OpenViBE SDK&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;designer&lt;/strong&gt; &lt;em&gt;git repository for OpenViBE Designer&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;extras&lt;/strong&gt; &lt;em&gt;git repository for OpenViBE Extras&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;test&lt;/strong&gt; &lt;em&gt;git repository for integration tests&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;build&lt;/strong&gt; &lt;em&gt;contains all of the build folders populated by CMake&lt;/em&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;sdk-debug&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;sdk-release&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;designer-debug&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;designer-release&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;extras-debug&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;extras-release&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;dist&lt;/strong&gt; &lt;em&gt;contains all of the folders created during CMake INSTALL phase&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;sdk-debug&lt;/strong&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;sdk-release&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;designer-debug&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;designer-release&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;openvibe-debug&lt;/strong&gt; &lt;em&gt;this tis the final destination of the complete Debug build&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;openvibe-release&lt;/strong&gt; &lt;em&gt;and the release build&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;In my examples I am putting all of these files under &lt;code&gt;/opt&lt;/code&gt;, if you want them somewhere else you should change all instances of &lt;code&gt;/opt&lt;/code&gt; in this tutorial to something else.&lt;/p&gt;&#xA;&lt;h1 id=&#34;clone-the-repositories&#34;&gt;Clone the repositories&lt;/h1&gt;&#xA;&lt;p&gt;Get to the folder where you want to have your &lt;strong&gt;openvibe&lt;/strong&gt; root folder and do:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;cd&lt;/span&gt; /opt&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;mkdir openvibe&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;cd&lt;/span&gt; openvibe&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;mkdir build&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;cd&lt;/span&gt; build&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;mkdir sdk-debug sdk-release designer-debug designer-release openvibe-debug openvibe-release&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;cd&lt;/span&gt; ..&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;mkdir dist&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git clone git@gitlab.inria.fr:openvibe/sdk.git sdk&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git clone git@gitlab.inria.fr:openvibe/designer.git designer&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git clone git@gitlab.inria.fr:openvibe/extras.git extras&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git clone git@gitlab.inria.fr:openvibe/test.git &lt;span class=&#34;nb&#34;&gt;test&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h1 id=&#34;install-dependencies&#34;&gt;Install dependencies&lt;/h1&gt;&#xA;&lt;p&gt;Some dependencies are needed, this will install all linux native packages + some extras such as test.&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;c1&#34;&gt;# if you want test data you will need the values for these variables&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;export&lt;/span&gt; &lt;span class=&#34;nv&#34;&gt;PROXYPASS&lt;/span&gt;&lt;span class=&#34;o&#34;&gt;=&lt;/span&gt;&lt;span class=&#34;s2&#34;&gt;&amp;#34;&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;export&lt;/span&gt; &lt;span class=&#34;nv&#34;&gt;DEPENDENCY_SERVER&lt;/span&gt;&lt;span class=&#34;o&#34;&gt;=&lt;/span&gt;&lt;span class=&#34;s2&#34;&gt;&amp;#34;&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;perl sdk/scripts/linux-install_dependencies.pl --manifest-dir sdk/scripts/ --dependencies-dir dependencies&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;perl sdk/scripts/linux-install_dependencies.pl --manifest-dir designer/scripts/ --dependencies-dir dependencies&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;perl sdk/scripts/linux-install_dependencies.pl --manifest-dir extras/scripts/ --dependencies-dir dependencies&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nb&#34;&gt;cd&lt;/span&gt; /opt/openvibe/sdk&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;./unix-get-dependencies.sh --manifest tests-data.txt --out /opt/openvibe/dependencies --cache /opt/openvibe/dependencies/arch&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h1 id=&#34;configure-the-qtcreator&#34;&gt;Configure the QtCreator&lt;/h1&gt;&#xA;&lt;p&gt;This step will have to be reproduced for all of the other repositories with minor changes.&lt;/p&gt;&#xA;&lt;p&gt;It is important to know how CMake actually works, a quick summary:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;CMake creates a &lt;em&gt;build&lt;/em&gt; folder during configuration step. This folder contains all of the configuration files (CMakeCache.txt is the most important), ninja file (this tells the compiler in what order it should build the project) and the built binary files.&lt;/li&gt;&#xA;&lt;li&gt;When you configure the project all of the variables you specify at configure are saved in the &lt;em&gt;build&lt;/em&gt; folder.&lt;/li&gt;&#xA;&lt;li&gt;When you build the project, the binary files are kept in the &lt;em&gt;build&lt;/em&gt; folder.&lt;/li&gt;&#xA;&lt;li&gt;When you INSTALL the project, only the files that are necessary for the final application are copied into the &lt;em&gt;dist&lt;/em&gt; folder (specified by &lt;strong&gt;CMAKE_INSTALL_PREFIX&lt;/strong&gt;. On Linux, the default &lt;em&gt;dist&lt;/em&gt; folder is &lt;code&gt;/usr/local&lt;/code&gt; and on Windows it is &lt;code&gt;C:\Program Files (x86)\PROJECT_NAME&lt;/code&gt;. We &lt;strong&gt;do not&lt;/strong&gt; want to use the default folders!&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;session-configuration&#34;&gt;Session configuration&lt;/h2&gt;&#xA;&lt;p&gt;Launch QtCreator, create a new session&lt;/p&gt;&#xA;&lt;h2 id=&#34;sdk-configuration&#34;&gt;SDK configuration&lt;/h2&gt;&#xA;&lt;p&gt;Go to &lt;strong&gt;Welcome -&amp;gt; Open Project&lt;/strong&gt; and navigate to the &lt;code&gt;openvibe/sdk/CMakeLists.txt&lt;/code&gt; file, a dialog like this will open:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/sdk-configure-project.png&#34; alt=&#34;sdk-configure-project&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Note that I have already changed all paths to what they should be.&lt;/p&gt;&#xA;&lt;p&gt;Click on the &lt;strong&gt;Configure Project&lt;/strong&gt; button.&lt;/p&gt;&#xA;&lt;h3 id=&#34;cmake-variables&#34;&gt;CMake variables&lt;/h3&gt;&#xA;&lt;p&gt;You will see a lot of errors printed in the General Messages tab on the bottom. Go to the &lt;strong&gt;Projects&lt;/strong&gt; pane on the right and select &lt;strong&gt;build&lt;/strong&gt; under GCC.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/build-configuration-button.png&#34; alt=&#34;build-config-button&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Check that the &lt;strong&gt;Edit build configuration&lt;/strong&gt; dropdown is set to &lt;strong&gt;Debug&lt;/strong&gt; on the top of this window.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/sdk-build-type-debug.png&#34; alt=&#34;sdk-build-type-debug&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Now you will need to (sadly, blindly) add a few variables to the lot. This is because the configuration by default is not what we want.&lt;/p&gt;&#xA;&lt;p&gt;Add these variables:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;CMAKE_INSTALL_PREFIX&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/sdk-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;OV_CUSTOM_DEPENDENCIES_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dependencies&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;BUILD_UNIT_TEST&lt;/strong&gt; &lt;code&gt;Boolean&lt;/code&gt; &lt;code&gt;ON&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;BUILD_VALIDATION_TEST&lt;/strong&gt; &lt;code&gt;Boolean&lt;/code&gt; &lt;code&gt;ON&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The test variables are not strictly necessary and you can turn them OFF if you want.&lt;/p&gt;&#xA;&lt;p&gt;Click on &lt;strong&gt;Apply Configuration&lt;/strong&gt;. Note that Qt Creator does not save this configuration if you do not use Apply!&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/sdk-build-configuration.png&#34; alt=&#34;sdk-build-config&#34;&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;install-and-clean&#34;&gt;Install and clean&lt;/h3&gt;&#xA;&lt;p&gt;In order to actually run the INSTALL step after each build (this is not how normal projects work but here it is necessary).&lt;/p&gt;&#xA;&lt;p&gt;In the &lt;strong&gt;Build Steps&lt;/strong&gt; and &lt;strong&gt;Clean Steps&lt;/strong&gt; choose the &lt;em&gt;install&lt;/em&gt; and &lt;em&gt;clean&lt;/em&gt; option respectively.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/sdk-build-steps.png&#34; alt=&#34;sdk-build-steps&#34;&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;run-environment&#34;&gt;Run environment&lt;/h3&gt;&#xA;&lt;p&gt;OpenViBE requires some variables on runtime to work. Also, as we are not installing into a default prefix we need to tell Linux where to find the libraries.&lt;/p&gt;&#xA;&lt;p&gt;In the &lt;strong&gt;Build Environment&lt;/strong&gt; click on &lt;strong&gt;Batch Edit&amp;hellip;&lt;/strong&gt; and insert the following string:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;LD_LIBRARY_PATH=/opt/openvibe/dist/sdk-debug/lib&#xA;OV_PATH_ROOT=/opt/openvibe/dist/sdk-debug&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;You are now ready to build &lt;em&gt;OpenViBE SDK&lt;/em&gt; in &lt;em&gt;Debug&lt;/em&gt; mode. Give it a spin, either right click on the OpenVIBE project in the &lt;strong&gt;Edit&lt;/strong&gt; view or use the hammer button on the bottom left.&lt;/p&gt;&#xA;&lt;h3 id=&#34;release-configuration&#34;&gt;Release configuration&lt;/h3&gt;&#xA;&lt;p&gt;Redo the same thing for &lt;strong&gt;Release&lt;/strong&gt; configuration on the top.&lt;/p&gt;&#xA;&lt;p&gt;In this case you will need to change the &lt;strong&gt;CMAKE_INSTALL_PREFIX&lt;/strong&gt; to &lt;code&gt;/opt/openvibe/dist/sdk-release/&lt;/code&gt;. And choose the appropriate environment variables like so:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;LD_LIBRARY_PATH=/opt/openvibe/dist/sdk-release/lib&#xA;OV_PATH_ROOT=/opt/openvibe/dist/sdk-release&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;h2 id=&#34;designer-configuration&#34;&gt;Designer configuration&lt;/h2&gt;&#xA;&lt;p&gt;This step is very similar to the SDK. First open the project from the Welcome screen.&lt;/p&gt;&#xA;&lt;p&gt;On the &lt;em&gt;configure project&lt;/em&gt; page select:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Debug &lt;em&gt;build folder&lt;/em&gt; is &lt;code&gt;/opt/openvibe/build/designer-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Release &lt;em&gt;build folder&lt;/em&gt; is &lt;code&gt;/opt/openvibe/build/designer-release&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Do not forget to disable all other build types.&lt;/p&gt;&#xA;&lt;h3 id=&#34;cmake-variables-1&#34;&gt;CMake variables&lt;/h3&gt;&#xA;&lt;p&gt;You will need some additional CMake variable specified:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;OPENVIBE_SDK_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/sdk-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;LIST_DEPENDENCIES_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dependencies&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;CMAKE_INSTALL_PREFIX&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/designer-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This tells the designer to find the SDK built in the previous step. Otherwise the designer will use SDK from its dependencies.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/designer-build-configuration.png&#34; alt=&#34;designer-build-config&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Click on &lt;strong&gt;Apply Configuration&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h3 id=&#34;install--clean&#34;&gt;Install &amp;amp; Clean&lt;/h3&gt;&#xA;&lt;p&gt;Check the &lt;code&gt;install&lt;/code&gt; and &lt;code&gt;clean&lt;/code&gt; options in Clean and Build steps like in SDK.&lt;/p&gt;&#xA;&lt;h3 id=&#34;run-environment-1&#34;&gt;Run environment&lt;/h3&gt;&#xA;&lt;p&gt;We also want to be able to run a &amp;ldquo;pure&amp;rdquo; designer installation from Qt Creator.&lt;/p&gt;&#xA;&lt;p&gt;In the &lt;strong&gt;Build Environment&lt;/strong&gt; click on &lt;strong&gt;Batch Edit&amp;hellip;&lt;/strong&gt; and insert the following string:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;LD_LIBRARY_PATH=/opt/openvibe/dist/designer-debug/lib&#xA;OV_PATH_ROOT=/opt/openvibe/dist/designer-debug&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;You are now ready to build &lt;em&gt;OpenViBE Designer&lt;/em&gt; in &lt;em&gt;Debug&lt;/em&gt; mode. Give it a spin, either right click on the OpenVIBE project in the &lt;strong&gt;Edit&lt;/strong&gt; view or use the hammer button on the bottom left.&lt;/p&gt;&#xA;&lt;h2 id=&#34;extras-configuration&#34;&gt;Extras configuration&lt;/h2&gt;&#xA;&lt;p&gt;Once again (and for the last time).&lt;/p&gt;&#xA;&lt;p&gt;On the &lt;em&gt;configure project&lt;/em&gt; page select:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Debug &lt;em&gt;build folder&lt;/em&gt; is &lt;code&gt;/opt/openvibe/build/openvibe-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Release &lt;em&gt;build folder&lt;/em&gt; is &lt;code&gt;/opt/openvibe/build/opevibe-release&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Do not forget to disable all other build types.&lt;/p&gt;&#xA;&lt;h3 id=&#34;cmake-variables-2&#34;&gt;CMake variables&lt;/h3&gt;&#xA;&lt;p&gt;You will need some additional CMake variable specified:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;OPENVIBE_SDK_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/sdk-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;DESIGNER_SDK_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/designer-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;LIST_DEPENDENCIES_PATH&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dependencies&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;CMAKE_INSTALL_PREFIX&lt;/strong&gt; &lt;code&gt;String&lt;/code&gt; &lt;code&gt;/opt/openvibe/dist/openvibe-debug&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This tells the designer to find the SDK built in the previous step. Otherwise the designer will use SDK from its dependencies.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/extras-build-configuration.png&#34; alt=&#34;extras-build-config&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Click on &lt;strong&gt;Apply Configuration&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h3 id=&#34;install--clean-1&#34;&gt;Install &amp;amp; Clean&lt;/h3&gt;&#xA;&lt;p&gt;Check the &lt;code&gt;install&lt;/code&gt; and &lt;code&gt;clean&lt;/code&gt; options in Clean and Build steps like in SDK.&lt;/p&gt;&#xA;&lt;h3 id=&#34;run-environment-2&#34;&gt;Run environment&lt;/h3&gt;&#xA;&lt;p&gt;Finally, we want to be able to run the complete installation.&lt;/p&gt;&#xA;&lt;p&gt;In the &lt;strong&gt;Build Environment&lt;/strong&gt; click on &lt;strong&gt;Batch Edit&amp;hellip;&lt;/strong&gt; and insert the following string:&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;LD_LIBRARY_PATH=/opt/openvibe/dist/openvibe-debug/lib&#xA;OV_PATH_ROOT=/opt/openvibe/dist/openvibe-debug&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;You are now ready to build the &lt;em&gt;Full OpenViBE Designer&lt;/em&gt; in &lt;em&gt;Debug&lt;/em&gt; mode. Give it a spin, either right click on the OpenVIBE project in the &lt;strong&gt;Edit&lt;/strong&gt; view or use the hammer button on the bottom left.&lt;/p&gt;&#xA;&lt;p&gt;You should now see all of the various OpenViBE projects in the build menu.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/projects.png&#34; alt=&#34;projects&#34;&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;running-the-openvibe-designer-with-the-full-feature-set&#34;&gt;Running the OpenViBE Designer with the full feature set&lt;/h3&gt;&#xA;&lt;p&gt;The Designer project is built in a separate project from extras. If you want to run the designer (or debug it) with all of the plugins, you need to create a new run configuration.&lt;/p&gt;&#xA;&lt;p&gt;Go to &lt;strong&gt;Projects -&amp;gt; OpenViBE -&amp;gt; Run&lt;/strong&gt; in the left pane. Be careful to choose the OpenViBE Project which corresponds to extras!&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/run-configuration-button.png&#34; alt=&#34;run-config-button&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Click on &lt;strong&gt;Add -&amp;gt; Custom Executable&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/run-configuration-add-button.png&#34; alt=&#34;run-config-add-button&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Now select the &lt;code&gt;/opt/openvibe/dist/openvibe-debug/bin/openvibe-designer&lt;/code&gt; as &lt;em&gt;Executable&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Rename this configuration as &lt;em&gt;Debug Designer&lt;/em&gt;. You can now choose it from the projects menu and run it using the play button (or debug it using the play button with a little bug on it)&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/openvibe-qtcreator/debug-designer.png&#34; alt=&#34;debug-designer&#34;&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>A nice dark color theme for QtCreator</title>
      <link>https://yozy.net/2011/05/a-nice-dark-color-theme-for-qtcreator/</link>
      <pubDate>Thu, 26 May 2011 19:18:46 +0000</pubDate>
      <guid>https://yozy.net/2011/05/a-nice-dark-color-theme-for-qtcreator/</guid>
      <description>&lt;p&gt;&lt;em&gt;Last update: 2013-06-29 for Qt Creator 2.7.1&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Staring at long lines of code can get frustrating. Even more so if the said&#xA;lines have ugly eye-hurting colors. I have been using the beautiful MacVim&#xA;theme in Vim for some time now and it is quite awesome. However QtCreator,&#xA;which I &lt;a href=&#34;https://yozy.net/2011/04/using-qtcreator-for-openvibe-development/&#34; title=&#34;Using QtCreator for OpenViBE development&#34;&gt;use for OpenViBE development&lt;/a&gt;, lacks such a theme. This problem was&#xA;easily fixed though. Here is a screenshot of a theme I have created and,&#xA;because of the lack of creativity, named &lt;em&gt;Gulf&lt;/em&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://yozy.net/images/Gulf-Qt-Creator-Theme.png&#34; alt=&#34;gulf-screenshot&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;And here is the link for download:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://yozy.net/files/downloads/gulf_qtcreator_theme.zip&#34;&gt;Gulf QtCreator theme&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
