Revision history [back]

Looking at the CMakeLists.txt of ackerman_description, there seem to be no install(..) rules. Without those, no files will be, well, installed.

For ackerman_description, something like:

install(DIRECTORY launch urdf
  DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})

should do.

See catkin 0.6.14 documentation » How to do common tasks » Building and installing targets for more information (and examples) of how to do this.

Looking at the CMakeLists.txt of ackerman_descriptionackerman_vehicle_description, there seem to be no install(..) rules. Without those, no files will be, well, installed.

For ackerman_descriptionackerman_vehicle_description, something like:

install(DIRECTORY launch urdf
  DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})

should do.

See catkin 0.6.14 documentation » How to do common tasks » Building and installing targets for more information (and examples) of how to do this.

Looking at the CMakeLists.txt of ackerman_vehicle_description, there seem to be no install(..) rules. Without those, no files will be, well, installed.

For ackerman_vehicle_description, something like:

install(DIRECTORY launch urdf
  DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})

should do.

See catkin 0.6.14 documentation » How to do common tasks » Building and installing targets for more information (and examples) of how to do this.

<export>
  <architecture_independent />
</export>

Looking at the CMakeLists.txt of ackerman_vehicle_description, there seem to be no install(..) rules. Without those, no files will be, well, installed.

For ackerman_vehicle_description, something like:

install(DIRECTORY launch urdf
  DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})

should do.

See catkin 0.6.14 documentation » How to do common tasks » Building and installing targets for more information (and examples) of how to do this.

I think that distribution of ackermann_vehicle as Ubuntu packages used to work

Looking at the history of the CMakeLists.txt in ackerman_vehicle_description that seems unlikely, as there has only ever been one version of that file, and it never contained the required install(..) statements.

Edit: I'd also suggest adding the architecture_independent tag to the export section of your package.xml, as ackerman_vehicle_description does not contain any artefacts that will need to be rebuild for different processor architectures (ie: x86 vs x64, etc). That saves the buildfarm some effort, and results in your packages becoming available sooner. Just add the following to the end of your manifest:

<export>
  <architecture_independent />
</export>