When you create a project with existing sources the project is parsed to support the code assistance features of the IDE. The parsing data is saved on disk in the code assistance cache. Each time you open the project the IDE examines the cache and if necessary parses any changed or new files to update the cache.
By default the IDE creates one code assistance cache for all your projects in your user directory. The cache in your user directory cannot be copied or shared.
Parsing can be triggered when you update a project from a code repository in a version control system such as Subversion or Mercurial. For large projects, it can take a long time.
A solution is for one developer using this version of the IDE to create a project-specific cache and copy it to a shared location where other developers using this version of the IDE can copy it to their computer. Then each developer can modify their project properties to reference the copied cache. After this, the parsing when you open the project is much faster.
In order to use a code assistance cache copied from another computer, your computer must meet the following requirements:
Note that if your team uses several different versions of operating systems and tool collections, you must create a different version of the cache for each combination of operating systems and tool collections.
To instruct the IDE to create the code assistance cache in a non-default location:
Add the line cache.location=nbproject/private/cache to one of the following files:
The IDE parses the project and places the code assistance cache in nbproject/private/cache. For very large projects this can take a long time.
Note: It is important to exit the IDE before zipping or copying to ensure all data is flushed to cache.
To use a pre-generated code assistance cache:
The IDE uses the copied code assistance cache instead of reparsing the project. If there are some newer files on the machine to which you copied the cache, only newer files are parsed.
See also | |
---|---|
Configuring Code
Assistance Settings for C and C++ Projects Using Properties Files for Version Controlled Projects |
Copyright © 2015, Oracle and/or its affiliates. All rights reserved.