Forum Discussion
DLL vs SDK
Would it be more convenient to put build the SDK into a DLL for windows based programming that can be called from programs rather than, integrating the SDK into every single Software title. The SDK...
"lazydodo" wrote:
1) Dump the C++ SDK, we all make mistakes, it's how we learn, no big deal.
2) Define a STRONG C API (Strong meaning, once the SDK supports a certain function it's signature or behavior can NEVER EVER change)
3) Deliver this as a DLL on windows and as a shared library on other platforms. (Forcing developers to statically link your code is bad, and you should feel bad)
4) Give developers the right to redistribute this dll with their application.
5) Optional: Release the source for this dll to developers to help them with debugging.
Strongly agree. However, there should be some distinction made... the above best describes a thin hardware abstraction. Minimal code and API to access the hardware.
On top of this can be a featureful SDK, written in C++ for Windows if desired. It seems to me that a larger SDK is really a platform to quickly make demos or start working with Oculus hardware. A core API (C conventions and cross platform) would be easier to fit into an existing engine or application, and access from other languages. And having it as dll/so, as mentioned, lets all software (from various SDKs to applications) benefit from bugfixes and upgrades.