• View
• Edit
• History
• Print

0

Changes from CodeLite 1.0.XXXX

As of CodeLite 2.0, CodeLite no longer uses an external symbols database for code completing symbols which are not part of your workspace (e.g. fprintf(), wxString etc.). It is now using a 'File Crawler' to locate all the files that needs to be parsed based on the include statements found in your source files.

As a result, the codelite in codelite 2.0 is faster and allows the user to add as many third party libraries as he wishes without concern to the database size.

Configuring the Parser

In most cases, when starting codelite, it will try to auto-detect some basic paths and will add them to the parser include path. Note that these paths are used to locate include files and they are not scanned.

The parser search paths can be configured from the 'Settings > Tags Settings > Include Files' tab (as seen in the next picture)

The 'Include Files' page, has two sections:

• The Search Paths - these paths are used to locate 'include' statements in your code. So lets say you wrote in your code the following code snippet:

 #include <string>
 int main(int argc, char **argv)
 {
     std::string str = "hello world";
     return 0;
 }

Now when you save the file, the parser thread kicks in and does the following:

1. Scan the file for include statement, in our example: 'include <string>'
2. Next, it will use the search paths to locate the file 'string' (according to the 'Include Files' picture above, the file is found under C:\MinGW-4.4.0\lib\gcc\mingw32\4.4.0\include\c++)
3. The file is then parsed (along with all its include statements) and the symbols are stored into the database

So from this point on, codelite knows about std::string

• The second part of the 'Include Files' page, is the 'Exclude' section. Place here any path that you don't want codelite to locate files

Key Notes:

• Parsing is done only after a save operation or
• Manually invoking the parser (right click in the editor -> Retag file)
• Each workspace manages its own symbols database, so symbols available for one workspace might not be there for another workspace (unless the file containing them is also included somewhere in the workspace)

Tip: How to fast add / exclude paths to the parser

One could use the 'Explorer' tab to quickly add / exclude paths by selecting the folder in the 'Explorer' tree and from the context menu select 'Tags -> Add this path to the parser search path' OR 'Tags -> Add this path to the parser exclude path'