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
I have some projects with mixed python, c and c++ files. Since python is processed by pycscope and c/c++ is processed by cscope (besides ctags) it is a bit cumbersome to combine all things in just one database file (I need to parse and combine the cscope files before right now). It would be easier and way more practical if it was possible to cqmakedb to accept multiple -c (and also -t) input. Right now it doesn't.
Another thing that would be wonderful is if we could set a base path for files with relative paths.
And as a last wish (I know, too many wishes), it would be great if on filters we could put ';' to separate file extensions.
Anyway, nice app, thanks for sharing.
The text was updated successfully, but these errors were encountered:
Hi @andrecbarros, these are very good use cases that I personally don't use, especially combining several cscope.out files. I will look into adding these. Thank you for your support.
@andrecbarros I was wondering if I can simply append different cscope.out contents into one CodeQuery database, but the base path wouldn't be the same. That's the problem.
It is actually a wish.
I have some projects with mixed python, c and c++ files. Since python is processed by pycscope and c/c++ is processed by cscope (besides ctags) it is a bit cumbersome to combine all things in just one database file (I need to parse and combine the cscope files before right now). It would be easier and way more practical if it was possible to cqmakedb to accept multiple -c (and also -t) input. Right now it doesn't.
Another thing that would be wonderful is if we could set a base path for files with relative paths.
And as a last wish (I know, too many wishes), it would be great if on filters we could put ';' to separate file extensions.
Anyway, nice app, thanks for sharing.
The text was updated successfully, but these errors were encountered: