Hi,

Whenever I opened a package into Qt Creator using the CMakeLists.txt file (previous method that I had before using your plugin) I was able to navigate through my code using Qt Creator shortcuts (e.g select the name of a function and press F2 to go into the function definition).

Now using your plugin, even though I am able to build everything I can't do that anymore. Does it work for you? maybe I have something wrong in my config.

thanks.

Hello,

I noticed that when I create a urdf file from the plugin the closing tag seems wrong.
auto-generated template:

<?xml version="1.0" ?>
<robot name="tmp" xmlns:xacro="http://ros.org/wiki/xacro">
    <link name="base"/>
    <link name="tool0"/>

</launch>

The closing tag is supposed to be </robot> and not </launch>

Not a big issue, this could be included in another PR.

executing direclty or sourcing wirks fine, but symlinking the wrapper does not open qtcreator any more. Seems like an easy fix, just open qtcreator directly without testing for names etc (here is the debug output):

• QT_BASE_DIR=/opt/qt57
• export QTDIR=/opt/qt57
• QTDIR=/opt/qt57
• export PATH=/opt/qt57/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
• PATH=/opt/qt57/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  ++ uname -m
• [[ x86_64 == \x\8\6_\6\4 ]]
• export LD_LIBRARY_PATH=/opt/qt57/lib/x86_64-linux-gnu:/opt/qt57/lib:
• LD_LIBRARY_PATH=/opt/qt57/lib/x86_64-linux-gnu:/opt/qt57/lib:
• export PKG_CONFIG_PATH=/opt/qt57/lib/pkgconfig:
• PKG_CONFIG_PATH=/opt/qt57/lib/pkgconfig:
  ++ echo qtcreator
  ++ grep wrapper
• TEST=
• '[' '' '!=' '' ']'

vs, when executing directly:

• QT_BASE_DIR=/opt/qt57
• export QTDIR=/opt/qt57
• QTDIR=/opt/qt57
• export PATH=/opt/qt57/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
• PATH=/opt/qt57/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  ++ uname -m
• [[ x86_64 == \x\8\6_\6\4 ]]
• export LD_LIBRARY_PATH=/opt/qt57/lib/x86_64-linux-gnu:/opt/qt57/lib:
• LD_LIBRARY_PATH=/opt/qt57/lib/x86_64-linux-gnu:/opt/qt57/lib:
• export PKG_CONFIG_PATH=/opt/qt57/lib/pkgconfig:
• PKG_CONFIG_PATH=/opt/qt57/lib/pkgconfig:
  ++ echo /opt/qt57/bin/qtcreator-wrapper
  ++ grep wrapper
• TEST=/opt/qt57/bin/qtcreator-wrapper
• '[' /opt/qt57/bin/qtcreator-wrapper '!=' '' ']'
  ++ echo /opt/qt57/bin/qtcreator-wrapper
  ++ sed s/-wrapper//
• exec /opt/qt57/bin/qtcreator

, which works fine

Hey

I'm having this problem compiling:

./ui_ros_package_wizard_details_page.h:13:25: fatal error: QtGui/QAction: No such file or directory #include <QtGui/QAction>

As far as I could see, QAction change from QtGui to QtWidgets. Can you help me with that? Thanks

I'm not sure if this is an issue or not. I've been working with a node that uses PCL, but the auto-complete is not working. I had to add (manually) the following to the workspace file:
<Directory>/usr/include/pcl-1.7</Directory>
Is this a known issue or user error? Should QT automatically add this based on the CMakeLists.txt?

After following the install procedure, I get the following error when opening qt57creator:

Hi,
When I use this new version ros_qtc_plugin. I can build project successfully. But when I want to run the project .In the step ROS run configuration, the ros_qtc_plugin cannot auto detect the package and node. So I should fill this message manually like this"ROS Step: rosrun beginner_tutorials listener". I cannot upload the picture by this . I remember that this can auto detect in the old version. Can you give me a old version？Because this is very confuse for a beginner. Thanks!

Hello everyone!

I thought I would give this plugin a try. I am using Sublime Editor 2 so far for all my ROS needs.

OS: Ubuntu 16.04
ROS Distro: Kinetic

I initially installed QtCreator in my system with sudo apt-get install qtcreator. I ran $ qtcreator and the application opened just fine.

Then I followed these instructions to install the plugin.

Some errors would occur during the apt-get update which wouldn't let the `apt-get install proceed':

$ sudo apt-get update && sudo apt-get install qt57creator-plugin-ros
Hit:1 http://gr.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://gr.archive.ubuntu.com/ubuntu xenial-updates InRelease                                  
Hit:3 http://gr.archive.ubuntu.com/ubuntu xenial-backports InRelease                                
Hit:4 http://ppa.launchpad.net/beineri/opt-qt57-xenial/ubuntu xenial InRelease                      
Ign:5 http://linux.dropbox.com/ubuntu wily InRelease                                                
Ign:6 http://ppa.launchpad.net/irie/blender/ubuntu xenial InRelease                                 
Get:7 http://linux.dropbox.com/ubuntu wily Release [6596 B]                                         
Get:8 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]                         
Hit:9 http://ppa.launchpad.net/levi-armstrong/ppa/ubuntu xenial InRelease                           
Hit:10 http://archive.canonical.com/ubuntu xenial InRelease                                         
Hit:12 http://ppa.launchpad.net/thomas-schiex/blender/ubuntu xenial InRelease                       
Ign:13 http://ppa.launchpad.net/irie/blender/ubuntu xenial Release                                  
Ign:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages                      
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages                       
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages                        
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US                   
Ign:18 http://desktop-download.mendeley.com/download/apt preview InRelease                        
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Hit:20 http://desktop-download.mendeley.com/download/apt preview Release
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata             
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons                
Ign:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages
Hit:24 http://packages.ros.org/ros/ubuntu xenial InRelease
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons
Ign:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons
Ign:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons
Ign:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons
Err:14 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 Packages
  404  Not Found
Ign:15 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main i386 Packages
Ign:16 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main all Packages
Ign:17 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en_US
Ign:19 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main Translation-en
Ign:21 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main amd64 DEP-11 Metadata
Ign:23 http://ppa.launchpad.net/irie/blender/ubuntu xenial/main DEP-11 64x64 Icons
Fetched 101 kB in 3s (28,9 kB/s)
Reading package lists... Done
W: The repository 'http://ppa.launchpad.net/irie/blender/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://ppa.launchpad.net/irie/blender/ubuntu/dists/xenial/main/binary-amd64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

I separately typed sudo apt-get install qt57creator-plugin-ros and the installation finished.

However, after typing $qtcreator to test things, I got

$ qtcreator
bash: /usr/bin/qtcreator: No such file or directory

It seems something broke.

Any thoughts?

Ubuntu: 14.04

The Qt Quick drop down list doesn't have a ROS item as described in 3.4 - #3

The plugin is bound to QTC 4.0. Compilation against latest branch 4.1 fails with lot of errors.

A symlinked package folder is not correctly searched for source files. Only some top-level files are shown (package.xml, etc). But all C++ sources are missing.

Hey, I love this plugin, it's fantastic, but I am having an issue.

When I try to run/Debug my node from within QtCreator, i get

No executable specified
Debugging has finished

I have set the Run Step to rosrun <package> <node> and I have a roscore running in the background, and I've tried starting qtcreator both from a terminal and from the supplied icon with the same result.

I can run successfully run the node from my terminal with rosrun <package> <node>

I've also read the instructions on your wiki, and if I choose Debug->Start Debugging->Attach to an Unstarted Application and select my Executable then check "Continue on Attach" I get into this crazy loop where the debugger stops responding.

I've simplified my main file as much as I can, and I'm starting with a long sleep() command as mentioned in #29 to no avail.

Any ideas?

Hello friendly people,

according to issue #60 , i have other questions.
Let say, this is how looks the structure of the package "catkin_ws" that i'm using and the node is called motive_node. So i have

/catkin_ws

       |_build
              |_catkin, catkin_generated, CMakeFiles
              |_motive_node, test_results
              |_CATKIN_IGNORE, catkin_make.cahe, camke_install.cmake, .....
        |_devel
              |_include, lib, share, setup.bash, ....
        |_gdb-7.7.1
        |_src
              |_motive_node
                           |_config, include, launch, src, CMakeLists.txt, CMakeLists.txt.user, ...
              |_build-motive_node-Desktop-Debug
                           |_catkin, catkin_generated, CMakeFiles, devel, src, test_results, CATKIN_IGNORE, ....
              |_CMakeLists.txt

ok , now i open for example 2 terminal,
First, on one: i source qtcreator and start it,

open project->catkin_ws/src/motive_node/CMakeLists.txt (according that i have already run the command 'catkin_make' a few days before).

qtcreator creates a new directory "build-motive_node-Desktop-Debug" with the new files, almost the same as the first directory build in 'catkin_ws/build'

on the 2nd terminal: i launch the node with roslaunch

And then i follow the instructions on issue #60 ,

1. Lets assume, you work with mocap in a company or at home and you have to connect ros to mocap using the command 'roslaunch', to get informations about motion (x,y,z) of the markers, that means the debugging can only work when this connection has been established, otherwise it cant work ?
   Because when the software is in another place, and you are at home and only have the package 'motive_node' with you, you can not start to debug for example the cpp data contained in 'motive_node/src/motive_data.cpp' , because you are not able to connect to the mocap software, because roslaunch will not work ?
   I ask, because it is not clear for me the meaning of attach to running application, unstarted application and start and debug external application? i thought that it would be possible to debugg the cpp data without to run 'roslaunch' , using unstarted application. Because like i said, when i'm in another place i can not run roslaunch and i want to make some modifications in the cpp data.

2. when i follow the instructions on issue #60 , i also get
   QIODevice::read (QFile, "/proc/9701/stat"): device not open
   QIODevice::read (QFile, "/proc/9702/stat"): device not open
   QIODevice::read (QFile, "/proc/9708/stat"): device not open
   QIODevice::read (QFile, "/proc/9711/stat"): device not open
   ...

but i am still able to debug. Is it bad to have device not open on the console?

3. After that i have try

open project->catkin_ws/src/motive_node/CMakeLists.txt (according that i have already run the command 'catkin_make' a few days before).

then i tried

open project->catkin_ws/src/CMakeLists.txt (according that i have already run the command 'catkin_make' a few days before).

And then

Projects->build->Edit build configuration: Debug

A new project and new directory were created 'catkin_wsbuild-src-Debug' under catkin_ws/catkin_wsbuild-src-Debug, containing also the information,

what do you think is the preferred version between the 2 variants? Or is it better to directly import the workspace using import ros project?

4. Let say , i have a code which looks like this

#include "motive_node/motive_data.h"
#include "motive_node/motive_config.h"
#include <ros/ros.h>
#include <tf/transform_datatypes.h>
#include <string>

int main( int argc, char* argv[] )
{
// Initialize
ros::init(argc, argv, "mo_node");
ros::NodeHandle n("~");

string infos = "My first stream"
ROS_DEBUG_STREAM("Info" << infos)
}

I can not stream the info on the console. Also ROS_DEBUG doesnt work?

Does anyone can help?

Thank you so much!
Sami

When clicking on header files, QTC opens headers from the underlay (e.g. /opt/ros).
Probably include directories are not setup correctly.

Proposed agreement is below:

/**
 * @copyright Copyright (c) 2016, Southwest Research Institute
 *
 * @license Software License Agreement (Apache License)\n
 * \n
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at\n
 * \n
 * http://www.apache.org/licenses/LICENSE-2.0\n
 * \n
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

Does the current version of plugin support auto-complete for ros related variables, package name, parameter names, xml tags etc. If yes, please mention how to use it. I could auto complete using tradition al Ctrl+Space.

I am not getting code completion while typing. When I go into Help->About plugins, I don't see the Clang model plugin.

Any ideas?

Hi Levi,

My installation process went kind of smooth I guess, but the plug-in was not added in qt creator.

1. I can't see the ros workspace option in the import drop list;
2. There was no ros related plug-in the plug-in list either.
   any suggestions?
   

thanks.

It'd be great if the exact (minimal) version numbers for dependencies such as Qt and Qt Creator could be listed somewhere, probably the repository readme.

From setup.sh I gather that it clones the 4.0 branch of Qt Creator, so if that means that the dependencies are basically those listed in the qt-creator/readme.md, something along the lines of "refer to the Qt Creator readme for further dependencies" could be enough.

I'm not using this plugin, but I was looking at it as an example.

This spelling mistake jumped out at me:

https://github.com/ros-industrial/ros_qtc_plugin/blob/master/setup.sh#L79

As far as I can tell, it has been renamed to opt-qt571-trusty (from opt-qt57-trusty).

The wiki should probably be updated to reflect this.

Hey,
I just upgraded qt57creator-plugin-ros:amd64 from 0.1.3-0trusty2 to 0.1.4-0trusty4 with apt.
I closed my qt creator 57 session before. Everything was working fine till then. Qt Creator found my workspace and saved all paths in the catkin.workspace file.

After the upgrade qt creator won't find any libs or included files. (See pic, all red underlined files or libs cant be found).

I tried to import the catkin workspace again, so your plugin exchanged the workspace file with paths to a one without any paths:
<?xml version="1.0"?> <Workspace> <Distribution name="indigo"/> <DefaultBuildSystem value="0"/> <WatchDirectories> <Directory>src</Directory> </WatchDirectories> </Workspace>
Compiling doesn't work anymore too. Nothing happens, no error messages whatsoever.

What needs to be done to make your QtCreator57 work again?

Thanks in advance :)

I noticed that when the plugin is active I can not modify the formatting in Preferences->C++->Code Style.

To be precise, I change them, but my settings are ignored

The disable tab for ROS Step was not functioning. To simply put, if I have 3 ROS Steps in a specific run configuration, disable tab does not allow me to disable the ROS Step. ROS still launches all the nodes included in the run configuration.

Does this only happen to me or is there anyone sharing the same issue?

Thanks!

Is it possible to enable catkin tools support to the build process? How can I change this setting?

Thanks!

Hi,
Could you please give us a brief tutorials on how to do basic rosrun and roslaunch using the plugin? THX!

What's the purpose of the Update button in build settings?

I tried to update my project tree to re-generate the list of include directories. But didn't work.
The ROS distribution button resets to Groovy after restart. By the way, what about newer ROS releases?

After following
https://github.com/ros-industrial/ros_qtc_plugin/wiki/1.-How-to-Install-(Users-&-Developers)#section1.2
on ubuntu16.04 with qtcreator already installed, I got:

Unpacking qt57creator (4.0.2-1basyskom1) ...
dpkg: error processing archive /var/cache/apt/archives/qt57creator_4.0.2-1basyskom1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/mime/packages/Nokia-QtCreator.xml', which is also in package qtcreator-data 3.5.1+dfsg-2ubuntu2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

of course
dpkg --remove qtcreator-data ; apt-get -f install
solved the problem, but you might want to conflict (remove) with qtcreator-data not just qtcreator itself.

Hi Levi.

I'm not sure where else I'm supposed to send you this, I looked for an email address but didn't see one. I apologize if this is the incorrect location to to be asking these questions.

I'm pretty new to Linux, QT and ROS. So, I'm sorry if the questions I'm about to ask are very basic...

I'm trying to get your ROS QT plugin setup properly but having some issues. I'm sure it's all user error from not undertanding all this properly.

In your WIKI, you said download the latest version of QT. I already have QT installed sure it's up to date.

In step 1.1, you mention to configure QT Chooser to look at :
/home//Qt//gcc_64/bin
/home//Qt//gcc_64/lib

I'm curious why I'd need to tell QT Chooser to look here when QT is already setup just fine with my pre existing install of QT.

In step 1.2 I'm going on the assumption that this is an either-or. Either setup for users or setup for developers. Yes? For now I just want to setup for users. I saved the bash script and executed it. As you probably know, this created the qtc_plugins folder. I also noticed that it downloaded what looks to be a full install of QT via the qt-creator directory. I'm curious to know what this is for.

in setup 1.3, you mention launch QT creator via the command prompt $qtcreator. When I run this I get an error stating "The program qtcreator is currently not installed .......

However, QT launches just fine if I click the icon from app launcher. When I launch from the app launcher, I go into new project, import project, I don't see any type of ROS workspace.

Was hoping you might be able to shed some light on my issues.

Thanks!

The active branch is not shown next to the folder name until the project is closed and opened again.

I installed your new qt creator 4.2 with qt 5.7.1 build in my new (clean) ubuntu 14.04 virtual machine.
I used your new PPA cause the old benri PPA wasn't available any more.
After installation I can start your qt creator but it is not loading properly.

The "Welcome" page stays black and it is not possible to click any menu button. It doesnt open anything.
You can choose the "Edit" page, but you can not open anything. There is no right click menu or anything working. Most of the time those pressing actions result in a crash of qt creator.

I tried reinstalling the plugin and "apt-get purge" the whole qt creator and installing it again.
Didn't help.
Can you help me solving the problem?

Thanks in advance!

PS: My work installation still works fine (the older Qt Creator 4.1 build with Qt 5.7.0), but I did not add the new PPA yet there so I guess it didn't update.

I'd like to suggest the following to make the installation instructions clearer:

1. more clearly define what users of the plugin are, and what developers are

2. split the current Setup ROS Qt Creator Plug in wiki page into two separate pages, one for users (just the PPAs and apt-get line), the other for developers (using setup.sh)

3. clearly mark both pages as separate procedures, so as to avoid users assuming that they have to follow both (the page currently starts the developer section with: "This section explains how to setup your system for development", which can be really confusing (development of what?))

4. condense the 'user install' to just three lines (for Trusty, but similar for Xenial):

   sudo add-apt-repository ppa:beineri/opt-qt57-trusty
   sudo add-apt-repository ppa:levi-armstrong/ppa
   sudo apt-get update && sudo apt-get install qt57creator-plugin-ros
   

   Dependencies will be automatically installed by apt-get, no need to do everything separately.

5. clearly mark the PPA instructions as Ubuntu only, and possibly include steps for non-Ubuntu users?

I ran into the following errors while executingsetup.sh to install the plugin.

/usr/bin/ld: cannot find -lProjectExplorer
/usr/bin/ld: cannot find -lCppTools
/usr/bin/ld: cannot find -lQtSupport

I downloaded and installed before Qt 5.7 though the *.run file and edited qtchooser.
I am going to try again on a fresh instal.

Hi!

After building QtCreator and the ROS plugin with the script, I open QtCreator in a terminal, import an existing ros workspace, and when I try to open it, QtCreator force close and gives a segmentation fault.

Any idea?

Thanks.

It's a detail but Qt is "cute" and QT is QuickTime.
The YouTube video title and the wiki should be edited

Hi,
I just tried to install qt57creator-plugin-ros follwoing the installation instructions for "Users". Adding the ppa's worked fine. But when I try to install the plugin, I get:

ros@base:~$ sudo apt-get update && sudo apt-get install qt57creator-plugin-ros
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]
Hit:2 http://de.archive.ubuntu.com/ubuntu xenial InRelease                                           
Hit:3 http://ppa.launchpad.net/beineri/opt-qt57-xenial/ubuntu xenial InRelease                                                  
Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease                                                                    
Hit:5 http://ppa.launchpad.net/levi-armstrong/ppa/ubuntu xenial InRelease                                 
Hit:6 http://dl.google.com/linux/chrome/deb stable Release                                                
Hit:7 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease      
Hit:8 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:10 http://packages.ros.org/ros/ubuntu xenial InRelease
Fetched 94,5 kB in 5s (16,5 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qt57creator-plugin-ros : Depends: qt57creator (>= 4.0.2) but it is not installable
E: Unable to correct problems, you have held broken packages.

My setup:

• Ubuntu 16.04
• ROS Kinetic
• Qt Creator 4.1.0

Regards

Hello everyone,

unfortunately, since today, the ROS Qt Creator Plug-in does not stop at Breakpoints.

On the terminal, where I started sudo /opt/qt57/bin/qtcreator, it shows the following:

QIODevice::read (QFile, "/proc/9692/stat"): device not open
QIODevice::read (QFile, "/proc/9173/stat"): device not open
default KB_LAYOUT_DIR: "/usr/share/qtermwidget5/kb-layouts"
loadAllColorSchemes
QIODevice::read (QFile, "/proc/9701/stat"): device not open
QIODevice::read (QFile, "/proc/9702/stat"): device not open
QIODevice::read (QFile, "/proc/9708/stat"): device not open

QIODevice::read (QFile, "/proc/9692/stat"): device not open
QIODevice::read (QFile, "/proc/9173/stat"): device not open
default KB_LAYOUT_DIR: "/usr/share/qtermwidget5/kb-layouts"
loadAllColorSchemes
QIODevice::read (QFile, "/proc/9701/stat"): device not open
QIODevice::read (QFile, "/proc/9702/stat"): device not open
QIODevice::read (QFile, "/proc/9708/stat"): device not open
QIODevice::read (QFile, "/proc/9711/stat"): device not open
QIODevice::read (QFile, "/proc/9714/stat"): device not open
QIODevice::read (QFile, "/proc/9715/stat"): device not open
QIODevice::read (QFile, "/proc/16212/stat"): device not open
QIODevice::read (QFile, "/proc/16216/stat"): device not open
"The command "/qmake" could not be started."
*** UNEXPECTED STATE TRANSITION: Debugger::Internal::GdbAttachEngine(0x6bef230, name = "GdbEngine") "State changed from EngineRunRequested(7) to EngineShutdownRequested(19) [master]"
QProcess: Destroyed while process ("/bin/bash") is still running.
QProcess: Destroyed while process ("/bin/bash") is still running.

I didn't write all lines, there are several more lines similar to this " ... device not open"

It's so weird because it worked till today!?
I always clicked on Debug-> Start Debugging->Attach to unstarted application--> and then choose the executable and start watching and then I click Ctrl+R .
Does anyone know why?
Thank you so much!

Gre

This plugin builds on top of catkin_make, which handles the whole workspace as a single cmake project.
Obviously this facilitates QTC integration. However, catkin_make has several drawbacks and there are more recent build tools available, e.g. catkin tools that tackled those issues.
Are there any plans to support / switch to catkin tools?

I just installed the plug-in and all seemed to go well. But when I attempt to create a new ROS package Qt crashes when I click finish. I'm running Ubuntu 16.04.

It did work once when I put dummy items in the depends fields. But only once. Also, I made a sample URDF file without any problems.

This looks like an excellent product. Any help would be appreciated.

Sincerely,

Mike Armstrong

With Alt-8 it is possible to see the opened ROS terminals when you are running a node or a launch file. If you press the Red button it will stop the current terminal, but if you don't have any terminal then it seg faults Qt creator.

It was found when importing a workspace like ros-planning/moveit that the codeblock project files where not being generated resulting in no include directories for the project.

I didn't find an option for adding msg and srv files into the package, is this feature supported ?
while msg and srv files are usually pretty simple , they require several changes in the CMakeLists.txt file.
I hope you add a wizard for adding those files and their dependencies, making necessary changes in CMake files.

Hi,

I followed the wiki install instructions but when I try to set the code format to ROS:

2.4 Set ROS Code Format

Open Qt Creator
Goto: Tools > Options > C++ > Code Style
Select ROS from the Current Settings drop down list.
Goto: Tools > Options > Qt Quick > Code Style and repeat step 3.
Also need to change indent size to 2 space: Tools > Options > Text Editor > Behavior

This options are not available. I am sure that I am using the new Qtcreator compiled version.

Details of my computer:

Ubuntu 14.04
Qt Creator 4.0.2
Based on Qt 5.6.0 (GCC 4.8.4, 64 bit)

Hi, dear Authors:

I installed this plugin with Qt5.7 and learned how to use it from this issue and wiki.

But, when I want to debug some ros package code using " Menu Bar > Debug > Start Debugging > Attach to Running Application..." . I found some pkg labeled with [develop] can be debuged. While other pkg labeled with [master] can not be set breakpoint.

Could you tell be how to deal with it? Thanks in advance!

I have met following problem related to unmet dependencies.

wkyoun@wkyoun-XPS-13-9343:~/catkin_ws/src$ sudo apt-get install qt57creator-plugin-ros

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qt57creator-plugin-ros : Depends: qt57creator (>= 4.1.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.