For starting roscore, it requires a number of runtime dependencies.
At the moment, all runtime dependencies, even recursive runtime dependencies,
are added only in the roslaunch recipe. Hence, the recipe contains all
runtime dependencies.
At a later stage, one should move the recursive runtime dependencies into
the appropriate recipes.
In the topic-tools recipe, a QA error was raised as the .debug files were put
into the main package. By adding this line in the catkin class, the files are
now placed in the dbg package.
The CMake generate_messages function from the genmsg package
detects the installed message generators via files in the
/usr/etc/ros/genmsg directory. Stage the /usr/etc directory
manually as it is not a common path.
Fixed#50
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Rostest depends on its own package and therefore needs to search
in the devel space for the rostestConfig.cmake during native
build.
| CMake Error at /.../usr/share/catkin/cmake/find_program_required.cmake:5 (message):
| rostest not found
|
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
All ROS packages with install tools in the bin directory or install
python code with is used by other packages should be used as native
version. Adapte the DEPENDS accordingly.
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Adapt genmsg to handle msg files relatively to the current
cmake path. Without this modification genmsg failed to generate
messages because it pass a path without sysroot to the python
code.
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Catkin require a .catkin file in all CMAKE_PREFIX_PATH to add them
to the CATKIN_WORKSPACES. Remove this requirement as it couldn't
be satisfy when catkin packages are installed into the common usr
prefix. Without this adaption catkin couldn't find all files.
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Replace CXXFLAGS += "-fPIC" with EXTRA_CXXFLAGS to allow native
build and use relative paths to simplify recipe.
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
In the previous commit, I accidently also edited another line than intended and
missed to see the accident before committing.
This commit reverts that accident.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
In the future, all test reports are supposed to be tracked and archived in the
meta-ros-test-reports git repository. This git repository is linked into the
meta-ros with a git submodule in the directory test-reports.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
The commit 83c813b8c3 was due to an experiment
to cross-compile some packages and compile other on the target.
It turned out that there are a couple of difficulties and stopped working on
that experiment.
To obtain a working native compilation of ros-groovy,
this commit reverts the commit 83c813b8c3 to
a state where the installation and compilation worked.
In the current state, the catkin recipe does not work on the target system.
We want to keep the native compilation of ros groovy working, even if our
current development is focusing on the cross-compilation.
To make the native compilation of ros groovy more stable, we go back to the
previous state where even catkin was compiled on the target system.
Hence, this commit reverts commit 2c8274b74f
to obtain that previous state.
The conflicts in the files of this commit were manually resolved.
The recipes were created by manually extracting the information
from the corresponding package.xml.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
After the release of ROS groovy, there is no strong reason to
continue to work on the cross-compilation of the previous ROS
version fuerte. Hence, this commit removes the initial
non-functioning recipe and the reference in the README file.
For cross-compiling ROS fuerte, the repository at
https://github.com/yida/yida-collections
might be a better starting point anyway.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>