The DDK is for the CoApp core engine. Rather than take a dependency on MSVCR100.DLL (or any other Visual Studio DLL), we link against the standard C functions in MSVCRT (which ships with every version of Windows).
It means that we’re restricting ourselves to C rather than C++, but it also frees us from having any dependencies not already on the system. G From: Conan Kudo (ニール・ゴンパ) [mailto:ngomp...@gmail.com] Sent: Tuesday, June 08, 2010 2:48 PM To: Garrett Serack Cc: Adam Baxter; coapp-developers@lists.launchpad.net Subject: Re: [Coapp-developers] Building CoApp code! Why do we need the DDKs? Isn't CoApp for applications and libraries, not device drivers? On Tue, Jun 8, 2010 at 7:56 AM, Garrett Serack <garre...@microsoft.com<mailto:garre...@microsoft.com>> wrote: The .NET 4 SDK is installed along with Visual Studio…. So yeah, but there isn’t a separate Windows SDK. G From: Adam Baxter [mailto:volta...@voltagex.org<mailto:volta...@voltagex.org>] Sent: Tuesday, June 08, 2010 2:55 AM To: Garrett Serack Cc: coapp-developers@lists.launchpad.net<mailto:coapp-developers@lists.launchpad.net> Subject: Re: [Coapp-developers] Building CoApp code! The Windows SDK link you provided is the Win 7/.NET 3.5 version. Will we also need the .NET 4 version? On Tue, Jun 8, 2010 at 1:48 PM, Garrett Serack <garre...@microsoft.com<mailto:garre...@microsoft.com>> wrote: 1. Install (to the default path!): - Visual Studio 2010 - Windows DDK (http://bit.ly/95Bl28) - Windows SDK (http://bit.ly/aAKQxp) - Bazaar: http://bit.ly/964shL (contains cli, gui, and tortoise bzr clients) - Putty: http://tinyurl.com/2p6sw4 (SSH Client, contains the PAGEANT tool) 2. Create/Register a SSH public key with Launchpad 3. Run Pageant, load your private key. 4. From the command line: > cd c:\projects (or wherever you want to checkout the code) > bzr branch lp:coapp-solution coapp > cd coapp > cscript Checkout-Projects.js The local.props file contains the location of the DDK (C:\WinDDK\7600.16385.1\) If the path is different, you will need to adjust that value in a text editor. 5. Open up the coapp.sln project in Visual Studio. Ctrl-Shift-B to build Everything builds to the ...\coapp\output\<plat>\<debug|release> \bin directory. (ie: ...\coapp\output\x86\release\bin\CoApp.exe) This builds the engine, the managed toolkits and the CLI. It doesn’t really do anything yet, except for parse the command line & print the help. [Description: Description: fearthecowboy]<http://fearthecowboy.com/> Garrett Serack | Microsoft's Open Source Software Developer | Microsoft Corporation Office:(425)706-7939 email/messenger: garre...@microsoft.com<mailto:garre...@microsoft.com> blog: http://fearthecowboy.com<http://fearthecowboy.com/> twitter: @fearthecowboy<http://twitter.com/fearthecowboy> I don't make the software you use; I just make it better on Windows. _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> Post to : coapp-developers@lists.launchpad.net<mailto:coapp-developers@lists.launchpad.net> Unsubscribe : https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers> More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net<mailto:coapp-developers@lists.launchpad.net> Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
<<inline: image001.gif>>
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
