Ahh 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_Drive
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
free
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 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
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 C
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 wrote:
> 1. Install (to the default path!):
>
> - Visual Studio 2010
>
> - Windows DDK (http://bit.ly/95Bl28)
>
> -
5 matches
Mail list logo
