Nested Directories In Include Package

[akinakinyilmaz]

I try to get my include directory with its subdirectories into my include packet I use :
include: {"${X_FOLDER}__.h"};
However when I have a folder X that has one folder with .h files in X_FOLDER, in my package I see they are all extracted to root of include folder of my packet.
When I have two folders with .h files X and Y, I get my headers with my subdirectories X and Y in my include packet.
I read other issues but nestedInclude seems for limited usage, how it can be used for generic usage (when I have many subfolders down to X_FOLDER)

[zarkara]

Nested folders works (without collapsing subfolder tree if you specify like this. include: { "${X_FOLDER}__" }; You can also have multiple include sources like this: include: { "${X_FOLDER}_","${X_FOLDER2}*_" };
This assumes you have you autopkg file at some folder above all your paths and use a define like:
#defines { X_FOLDER = src\subfolder1\subfolder2;}

[swn1]

There's another issue about this and it includes a long rambling discussion about fixes and various changes that were made to the code, in the end it wasn't clear to me exactly what is in the release and how to invoke it. That said, here's the logic I'm using to deploy boost (just showing the header portion). It should do what you want in the current release; caveat emptor, I'm running a version built from my branch of coapp.powershell.

files{ 
    boostinclude: {
        #destination = ${d_include}\boost;
        boost\boost\**\*
    };
}
targets {
    Includes += ${pkg_root}/${d_include}; // see coapp.powershell issue #45.
}

NB: the second "boost" in the path is part of the logical file structure, the first one is injected into the header search path as /include; boost components expect to be included as #include <boost/foo.bar>. Some fiddling may be needed to get the structure to lay out the way you need it but this idiom captures the "trick" to getting it to work.