coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Well, that was the idea...

I suppose that typical config.h files might differ between the two, but other than that, I can't think of a case where the header files would be different.


But, it's not a *requirement*, just a lack-of-caffeine-induced-delirium-idea...

G

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: Friday, April 16, 2010 9:00 AM
To: William A. Rowe Jr.
Cc: coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Bundling x64 and x86 binaries in the same library package?

On Fri, Apr 16, 2010 at 5:38 PM, William A. Rowe Jr. <wmrowe@xxxxxxxxx> wrote:
> On 4/16/2010 9:59 AM, Garrett Serack wrote:
>> For Library packages (static and dynamic) I’m wondering if we 
>> shouldn’t just put both variants in the same package—still installing 
>> the WinSxS binaries appropriately, and putting the .lib files in the correct spot.
>>
>> This would actually conserve disk-space, since the x64 and x86 
>> versions of the packages could share include & doc directories, and 
>> we could use symlinks for that.
>
> Don't go there.
>
> This is the source of most OS/X pain; the fact that Apple has stacked 
> the single unified binaries.  Many open source include files simply 
> don't and can't cope with this, and many patches that would enable 
> this on OS/X are rejected out of hand because the model is broken with 
> respect to particular open source projects :)

Putting both variants in one package doesn't mean both variants should use the same include files, does it?

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