Although this is actually deprecated in 10.10, new APIs are available in 10.9 and it will make addressing deprecation warnings when upgrading to 10.10 easier.
We no longer build frameworks as standalone targets but instead link it all together, which also means resources from “frameworks” will end up in the main bundle.
Currently the new build file generator does not create test targets and changing linker settings in frameworks is not inherited by the main target (since there is no naive way to “merge” framework specific linker settings).
For custom library dependencies (capnp, kj, and libressl) we specify them via `LIBS` using `/path/to/libfoo.a` so that the root target will inherit these dependencies and using the absolute path ensures that we get the static (rather than dynamic) version.
Although we only use the headers in a single framework, we generally do not use per-framework include paths and furthermore, by having it as a “global” setting, it’s much easier to change how TextMate is built (w/o having to analyzer compiler flags like `-I`).
This should be a quick check, only done after entering a valid license, and the UI feedback depends on the result, so little was gained from doing it as a background check.
After switching to a version of libressl compiled from source I am seeing crashes from BIO_new_mem_buf and PEM_read_bio_RSA_PUBKEY.
Also minor code touchups, no functional change.
Apple deprecated `openssl` in 10.7 and the headers are now removed in 10.11. Since we use some low level functions that are not provided in Apple's crypto frameworks, we now require are own version.
The creator code is obsolete and doesn’t serve much of a purpose, as we already mention TextMate in the service name.
When updating a keychain item we leave out kSecAttrLabel and kSecAttrComment, which may fix issue #1029.
The new (non-deprecated) API no longer allows us to target a specific keychain for add, remove, and lookup.
This wasn’t used by TextMate itself but was extremely useful for writing tests against the API (using temporary keychains).
There is currently no way to add a TextMate (1.x) license to the key chain, but those who used TextMate r9147 or earlier should have one stored already.
