enable kobuki Windows build#27
Conversation
…nto windows_bringup
enable windows build
|
Wondering if this breaks anything in Unfortunately, I've not got any windows CI running anymore. |
Since the entire porting effort includes changing Ideally everything should just work =) However, only packages consumed by BTW, quick question: are the |
|
Aye, lots of stuff there that made sense before later c++ versions became readily available, especially for embedded systems. I know of a few groups using it on non-Kobuki robots, albeit only a few of the libraries, but the main consideration is for a line of non-research robots (> 100k). For these it absolutely does not make sense to replace working code at the risk of introducing bugs when the existing code, even though it's not std, is working perfectly. As a result - this is one of the few libraries I do try to maintain - with extra emphasis on 'maintain'. I try not to fiddle with the API too much and if that desire is ever there, it should fork from this project and become an ECL2. |
|
Keep me tuned into the status of your windows build efforts - happy to help make it work on this side if you can validate all of the libraries working there. |
Thanks for explanation! That's very close to what I thought, I was thinking there must be some robotic applications running on platforms without well-established support of STL, thanks a lot for confirming that =) I will start to create a dashboard/markdown for all Windows-related changes, as well as enable and run ecl's test coverage on changed modules. Will be updating on this thread before the end of this week. |
this library needs to be updated in order to enable the kobuki code base to build on Windows
windows.h,windows.hshould not be included in header filesthis port points to the melodic release branch because it currently only targets ROS1.melodic