Indexing Chromium #499
Unanswered
mohamedmansour
asked this question in
Q&A
Replies: 1 comment
-
|
The biggest problem would be figuring out how to run the indexers, particularly for the C/C++/ObjC code. Glean has support for CMake but not Ninja, so you'd need to build something to get the CDB (compilation database) for every C/C++/ObjC file from the build system and then invoke the Glean clang indexer. Glean's CMake support is here. Similarly for the other languages, you have to invoke the Glean indexer on the source files, but the non-C languages tend to be much simpler because there aren't as many dependencies from the build system. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Any tips on how to do this? Chromium contains a lot of languages like c, c++, obj-c, js, ts, python, go, and rust.
I am curious how it works in that scale. And I want to compare it to the speed of source.chromium.org when getting references for example.
Beta Was this translation helpful? Give feedback.
All reactions