gordonwatts commented 10 years ago

This might be related to issue #45. I have the following code in my autopkg file:

files {
  include: { "..\cppunit\include\**\*", ".\include\**\*" };

Lets say under ".\include" I have ".\include\TestPolicy\junk.h", then junk.h will be included but at the base level. So in the client project I can do #include "junk.h" - "TestPolicy/junk.h" will not work.

Now, if I add a second file, say ".\include\Dummy\dummyheader.h", then when coapp packs up the include files, they are set in a different directory.

This smells like a bug to me.

dinazil commented 9 years ago

The same happens to me. I'm using version 1.23.521.0.

dinazil commented 9 years ago

I ended up doing

nestedInclude: {

destination = ${d_include}\myclient;

         "${SDK}include*"
    };

instead of include: { "${SDK}include**" };

But from the tutorial (http://coapp.org/tutorials/building-a-package.html) it sounds like the original way should work. So maybe the tutorial should be updated?

coapp / coapp.powershell

Nested Includes Treated Differently depending on other directories #69

destination = ${d_include}\myclient;