<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body> <div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">On 12 Jun 2018, at 0:20, Allan Odgaard wrote:</p> <blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">For the dependency cycle that ninja “did not detect”, I do actually have some (non-committed) code that improves on dependency detection which would have caught this, but it’s not just a simple “source depends on header” issue, but about link dependencies, which can be a little tricky, as you can’t assume that including a header file means you necessarily wants to link with the library to which the header belongs, for example some sources may include oak/debug.h but do not want to automatically link with my oak debug library, unless in debug mode, and iirc that was the primary reason I didn’t yet push the code that automatically figures out link dependencies.</p> </blockquote><p dir="auto">For anyone interested in this stuff, I have updated the build process: <a href="https://github.com/textmate/textmate/commit/412e6798ca206b15cdc8f86a1387835a3f4f82e7" style="color:#3983C4">https://github.com/textmate/textmate/commit/412e6798ca206b15cdc8f86a1387835a3f4f82e7</a></p> <p dir="auto">This should address the issues some have experienced during initial full build where a header is unavailable because that target has not yet been built yet.</p> <p dir="auto">More details in the commit message.</p> </div> </div> </body> </html>