ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

As of right now, it seems like both wrapper scripts are not generated with the executable flag set. Consequently, rosrun cannot run anything for me. Manually editing the files once generated is still a solution, but needs to be done often. Instead, I am using the following Makefile in my rosjava package.

SOURCES=$(shell find src/main -name *.java)
PACKAGE=<PACKAGE-NAME>

all: installed

installed: $(SOURCES)
    `rosstack find rosjava_core`/gradlew installApp
    mkdir -p bin
    ln -sf ../build/install/$(PACKAGE)/bin/$(PACKAGE) bin/$(PACKAGE)
    chmod a+x bin/$(PACKAGE)
    touch installed rospack_nosubdirs

clean:
    `rosstack find rosjava_core`/gradlew clean
    rm -rf bin installed rospack_nosubdirs

To use this Makefile, you'll have to manually replace PACKAGE-NAME once. This solution isn't exactly pretty, but works effectively well and allows for rosmake/make to build the package as well. I am interested if there are any other better solutions around.

As of right now, it seems like both wrapper scripts are not generated with the executable flag set. Consequently, rosrun cannot run anything for me. Manually editing the files once generated is still a solution, but needs to be done often. Instead, I am using the following Makefile in my rosjava package.

SOURCES=$(shell find src/main -name *.java)
PACKAGE=<PACKAGE-NAME>

all: installed

installed: $(SOURCES)
    `rosstack find rosjava_core`/gradlew installApp
    mkdir -p bin
    ln -sf ../build/install/$(PACKAGE)/bin/$(PACKAGE) bin/$(PACKAGE)
bin/execute
    chmod a+x bin/$(PACKAGE)
    touch installed rospack_nosubdirs

clean:
    `rosstack find rosjava_core`/gradlew clean
    rm -rf bin installed rospack_nosubdirs

To use this Makefile, you'll have to manually replace PACKAGE-NAME once. You can then use "execute" as the node type.

This solution isn't exactly pretty, but works effectively well and well. It also allows for rosmake/make to build the package as well. I am also interested if there are any other better solutions around.