Re: [Coapp-developers] Building CoApp code!

[Rivera, Rafael]

Ahhhhhhhhhh my ears are burning. /splashes gasoline CoApp can definitely be used to deploy (both user-mode and kernel-mode) device drivers. There's a blueprint for this package type on the wiki, but hasn't been fleshed out yet (http://coapp.org/Blueprints/Package_Blueprint/Role%3a_Device_Driver). Why the DDK for a CoApp compile, though? Well, there are some dependencies that only live in the DDK. For example, for CoApp-Trace, we need access to the Windows Tracing Preprocessor (tracewpp.exe). We haven't figured out if we can redistribute the component yet -- Garrett? /rafael On 6/8/2010 5:48 PM, Conan Kudo (ニール・ゴンパ) wrote: 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> 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] Sent: Tuesday, June 08, 2010 2:55 AM To: Garrett Serack Cc: 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> 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.     Garrett Serack | Microsoft's Open Source Software Developer | Microsoft Corporation Office:(425)706-7939                                       email/messenger: garre...@microsoft.com blog: http://fearthecowboy.com                                      twitter: @fearthecowboy I don't make the software you use; I just make it better on Windows.     _______________________________________________ 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   _______________________________________________ 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 _______________________________________________ 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

_______________________________________________
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