We maintain a set of patterns starting with lib/ that we don't export to as they are part of the X-Plane built-in library system. We can't exclude all lib/ paths as some libraries publish to their own paths inside lib (strange but true) and we can't exclude all EXPORT_EXTEND entries because some libraries extend their own paths (stranger but truer).
The lib/ paths we ignore are currently hard-coded but it would be good if we could build this set by dynamically parsing all of X-Plane's built in libraries - then we would know for certain which paths we can and can't include.
We maintain a set of patterns starting with
lib/
that we don't export to as they are part of the X-Plane built-in library system. We can't exclude alllib/
paths as some libraries publish to their own paths insidelib
(strange but true) and we can't exclude allEXPORT_EXTEND
entries because some libraries extend their own paths (stranger but truer).The
lib/
paths we ignore are currently hard-coded but it would be good if we could build this set by dynamically parsing all of X-Plane's built in libraries - then we would know for certain which paths we can and can't include.