Subject: [Boost-build] <framework> issue
From: Phillip Seaver (phil_at_[hidden])
Date: 2016-04-05 13:31:20
I'm building on OS X, and one of my libraries specifies the frameworks
it uses with <framework>. That library is used by another library,
which is in turn used by the executable. It fails to link because the
framework feature is not propagated, so no "-framework xxx" options get
added to the executable link.
On the Windows side, I use <library> to add the system libraries (which
I have as searched libraries in my Jamroot.jam) and that propagates up
like I want.
If I turn off the check that prevents features from being "free" and
"propagated", it still doesn't work.
It's easier if it is "free" since otherwise you have to look through the
SDK directories and find all the frameworks. Also, it allows you to
specify frameworks by path (if you have your own, e.g.). I haven't
tested that yet, though.
I'm not sure what the best way forward is. At the moment, I'm adding
the appropriate "<framework>" settings to the "exe" rule, just so I can
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk