catkin/catkin_simple

catkin, simpler

catkin_simple's Issues

Release as debian

Any chance of releasing this as a debian into indigo (and jade)? Is there substantial effort or some open issue, or is it more about finding the time to do the release?

linking a non-catkin package

Hello,

I have an issue about linking a non-catkin package pangolin using catkin_simple. Since pangolin provides package.xml, intuitively I think it should work with catkin_simple. My catkin layout is set as merged. How I include pangolin in my package.xml is like:

<build_depend>pangolin</build_depend>

And the compiling error with catkin build my_pkg -j10 is like:

CMakeFiles/xodom_node.dir/node/xodom.cpp.o: In function `pangolin::GlBufferData::~GlBufferData()':
xodom.cpp:(.text._ZN8pangolin12GlBufferDataD2Ev[_ZN8pangolin12GlBufferDataD5Ev]+0x18): undefined reference to `__glewDeleteBuffers'
CMakeFiles/xodom_node.dir/node/xodom.cpp.o: In function `pangolin::GlBufferData::~GlBufferData()':
xodom.cpp:(.text._ZN8pangolin12GlBufferDataD0Ev[_ZN8pangolin12GlBufferDataD5Ev]+0x1c): undefined reference to `__glewDeleteBuffers'
CMakeFiles/xodom_node.dir/node/xodom.cpp.o: In function `pangolin::GlTexture::Reinitialise(int, int, int, bool, int, unsigned int, unsigned int, void*)':

It seems the headers are properly found, yet the libpangolin.so is not able to be linked.

I had made it with another non-catkin package sophus, yet it can be used in a header-only manner. I guess there might be some subtlties.

I know it would work if I write a catkin wrapper for it, but I just wonder is there any generic way to include a non-catkin package?

Many thanks!

utilize different dependency types introduced in package format 2

Confirmation that catkin_simple is under BSD License

I would like to confirm whether catkin_simple is licensed under BSD. The package.xml file states that the license is BSD, but there is no separate License file. Is this repository in fact BSD? Would it be possible to add a LICENSE file with the BSD license to the repo?

Thanks in advance!

Should we change the name to catkin_ros?

Since we are adding utility to minimize effort on message generation and because this is mostly targeted at the ROS community.

@dirk-thomas thoughts?

Take advantage of REP-0140 tag changes

This is obviously blocked on the ratification of REP-0140 and its implementation.

Add auto discovery of dynamic_reconfigure

How to force CMake to run again?

I'm doing some work with catkin_simple and new messages. I noticed this known limitation mentioned here:

If new .msg or .srv files are added, they will not be detected until you force CMake to run again

Is there a better way to do this than deleting your build and devel directories?

Edited to add: I'm using catkin_tools, not catkin_make.

Thanks.

add a check that package.xml declared a build dependency on catkin_simple

We do this in catkin and it saves a lot of easy mistakes. Catkin simple could do the same.

What catkin says.

CMake Error at /opt/ros/hydro/share/catkin/cmake/catkin_package.cmake:112 (message):
  catkin_package() 'catkin' must be listed as a buildtool dependency in the
  package.xml
Call Stack (most recent call first):
  /opt/ros/hydro/share/catkin/cmake/catkin_package.cmake:98 (_catkin_package)
  /home/tfoote/work/trailmix/devel/share/catkin_simple/cmake/catkin_simple-extras.cmake:170 (catkin_package)
  Redwood/3rdparty/gflags_catkin/CMakeLists.txt:34 (cs_export)

Installation

I'm a total newbie to this, sorry for the question, but how do I install/configure this?

rewrite CMakeList.txt

hi ,I want using cmake build my project,how to rewrite CMakeList.txt.

find_package buildtool_depends?

I think catkin_simple should find_package <buildtool_depends>, not just <build_depends>? Or do I misunderstand how buildtool_depends is meant to be used.

In my case I have a package that adds some cmake macros (similar to catkin_simple itself) which I use in the CMakeLists.txt of a package that buildtool-depends on that cmake-macro-package. My current workaround is to specify it as build-depend instead.

Add auto generation of actions

re

Replace catkin_simple command to normal cmake command(really need help)

Thanks for answering questions... This is an awesome project to make the catkin code easier to compile.
However, now I want to add Cuda compilation. Normally when I compile cuda, I need to change

add_library()

to

cuda_add_library()

now it is cs_add_library()
I really don't know how to do with it. If I simply change it to cuda_add_library() of course compile will give error so I am wondering how could I just make this piece of code back to the general CMake command?

Thanks so much for help!

build issue

after I built this pkg and when I catkin_make I get

Base path: /home/jaewon/catkin_ws
Source space: /home/jaewon/catkin_ws/src
Build space: /home/jaewon/catkin_ws/build
Devel space: /home/jaewon/catkin_ws/devel
Install space: /home/jaewon/catkin_ws/install

Running command: "make cmake_check_build_system" in "/home/jaewon/catkin_ws/build"

Running command: "make -j4 -l4" in "/home/jaewon/catkin_ws/build"

and deos not builds anything
I deleted all catkin simple directories and used catkin_make --force-cmake then gets this log

Base path: /home/jaewon/catkin_ws
Source space: /home/jaewon/catkin_ws/src
Build space: /home/jaewon/catkin_ws/build
Devel space: /home/jaewon/catkin_ws/devel
Install space: /home/jaewon/catkin_ws/install

Running command: "cmake /home/jaewon/catkin_ws/src -DCATKIN_DEVEL_PREFIX=/home/jaewon/catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/home/jaewon/catkin_ws/install -G Unix Makefiles" in "/home/jaewon/catkin_ws/build"

-- Using CATKIN_DEVEL_PREFIX: /home/jaewon/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/jaewon/catkin_ws/devel;/opt/ros/kinetic
-- This workspace overlays: /home/jaewon/catkin_ws/devel;/opt/ros/kinetic
-- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/jaewon/catkin_ws/build/test_results
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.7.6
-- BUILD_SHARED_LIBS is on
-- Using CATKIN_WHITELIST_PACKAGES: catkin_simple
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jaewon/catkin_ws/build

Running command: "make -j4 -l4" in "/home/jaewon/catkin_ws/build"

can I get some help?

Installation Issue

I am confused of how to install catkin simple. Can you tell me how to install it using catkin_simple package

Can we increment the package version?

We have a big team and I'm always in search of new ways to make our software report good error messages that help (even novice) team members solve the problem for themselves. This was the motivation behind the ALL_DEPS_REQUIRED option. However, with an old version of catkin_simple, this option is simply ignored.

Now, it would be great if we could increment the package version so that I can write my package.xml files to require a minimum version of catkin_simple that supports this option. Then people would get one message to upgrade catkin_simple then (after upgrade) another message that they have a missing package.

Possible?