Content deleted Content added
m Signing comment by 173.9.45.237 - "" |
→API articles: new section |
||
Line 91:
:The API is built right into Windows, so if you have Windows, you already got it. But to have compilers you need, you need the headers and associated tools that describe the API to the compiler. This is available as a part of the [[Windows SDK]] ( [http://www.microsoft.com/downloads/info.aspx?na=47&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&u=details.aspx%3ffamilyid%3dE6E1C3DF-A74F-4207-8586-711EBE331CDC%26displaylang%3den] ). You can use that with the [[Visual C++]] line of compilers and [[Microsoft Visual Studio]] IDE (including VC++ Express [http://www.microsoft.com/express/download/]). [http://blogs.msdn.com/windowssdk/archive/2008/02/22/using-visual-c-2008-express-with-the-windows-sdk-detailed-version.aspx This blog post] explains how to use Windows SDK with VC++ Express 2008. The Windows SDK, however, won't allow you to use MinGW or GCC compilers. Use the MinGW Windows runtime/api for an analogous functionality. --[[User:Soumyasch|soum]] <sup>[[User talk:Soumyasch|talk]]</sup> 12:29, 7 May 2008 (UTC)
== API articles ==
These individual API/dll subsections need articles of their own, and should also be organized in part according to implementation (in/outside of kernel, "nt exec", some service, system library, etc). anyone have any ideas for how to do this, or votive to start an article?
[[Special:Contributions/68.110.212.162|68.110.212.162]] ([[User talk:68.110.212.162|talk]]) 06:17, 18 February 2010 (UTC) not an ip -- not signed in
| |||