Missing compliance tests for external function annotations IncludeDirectory, Library and LibraryDirectory

[tbeu]

The models in ModelicaCompliance.Functions.ExternalObjects assume that ExtObj.c is found in the default InludeDirectory. There also should be a test (either there or in ModelicaCompliance.Functions.External) that utilizes the IncludeDirectoty annotation according to MLS 3.2r2 section 12.9.4.

There is no single test that utilizes the Library and LibraryDirectory annotations for custom libraries (except ModelicaCompliance.Functions.External.FortranLapack for tool vendor provided Lapack library).

[HansOlsson]

The problem with Library and LibraryDirectory is that it is compiler and operating systems dependent. There are some ideas for standardizing a form of "makefile" for that to ease distribution, and I would propose delaying the Library-part until then.