-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workaround for ROS buildfarm error. #27
Conversation
After this, prerelease test passed. |
if you revert this commit, you can merge -> #28 |
|
@@ -1,4 +1,9 @@ | |||
// test-com.c | |||
|
|||
/* | |||
* Build with `gcc -o`. See https://github.com/start-jsk/rtmros_hironx/blob/6eb507f3ad0ed368d909960dd59ddaac0f77f496/hironx_ros_bridge/robot/dynpick/Makefile#L9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test-com: test-com.c
gcc -o $@ $^
and that means gcc -o test-com test-com.c
. Build with gcc -o
sounds like gcc -o test-com.c
that's may results gcc: fatal error: no input files
Reported in-code at #25.
Implementing solution might be possible (example) but considering the effort it takes, having it built on ROS buildfarm is less beneficial. I rather mit it to be built.