You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But after any change in the main.rs file, the rust target rosrust_msg takes a lot of time to build.
With the -vv flag of cargo build, I have noticed that the list of files printed with cargo:rerun-if-changed= includes literally all the files of my ROS workspace, including .git content for each package.
Commenting the following lines fixed the issue and only the .msg and .srv files are listed, which avoids the rosrust_msg rebuild after any change.
From all of my testing of how this trigger works, the rerun trigger needs to include the hierarchy of folders that we're looking at, otherwise adding a new .msg file won't be registered.
Overly eager rebuilds would be reduced by filtering out folders that we know won't contain message files, like .git.
I have using
rosrust
in a catkin workspace and use catkin to build the nodes using these lines in theCMakeList.txt
file, inspired from # 113But after any change in the
main.rs
file, the rust targetrosrust_msg
takes a lot of time to build.With the
-vv
flag ofcargo build
, I have noticed that the list of files printed withcargo:rerun-if-changed=
includes literally all the files of my ROS workspace, including.git
content for each package.Commenting the following lines fixed the issue and only the
.msg
and.srv
files are listed, which avoids therosrust_msg
rebuild after any change.rosrust/rosrust_msg/build.rs
Lines 84 to 86 in 2b75da0
I understand that using
rosrust
with catkin is not yet supported but maybe we can only add folders with namessrv
andmsg
in the list?The text was updated successfully, but these errors were encountered: