<div dir="ltr">I’m trying to create a build system with clear separation between the layers of my projects. My problem is that I can’t find an easy way to include headers from a dependency library.<div><br></div><div>(Longer explanation…)<br>
<div><br></div><div>My work is laid out like this:</div><div><br></div><div><div>engine/</div><div>______engine.scm</div><div>______engine#.scm</div></div><div><div>project1/</div><div>______ios-game1/</div><div>______android-game1/</div>
<div><div>______game1/</div><div>____________game1.scm</div><div>____________game1#.scm</div></div></div><div>project2/</div><div>______ios-game2/</div><div>______android-game2/</div><div><div>______game2/</div><div>____________game2.scm</div>
<div>____________game2#.scm</div></div><div><br></div><div>I want to build the engine project into libengine.a, and each of my games into their own library, i.e. libgame1.a and libgame2.a.</div><div>Then to make an iOS build for game1, for example, I link in libengine.a and libgame1.a</div>
<div><br></div><div>My problem is that, because I’m using namespaces, I need to include the #.scm header files from my engine into the game. Something like…</div><div><br></div><div>; game1.scm</div><div><div>(##include “engine/engine#.scm”)</div>
</div><div><br></div><div>However, the ##include directive only searches relative to the current file, so my build of libgame1.a fails. There doesn’t seem to be any way to specify an include path to look in.</div></div><div>
<br></div><div>Is there a possible solution? Or, if not, does it make sense to build one into Gambit? A gsc flag would work great for my purposes.</div><div><br></div><div>Thanks,</div><div>Axis</div></div>