These guidelines describe the EGL files that you will most
likely share in a repository or source-control system and some common
problems that you might encounter when you share EGL projects.
The way that you share your projects in a repository or source-control
system depends on the type of repository or source-control system.
In general, you share source files and build files but not derived
files, which are created from other files. This way, the files
in the repository are limited to only those necessary for the application.
If you edit a file directly, it is probably not derived. For information
about derived files in the context of EGL, see “Project sharing.”
When you share projects in a repository, be aware of these possible
problems:
- When derived files are checked into a repository, they often lose
their derived flags. In this case, files that you normally would not
check into a repository might seem as though they need to be stored
in a repository.
- Checking files into a repository can break the connections between
files. For example, if you check a UML model and a TPM file into a
repository and then check them out, the workbench might not detect
that the two are associated. For information
about this problem, see “Linking a UML model to an existing TPM file.”
- When you share projects in a repository, the projects are subject
to the same potential errors that are described in “Project sharing.”