
When you open a project, AppCode checks if there are any unresolved path variables.
APPCODE DISMISS FIND IN PATH UPDATE
Share the IML file through your version control system.Īfter your teammates update their projects from VCS, they will change the PATH_TO_LIB variable value so that it points to the library location on their computers. In the Preferences dialog ( Ctrl+Alt+S), select Appearance & Behavior | Path Variables, and click the button.Įnter the name of the new variable (for example, PATH_TO_LIB) and its value that points to the library location on your disk. If you want to make sure that the path is correct on your teammates' computers after they update the project from VCS, you can create a new variable. To configure path variables, in the Preferences dialog Ctrl+Alt+S, select Appearance & Behavior | Path Variables.įor example, you have a third-party library that is not stored in your project directory. $MODULE_DIR$: stands for the directory that keeps module configuration files IML. $PROJECT_DIR$: stands for the directory where your project is stored. $USER_HOME$: stands for your home directory. In AppCode, there are some pre-defined variables: If you use a path variable, you make the path relative as each variable is configured on each computer individually. Such a library is referenced by its absolute path and there is no guarantee that this path is the same on computers of your teammates.

Path variables are useful if, for example, you have a third-party library defined at the project or module level, and it is stored outside the project directory or module content roots (for projects shared through VCS). They provide sharing flexibility as you do not have to reference a fixed location on your computer. Path variables are placeholders that stand for paths to resources linked to your project.
