Basilisk 2.1.2 requires a clean build when adding/editing BSK messages - is there a plan to fix this/has this lalready been fixed in later versions?

[jbhagan]

When I edit/add a new BSK message, I cannot perform a quick rebuild with the diff of what I already have - I need to perform a clean build in order for Basilisk to work with the new message. Has this been fixed in later versions? Is there a plan to fix this behavior?

Apologies if this was already addressed elsewhere, I didn't see any mention of this in release notes or other conversations in this forum.

Thanks!

[schaubh]

This isn't a bug, but a requirement. When you run python conanfile.py the python script reads in all msg definitions and creates the associated C-msg wrapper code. There is no way to distinguish if a new message definition has been added, or if a message type has changed. Thus, intentionally, the msg system is wiped and rebuild each time you run python conanfile.py. If you are building modules, I recommend running python conanfile.py --buildProject False to only create the project and then compile in the IDE. This will yield much faster incremental build times.