Add .linkedFramework

[brentleyjones]

No description provided.

[erikdoe]

Can you provide a bit more context here?

It's been a long time but as far as I remember OCMock doesn't have a strict dependency on XCTest. If it's there at runtime it'll be used, but if it's not there, that's okay, too. There were good reasons for this approach. I wish I had documented them.

As far as I can tell, you're change would force linking of XCTest. Why would you do this in OCMock? If you want the extra functionality, you can always link XCTest from your test target and OCMock will discover it.

[brentleyjones]

Unless OCM_DISABLE_XCTEST_FEATURES is defined, there is a hard dependency on XCTest. I needed to add this to allow creating a dynamic framework for OCMock.

I'm open to different ways to support this, but without this change linking into a dynamic framework fails, because of the use of XCTest without OCM_DISABLE_XCTEST_FEATURES defined (which is the case for the SwiftPM target). Could create two targets, one with and one without this defined?