Add patch for imu_tools package

[wentywenty]

Fixes Windows-specific compilation issues

[wentywenty]

Run ls output/emscripten-wasm32
ls output/emscripten-wasm32
shell: /usr/bin/bash -l {0}
env:
ROS_VERSION: 2
SAVE_CACHE_AS_ARTIFACT: false
ls: cannot access 'output/emscripten-wasm32': No such file or directory
Error: Process completed with exit code 2.

This error in the sixth item of GitHub cil, do I need to modify any other files?

[wentywenty]

0s
Run pixi run python check_patches_clean_apply.py
pixi run python check_patches_clean_apply.py
shell: /usr/bin/bash -l {0}
env:
ROS_VERSION: 2
SAVE_CACHE_AS_ARTIFACT: false
No recipes with patches found – nothing to test.
1s
Run actions/cache/restore@v4
with:
path: output/emscripten-wasm32

key: Linux-emscripten-wasm32-pr-330
restore-keys: Linux-emscripten-wasm32-pr-330-

enableCrossOsArchive: false
fail-on-cache-miss: false
lookup-only: false

env:
ROS_VERSION: 2
SAVE_CACHE_AS_ARTIFACT: false
Cache not found for input keys: Linux-emscripten-wasm32-pr-330, Linux-emscripten-wasm32-pr-330-
0s
Run ls output/emscripten-wasm32
ls output/emscripten-wasm32
shell: /usr/bin/bash -l {0}
env:
ROS_VERSION: 2
SAVE_CACHE_AS_ARTIFACT: false
ls: cannot access 'output/emscripten-wasm32': No such file or directory
Error: Process completed with exit code 2.
0s
0s
0s
Run ls output/emscripten-wasm32
ls: cannot access 'output/emscripten-wasm32': No such file or directory
Error: Process completed with exit code 2.

[wentywenty]

This should not be my PR issue.

[traversaro]

Yes, that is a bug in the PR logic, feel free to ignore, thanks! Anyhow, yo ensure that the package is actually built, you need to increase its build number in https://github.com/RoboStack/ros-humble/blob/main/pkg_additional_info.yaml, and raise the build number in the comment in

ros-humble/vinca.yaml

Line 8 in 3cd1c60

# Reminder for next full rebuild, the next build number should be 14

to ensure that on next rebuild we raise the build number to 15.

[wentywenty]

Yes, that is a bug in the PR logic, feel free to ignore, thanks! Anyhow, yo ensure that the package is actually built, you need to increase its build number in https://github.com/RoboStack/ros-humble/blob/main/pkg_additional_info.yaml, and raise the build number in the comment in

ros-humble/vinca.yaml

Line 8 in 3cd1c60

# Reminder for next full rebuild, the next build number should be 14

to ensure that on next rebuild we raise the build number to 15.

Okay.

[wentywenty]

Do I need to modify the build number in pkg_additional_info.yaml and the comments in vinca.yaml according to your instructions?

Yes, that is a bug in the PR logic, feel free to ignore, thanks! Anyhow, yo ensure that the package is actually built, you need to increase its build number in https://github.com/RoboStack/ros-humble/blob/main/pkg_additional_info.yaml, and raise the build number in the comment in

ros-humble/vinca.yaml

Line 8 in 3cd1c60

# Reminder for next full rebuild, the next build number should be 14

to ensure that on next rebuild we raise the build number to 15.

[traversaro]

Ah, my bad, I was confused by the title of the PR, if the package was not built before there is no need to bump the build number.

[wentywenty]

Ah, my bad, I was confused by the title of the PR, if the package was not built before there is no need to bump the build number.

Thank you！

[traversaro]

@wentywenty Thanks you for the PR! In case you are interested in this, it may be useful to also propose the change you added here in https://github.com/CCNYRoboticsLab/imu_tools, so that we reduce the amount of patches we maintain locally here, see RoboStack/robostack.github.io#16 for issue on this effort in general.

[wentywenty]

@wentywenty感谢您的 PR！如果您对此感兴趣，不妨在https://github.com/CCNYRoboticsLab/imu_tools中提出您添加的更改，这样我们就可以减少本地维护的补丁数量。有关此工作的一般问题，请参阅[RoboStack/robostack.github.io#16 。](RoboStack/robostack.github.io#16)

CCNYRoboticsLab/imu_tools#218

okay~I have submitted a merge request.

[traversaro]

Thanks!