Software development kit: Difference between revisions

Revision as of 20:43, 12 May 2006

Revision as of 12:06, 16 May 2006

Line 3:

It may be something as simple as an [[application programming interface]] in the form of some files to interface to a particular [[programming language]], or include sophisticated hardware to communicate with a certain [[embedded system]]. Common [[Software development tools|tools]] include debugging aids such as an [[Integrated development environment|IDE]] and other [[Utility program|utilities]]. SDKs also frequently include sample code and supporting technical notes or other supporting documentation to help clarify points from the primary reference material.

A software engineer typically receives the SDK from the target system developer. Often times, the SDK can be downloaded directly via the [[Internet]]. Many SDKs are provided for free to encourage developers to use the system or language. Sometimes this is used as a marketing tool. For example, ''Foo Products'' might provide the ''Widget SDK'' for free to encourage people to use it. In turn, more people will be encouraged to buy more of their widgets since they can program them for free.

SDKs may have attached [[license]]s that make them unsuitable for building software intended to be developed under an incompatible license. For example a proprietary SDK will likely be incompatible with [[Free software]] development. And a [[GPL]] licensed SDK will ''likely'' be incompatible with proprietary software development. [[LGPL]] SDKs are typically safe for proprietary development.