I'm evaluating CLion for suitability to purchase for work on a large, commercial C project. It seems that the only way to leverage the code navigation feature is to have CLion be able to compile the project with cmake integration. This is a non-starter for us as the compilation system we're using is highly customized and tied into a number of non-Make-based scripts and environment settings.
Furthermore, we need to be able to explore & navigate codebases on otherwise read-only filesystems, as 1.) the build takes very long; 2.) we have trees we publish on network filesystems that we cannot write in-place.
I'm comparing CLion against the venerable "vim" with ctags integration, which allows me to quickly and easily navigate the entire codebase with a single tags file generated. With CLion, it appears I cannot navigate the code unless I use its native build/make integration. If this is true, we cannot be a customer.
Please tell me there is a non-invasive, non-destructive method of using CLion to view and navigate the tree.