JSC builds these test programs unconditionally: testmasm testb3 testair testapi But they're not exposed or installed in release mode. Our other tests all depend on developer mode, so let's be consistent. I noticed these recently because having installed binaries that depend on internal symbols of JSC makes it harder to change how we link JSC, though hopefully we'll never have to bother with that again anytime soon....
Created attachment 331350 [details] Patch
These are unit tests, and it might make sense to build unit tests in non-developer builds, e.g. packagers could use them for smoke checking...
You'd think, but our test scripts simply don't support running from tarball builds, and there's not much point in having a bunch of standalone test binaries in the builddir. That might be worth changing, of course.
Comment on attachment 331350 [details] Patch Clearing flags on attachment: 331350 Committed r226971: <https://trac.webkit.org/changeset/226971>
All reviewed patches have been landed. Closing bug.
<rdar://problem/36543176>