<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi build2 users,<br>
<br>
I am currently trying to compile some objective-C source files
using build2 for MacOS builds of SFML (see <a
moz-do-not-send="true"
href="https://github.com/build2-packaging/sfml/blob/master/sfml-window/src/buildfile#L72"
class="moz-txt-link-freetext">https://github.com/build2-packaging/sfml/blob/master/sfml-window/src/buildfile#L72</a>).<br>
I basically copied the adhoc-recipe from the GLFW package (see <a
moz-do-not-send="true"
href="https://github.com/build2-packaging/glfw/blob/master/glfw/src/buildfile#L24"
class="moz-txt-link-freetext">https://github.com/build2-packaging/glfw/blob/master/glfw/src/buildfile#L24</a>)<br>
<br>
It seems to work or at least do something meaningful. However,
during the build the compilation of some objective-c files fails,
because the compiler cannot find certain header files (see <a
moz-do-not-send="true"
href="https://github.com/build2-packaging/sfml/runs/6297094892#step:5:568"
class="moz-txt-link-freetext">https://github.com/build2-packaging/sfml/runs/6297094892#step:5:568</a>).<br>
The missing header files lie in the sfml-system package, which is
imported at the top of the buildfile </font><font face="monospace"><font
face="monospace"><a
href="https://github.com/build2-packaging/sfml/blob/master/sfml-window/src/buildfile#L72">https://github.com/build2-packaging/sfml/blob/master/sfml-window/src/buildfile</a>.
Building</font></font><font face="monospace"><font
face="monospace"><font face="monospace"><font face="monospace">
C++ sources, which also need these headers, works. </font></font><br>
It seems like the exported include paths of the sfml-system
dependency are not propagated to the adhoc recipe. </font></font><font
face="monospace"><font face="monospace"><font face="monospace"><font
face="monospace">I tried adding the intf_libs explicitly to
the adhoc recipe but that did not help.<br>
<br>
</font></font>Sadly I have no idea how the include paths are
internally managed by build2, specifically how and when exported
include paths are added to the compiler flags of certain
targets.<br>
<br>
Could anybody give me a hint on how to resolve this or what's
basically going on internally? Currently I ran out of ideas what
I could try out next.<br>
<br>
Regards<br>
Fabian<br>
</font></font>
</body>
</html>