Hi all, hi Robert,

> for Windows we could generate an .msi installer

If CMake can do that, I'll open a bottle of Champagne! :) That would be great 
to directly generate an installer for each platform...

But to end up the discussion, I'll say, until we got a real installer (which is 
the best solution), that:
- Tweaking the CMake script to add special DLLs in the tar.gz is a bad idea. 
DLLs should thus not be added in the archive.
- There should be a note and a link on the dowload page (and maybe in a README 
as J-S suggested). I suggest Robert (or anyone having write access to this 
page) to add, after the "Windows Visual Studio 8 packages" the following wiki 
text:
" - Requires the MSVC 2005 SP1 redistributables for your platform 
([http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647
 x86], 
[http://www.microsoft.com/downloads/details.aspx?FamilyID=eb4ebe2d-33c0-4a47-9dd4-b9a6d7bd44da
 x64] or 
[http://www.microsoft.com/downloads/details.aspx?FamilyID=747aad7c-5d6b-4432-8186-85df93dd51a9
 IA64]"

And the same for 2008 packages 
(http://www.microsoft.com/downloads/details.aspx?FamilyID=a5c84275-3b97-4ab7-a40d-3802b2af5fc2
 (x86), 
http://www.microsoft.com/downloads/details.aspx?FamilyID=ba9257ca-337f-4b40-8c14-157cfdffee4e
 (x64), 
http://www.microsoft.com/downloads/details.aspx?FamilyID=dcc211e6-ab82-41d6-8dec-c79937393fe8
 (IA64)).

Is that okay for everyone?

Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/


Le Tue, 17 Feb 2009 18:27:35 +0100, Jean-Sébastien Guay 
<[email protected]> a écrit:

> Hi Philip,
>
> I'll defer to others (Robert) for the decision, but I don't agree with
> your point of view. I think the redist is as close to a set of system
> DLLs as it can be without being on the actual Windows installation CD,
> so I think there's no point in putting copies of it everywhere on your
> system.
>
>> Personally I would trade the whopping 1.6 MB this would take up for the 
>> assurance that the binaries will work on all machines.
>
> 1.6MB per project, per instance of the binaries, per... That's the
> point, they're meant to be system-wide, not all over the system.
>
>> Of course if you want an end-user's first experience running osgviewer to 
>> view some model they found online to be a cryptic error message, then by all 
>> means leave things the way they are.
>
> OSG is not an end-user app. It's a library which you'll use to develop
> other apps. If you downloaded the binary packages, it's either because
> you wanted to evaluate it for possible use in your project, or you want
> to use it in an existing project (perhaps in place of a previous version).
>
>> Unfortunately, not every first time user of OSG is going to have MSVC 
>> installed or the runtime libraries installed.
>
> A note in the readme should suffice. We can even have a special readme
> that we only include in the Windows binary packages. As I said, if they
> want to do almost anything else on the machine they'll need the redist,
> so whether OSG is the reason they install it or anything else makes
> little difference. In all likelyhood they'll have Visual Studio
> installed anyways... So I think we're arguing about a minority of users.
>
> What we might consider doing would be, instead of generating tarballs,
> for Windows we could generate an .msi installer that would install the
> runtime correctly if needed (like most apps do). We could even generate
> both, and make it clear that if you download the tarball you need the
> runtime installed already.
>
>> There is no disadvantage to including the runtime DLLs aside from an extra 4 
>> files and 1.6MB of space used.  I think this is really a no brainer.
>
> There is no disadvantage to not including the runtime DLLs. Period. And
> we don't pollute the system with copies of DLLs that will be installed
> to the system directories by some other app sooner or later.
>
> Honestly, if there was a way for me to have one version of libpng,
> libjpeg, etc. like on a Linux box, installed system-wide, I'd do that.
> Unfortunately, it doesn't work like that on Windows. But at least we can
> keep the dependencies we need to ship to a minimum.
>
> J-S

_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to