4 ms·
Were there cases where rtags was not finding headers from your compilation database?
by dman 8y ago
Were there cases where rtags was not finding headers from your compilation database?
- ekoczwara 8y agoI've tried to setup rtags once again to provide detailed info, but I get: "RTags protocol version mismatch. This is usually caused by getting rtags.el from melpa and installing a new rtags build that modified the protocol. They need to be in sync." Anyway, I remember that I had negative experience with rtags.
- ekoczwara 8y agoOk, I've got it running. So the problem is: rtags-find-symbol-at-point opens wrong header files. I'm using custom sdk for embedded target generated by yocto. I need to be able to switch back and forth between desktop and embedded targets. Is this use case supported by rtags?
- dman 8y agoI never had to do that, so don't know if its an issue. I suspect it might not be smart enough to invalidate cache when you switch toolchains.
- ekoczwara 8y agoSo I've played with this some more. I've cleaned up everything, sourced environment-setup from my sdk, configured project with cmake, and now rtags-find-symbol-at-point can't find <iostream> (which is somewhere under /opt/etos/1.2/sysroots), rdm complains 'handleInclude failed (nil) ...' (https://pastebin.com/u39EGzdX https://pastebin.com/u39EGzdX). As 'Disclaimer' in https://github.com/Andersbakken/rtags/blob/master/README.org https://github.com/Andersbakken/rtags/blob/master/README.org says: 'RTags is still under development and is not the most stable piece of software you’ll ever find.'. Bugtracker on github has 123 opened issues. Do you consider RTags as serious option?