Path variables
Use path variables to define absolute paths to resources that are not part of a specific project. These external resources may be located in different places on the computers of your teammates. This is why user-defined custom path variables are not stored as project settings, but as global IDE settings. Once configured, such path variables will have the same value for any project that you open with your instance of GoLand.
Create a new path variable
Press Ctrl+Alt+S to open settings and then select .
Click
, enter the name and value of the variable, and click OK to apply the changes.
You can use path variables to specify paths and command-line arguments for external tools and in some run configurations. For more information, refer to Built-in IDE macros.
For example, you can define a path variable that points to the location of some data source (like a CSV file) or a third-party library that is not stored in your project. If you use this path variable in a run configuration that you share with your project, others can define the correct value for this path variable in their environment and be sure that the run configuration will work for them.
Another example is defining a path variable for the attached directory that you use in your project. On another machine, the directory might be stored in a different location. To make sure your project with the attached directory can be shared and used on another machine, use path variables to define the location of the attached directory.
Refer to the variable as $var_name$ in fields and configuration files that accept path variables.
GoLand also has the following built-in path variables:
- $USER_HOME$
The current user's home directory.
- $PROJECT_DIR$
The current project's root directory.
Ignore path variables
Whenever you open or update a project, GoLand checks for unresolved path variables. If the IDE detects any, it will ask you to define values for them. If you are not going to use files or directories with the unresolved path variables, you can add them to the list of ignored variables.
You can also use the list of ignored variables when a program argument passed to the run/debug configuration has the same format as a path variable (for example, an environment variable).
Press Ctrl+Alt+S to open settings and then select .
Add the names that GoLand shouldn't consider to be path variables to the Ignored Variables field.
Click OK to apply the changes.
Example: creating a new path variable
You may have a library that is located outside your project directory. This library is attached to your project, and the path to this library is included in the .iml file of your project. However, this path should not be absolute, because the location on this library may be different on your teammates' computers. In this case, you can create the PATH_TO_LIB variable:
Press Ctrl+Alt+S to open settings and then select .
Click
.In the Add Variable dialog, type the
PATH_TO_LIBvariable, and its value that points to the library location on your disk.Share the .iml file through your version control system.
After your teammates update their projects from VCS, they will change the
PATH_TO_LIBvariable value so that it points to the library location on their computers.