As EvoAl uses a domain-specific language that supports an import mechanism, EvoAl must find used files. Pitifully, the two main use cases have a slightly different lookup strategy.
## Eclipse search path
In Eclipse, your DSL files will be located in a project (it is sufficient to create a general project). When you create your first DSL file, Eclipse will ask if you want to add Xtext capabilities. Please answer **yes** here.
In Eclipse, your DSL files will be located in a project (it is sufficient to create a general project). When you create your first DSL file, Eclipse will ask if you want to add Xtext capabilities. Please answer **yes** here. In your DSL file, you can import everything that is within the project.
## Importing pre-defined EvoAl files
At the moment it is necessary to add the definition files from EvoAl to your Eclipse project. The easiest way is to create a new folder in your project and specify it to be a symbolic link in the advanced settings.
## Importing files from a different Eclipse project
If you want to import files from another project, you have to add a project dependency. Therefore, you have to add the dependency in the project settings of Eclipse.
