coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Yes, we'd like to have a tiny bootstrap DLL that gets us the engine DLL, and the bootstrap can ship in every MSI.

The bootstrap will be VERY small ( < 2048 bytes ).

The engine DLL we'd like to keep as small as possible too.

Garrett Serack | Open Source Software Developer | Microsoft Corporation 
I don't make the software you use; I make the software you use better on Windows.


-----Original Message-----
From: coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx [mailto:coapp-developers-bounces+garretts=microsoft.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Olaf van der Spek
Sent: Tuesday, May 18, 2010 3:06 AM
To: Ted Bullock
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Code?

On Tue, May 18, 2010 at 4:41 AM, Ted Bullock <tbullock@xxxxxxxxxxx> wrote:
> On Mon, May 17, 2010 at 8:25 PM, Jonathan Ben-Joseph <jbenjos@xxxxxxxxx> wrote:
>> This is because C truly is the least common denominator when it comes 
>> to language binding, almost every mainstream language can call 
>> directly into C shared libraries without much of any boilerplate code 
>> (see P/Invoke in .NET or ctypes in Python for example).
>
> Yes this is precisely why.  Also, we want to be able to bundle it into 
> packages so that if someone chooses to install a package outside of 
> the standard tools (administrative installs for example), CoApp will 
> be there and be able to get all the dependencies.

Wasn't the idea to include a tiny DLL inside each MSI that is able to download the engine on demand?
That tiny DLL is not the same as the entire engine.

Olaf

_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~coapp-developers
More help   : https://help.launchpad.net/ListHelp