I'm currently facing the problem to manage common libraries across addins/projects/attribs/layouts. The requirements in detail:
- There are complex tools which are spread across all parts of DOORS (i.e., addins, project-addins, layout dxl, attrib dxl, even triggers).
- There are libraries which these tools shall use in common.
- These libraries shall be located in exactly one place.
- Tools and libraries shall be outside of the DOORS program files structure, e.g., they are located in projects spaces.
To fulfill these requirements, things are easy as long as we talk about the non-library parts, i.e. those parts can be handled by applying multiple parts to the registry entries or command line parameters.
But: it seems to me that the libraries themselves cannot be placed in the required way, as the only path where DOORS is looking for code beside the addins, projects etc. is the DOORSHOME, and this is conflicting with requirement #4. And, the -H parameter obviously allows only one argument, not a list, like the other parameters.
The only solution I see is to replicate the DOORSHOME/* structure to the project space, and to put the libraries in there, and to redirect the DOORSHOME path by the relating registry entry/command line parameter.
Is this correct, or do you have any other idea?