| 24 Oct 2025 |
 emily | which has such annotations | 01:41:13 |
 Randy Eckenrode | Most things that want to use private libpcap symbols re-declare the function definition. Only Apple bothers to use the private headers. | 01:41:26 |
| Randy Eckenrode | It’s a static library that isn’t installed. | 01:41:57 |
| Randy Eckenrode | I did that to avoid having the same lists of files for multiple executables. | 01:42:45 |
| Randy Eckenrode | I do export the libdsc_extractor dylib though. | 01:43:14 |
| emily | fwiw, the repos that mention SPI_AVAILABLE are: libpthread, libmalloc, xnu, mDNSResponder, dyld, Security, WebKit, libdispatch, WebCore, configd, libplatform, libpcap, IOKitUser, Libinfo, eap8021x, libffi | 01:44:33 |
| emily | I think that the only time we'll be using headers with SPI_* stuff and not just wanting them to be elided (because we're building stuff ourselves and so it's available invariant of runtime OS version) is really just the xnu headers | 01:45:13 |
| emily | funny header name: SecProtocolRestrictedOptionsGoAwayIfNotApprovedForEPSKsPriv.h | 01:45:28 |
 samasaur | any idea why qt can't find Network.framework | 01:47:16 |
| emily | uhh | 01:48:19 |
| emily | did it -framework it? | 01:48:21 |
| samasaur | https://github.com/qt/qtbase/blob/e902f8ad85a3a36b266f5e96bf3dc1ddad9fa18e/cmake/QtFrameworkHelpers.cmake#L42 | 01:48:34 |
| samasaur | can't find it at configure time, not build time | 01:48:45 |
| emily | have you looked at our Qt patches | 01:49:31 |
| samasaur | oh dear | 01:49:42 |
| samasaur | no | 01:49:43 |
| emily | they're not as bad as they used to be | 01:49:58 |
| emily | find_library(${cache_var_name} "${framework_name}")
if(${cache_var_name} AND ${cache_var_name} MATCHES ".framework$")
set(${out_var} "-framework ${framework_name}" PARENT_SCOPE)
else()
set(${out_var} "${out_var}-NOTFOUND" PARENT_SCOPE)
endif()
| 01:50:09 |
| emily | hmm I hope I didn't break CMake's ability to find frameworks | 01:50:14 |
| samasaur | so the thing that's odd is that it appears able to find CFNetwork but not Network | 01:51:07 |
| samasaur | despite everything appearing to be "found" the same way | 01:51:15 |
| Randy Eckenrode | It would probably be worth making the symbols always be available for libpcap and libffi, but most things that want to use them will redeclare them anyway. | 01:51:29 |
| emily | libpcap and libffi will already get them always available | 01:51:43 |
| emily | because the public SDK causes SPI_AVAILABLE(…) to expand to nothing | 01:51:51 |
| emily | correctly in this case | 01:51:56 |
| emily | the only time we ever don't want that behaviour is basically when we're hacking up xnu headers, I think | 01:52:39 |
| Randy Eckenrode | I don’t know that the private headers with those declarations are even included in the packages. We build both with their configure scripts. | 01:52:42 |
| emily | which is why I suggested the best approach is probably to replace SPI_ → API_ in xnu headers and have an empty AvailabilityInternalPrivate.h (or drop their includes of it) | 01:53:12 |
| emily | since that will ensure the right behaviour there without screwing up the more common uses of SPI_* in the source releases | 01:53:28 |
| emily | (where we do want them to be elided) | 01:53:33 |
