Not possible to have a folder hierarchy in an imported library?

[zfields]

Is it not possible to have a folder hierarchy in an imported library? If not, why? Seems important for larger libraries with greater functionality.

[zfields]

This issue was valid as of 2015/02/16. I'm cleaning my inbox and translating all my notes into issues.

[kennethlimcp]

@zfields, what test did you do this verify this?

[zfields]

Test? I had a folder hierarchy in my code, where files used #include's with relative paths (successfully comepiled with BSD Unix). When I tried to compile with your compiler, they were unable to reference each other to compile. Then I flattened the whole thing and it worked. This is as of 2015/02/16, as I stated. I found an old email I wrote to the Spark team, and converted it to an issue this morning.

[joegoggins]

Hey @zfields , thanks for reporting this issue as well as the others in this repo, it really helps to pull together the pain points people have experienced with libraries so we can write up a spec/roadmap for another iteration that addresses them. I'm working with @suda on this now and will be drawing on issues posted here and community.particle.io. Let me know if you'd like to check out a preview of the spec once we've got a draft together.

Cheers,

-joe