Re: [osg-users] problem with Windows debug binaries?
Hi Philip, CMake supports integration with NSIS. Not sure if there is support for MSI yet. Wix looks like a promising candidate. Do NSIS provide the feature we want (install the MSVC redistribuables if needed)? Anyway, putting the links on the download page could always be useful I think. Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Sukender, Is that okay for everyone? Looks good to me. But putting all this text on the download page is too much. Instead, I've created a new page: http://www.openscenegraph.org/projects/osg/wiki/Downloads/VisualStudioBinaries Robert, can you please add a link to that page next to the Windows Visual Studio 8 packages item in the 2.8 section on the Downloads page? Call it (requirements) or some such: [http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8 Windows Visual Studio 8] packages ([wiki:Downloads/VisualStudioBinaries requirements]) Thanks, J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi J-S, This is a good solution, and I've update the download pages with the requirements link. Robert. On Wed, Feb 18, 2009 at 1:49 PM, Jean-Sébastien Guay jean-sebastien.g...@cm-labs.com wrote: Hi Sukender, Is that okay for everyone? Looks good to me. But putting all this text on the download page is too much. Instead, I've created a new page: http://www.openscenegraph.org/projects/osg/wiki/Downloads/VisualStudioBinaries Robert, can you please add a link to that page next to the Windows Visual Studio 8 packages item in the 2.8 section on the Downloads page? Call it (requirements) or some such: [http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8 Windows Visual Studio 8] packages ([wiki:Downloads/VisualStudioBinaries requirements]) Thanks, J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Robert, This is a good solution, and I've update the download pages with the requirements link. Great, thanks. J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
On Mon, Feb 16, 2009 at 11:48 AM, Norman Vine n...@cape.com wrote: Cory Riddell writes: A couple of notes: 1. I don't run as administrator all the time (it still amazes me how many Windows users always operate as an admin) 2. I untarred with cygwin's tar. Perhaps that does something funky with the permissions? My guess is you don't have the sp1 runtime http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14- 984d-389c36f85647displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-%0A984d-389c36f85647displaylang=en Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the bin folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. *C:\Program Files\Microsoft Visual Studio 8\VC\Redist\x86\Microsoft.VC80.CRT *\* See: http://www.codeproject.com/KB/cpp/vcredists_x86.aspx The debug prebuilts can't have the debug runtime included with them for legal reasons. Also, adding the following should cause the Visual Studio 7, 7.1, 8 or 9 runtime libraries to be copied to the bin folder when someone runs the INSTALL target in Visual Studio. I can't test this at the moment since I don't own VS at home, only VS Express. This should make packaging up distributions of the OSG easier: INCLUDE(InstallRequiredSystemLibraries.cmake OPTIONAL) -- Philip Lowman ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Philip, Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the bin folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. IMHO, installing the MSVC runtime crap is preferable to copying the same DLLs in every release zip for every version of OSG (and potentially every other project we work on...) and therefore having potentially tens if not hundreds of copies of the same files on your system. Installing the redist ensures you have one copy (the right one) and it's accessible to all programs. IMHO, the redist is as much a system DLL as anything that ships with Windows, and will probably be installed on any machine that runs any programs at all, really. Lots of installers for other programs will install it automatically, so I think it's a non-issue. If you don't have it installed, just install it. You will eventually anyways, and it's quick and painless. As for the debug redist, the debug binaries are only useful to developers who presumably will need to have Visual Studio installed to do anything useful with them, so it's another non-issue. Also, adding the following should cause the Visual Studio 7, 7.1, 8 or 9 runtime libraries to be copied to the bin folder when someone runs the INSTALL target in Visual Studio. I can't test this at the moment since I don't own VS at home, only VS Express. This should make packaging up distributions of the OSG easier: INCLUDE(InstallRequiredSystemLibraries.cmake OPTIONAL) I don't think this is a good idea either for the same reasons. J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Agreed that users should install the MSVC redistribuable (or directly MSVC)... or switch to Linux/Mac if they get bored with MS-specific ;) Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Tue, 17 Feb 2009 15:31:37 +0100, Jean-Sébastien Guay jean-sebastien.g...@cm-labs.com a écrit: Hi Philip, Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the bin folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. IMHO, installing the MSVC runtime crap is preferable to copying the same DLLs in every release zip for every version of OSG (and potentially every other project we work on...) and therefore having potentially tens if not hundreds of copies of the same files on your system. Installing the redist ensures you have one copy (the right one) and it's accessible to all programs. IMHO, the redist is as much a system DLL as anything that ships with Windows, and will probably be installed on any machine that runs any programs at all, really. Lots of installers for other programs will install it automatically, so I think it's a non-issue. If you don't have it installed, just install it. You will eventually anyways, and it's quick and painless. As for the debug redist, the debug binaries are only useful to developers who presumably will need to have Visual Studio installed to do anything useful with them, so it's another non-issue. Also, adding the following should cause the Visual Studio 7, 7.1, 8 or 9 runtime libraries to be copied to the bin folder when someone runs the INSTALL target in Visual Studio. I can't test this at the moment since I don't own VS at home, only VS Express. This should make packaging up distributions of the OSG easier: INCLUDE(InstallRequiredSystemLibraries.cmake OPTIONAL) I don't think this is a good idea either for the same reasons. J-S ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
. Original Message ... On Tue, 17 Feb 2009 09:31:37 -0500 Jean-Sébastien Guay jean-sebastien.g...@cm-labs.com wrote: Hi Philip, Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the bin folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. IMHO, installing the MSVC runtime crap is preferable to copying the same DLLs in every release zip for every version of OSG (and potentially every other project we work on...) and therefore having potentially tens if not hundreds of copies of the same files on your system. Installing the redist ensures you have one copy (the right one) and it's accessible to all programs. Personally I would trade the whopping 1.6 MB this would take up for the assurance that the binaries will work on all machines. 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. Unfortunately, not every first time user of OSG is going to have MSVC installed or the runtime libraries installed. Yes I agree this sucks. Unfortunately the SxS runtime libraries do not come with Windows. 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. -- Philip Lowman ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
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 -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Do end users download and install OSG? What on earth do they do with it? I believe the intent of the binary packages is to provide a shortcut for developers on Windows to get OSG and the dependencies. If that's the case, then it wouldn't make any sense to include the MSVC. The official distribution is the source tarball, no? cory Philip Lowman wrote: . Original Message ... On Tue, 17 Feb 2009 09:31:37 -0500 "Jean-Sbastien Guay" jean-sebastien.g...@cm-labs.com wrote: Hi Philip, Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the "bin" folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. IMHO, installing the "MSVC runtime crap" is preferable to copying the same DLLs in every release zip for every version of OSG (and potentially every other project we work on...) and therefore having potentially tens if not hundreds of copies of the same files on your system. Installing the redist ensures you have one copy (the right one) and it's accessible to all programs. Personally I would trade the whopping 1.6 MB this would take up for the assurance that the binaries will work on all machines. 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. Unfortunately, not every first time user of OSG is going to have MSVC installed or the runtime libraries installed. Yes I agree this sucks. Unfortunately the SxS runtime libraries do not come with Windows. 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. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Cory Riddell ha scritto: Do end users download and install OSG? What on earth do they do with it? I believe the intent of the binary packages is to provide a shortcut for developers on Windows to get OSG and the dependencies. If that's the case, then it wouldn't make any sense to include the MSVC. The official distribution is the source tarball, no? If you are a developer and want to test OSG on different hardware platforms, then you need something that run with minimum hassle: Think of build an usb pen and ask some colleague of yours to run that specific OSG example and see if it works ok on his (possibly old) pc I have been in this situation quite often. I came up with a folder that include the OSG install + osg data + a run.bat that set up OSG_FILE_PATH (it woul really be nice if there was a way to define a default path) It seems to me that, for testing purposes, the inclusion of system dll would be good, at least as a default off option. I silently had to patch osg CMakeFile to do exactly what Philip suggested but did not dare to ask for inclusion ...I know windows only hack are not exactly welcome. If you have to build apps that deploy as binaries in platform that you do not control (as it happen to me), it could be handy to have a reference osg installation to test the deployed platform against, as it happens that there are bugs related to bad OpenGL drivers. So the need to test with official OSG examples (test) I also think that OSG could benefit from extensive run time testing, on different HW platform and drivers, possibly published as a dashboard, as CDash already support an other sw like VTK do. In that usage pattern, asking for a runtime installation that requires Admin privilege to just save some bytes seems incorrect. Just my 0.2 Euros Luigi cory Philip Lowman wrote: . Original Message ... On Tue, 17 Feb 2009 09:31:37 -0500 Jean-Sébastien Guay jean-sebastien.g...@cm-labs.com wrote: Hi Philip, Yeah, those ZIP releases of the OSG 2.8.0 prebuilts should really have the following files placed in the bin folder so they work out-of-the-box on Windows 2000, Windows XP, or Windows Vista without anyone having to install the MSVC runtime crap. IMHO, installing the MSVC runtime crap is preferable to copying the same DLLs in every release zip for every version of OSG (and potentially every other project we work on...) and therefore having potentially tens if not hundreds of copies of the same files on your system. Installing the redist ensures you have one copy (the right one) and it's accessible to all programs. Personally I would trade the whopping 1.6 MB this would take up for the assurance that the binaries will work on all machines. 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. Unfortunately, not every first time user of OSG is going to have MSVC installed or the runtime libraries installed. Yes I agree this sucks. Unfortunately the SxS runtime libraries do not come with Windows. 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. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi all, I think I'll bow out of this discussion, we're not going forward at all and instead concentrating on relatively uncommon use cases. I think the big picture is the case where the binaries are used either to evaluate OSG for an upcoming project or to use in an existing project. In those cases, the machine will have the runtime already. OSG is not an end-user app, so the task of making installation and running easy on a bare machine is up to the app developer / packager, not to OSG itself. If one of you disagrees with this, you can submit a change to do it some other way, and see what Robert thinks. I think all possible opinions have been voiced so if someone actually wants to change things, be my guest, but let's stop just talking about it and running in circles... J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Luigi Calori wrote: If you are a developer and want to test OSG on different hardware platforms, then you need something that run with minimum hassle This might be a dumb question, but if you are really looking for minimal hassle, why not just statically link everything? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
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 jean-sebastien.g...@cm-labs.com 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 osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
One reason for not statically linking for many 3rd party libs this would break their licensing terms Gordon __ Gordon Tomlinson Product Manager 3D Email : gtomlinson @ overwatch.textron.com __ (C): (+1) 571-265-2612 (W): (+1) 703-437-7651 Self defence is not a function of learning tricks but is a function of how quickly and intensely one can arouse one's instinct for survival - Master Tambo Tetsura -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Cory Riddell Sent: Tuesday, February 17, 2009 1:41 PM To: OpenSceneGraph Users Subject: Re: [osg-users] problem with Windows debug binaries? Luigi Calori wrote: If you are a developer and want to test OSG on different hardware platforms, then you need something that run with minimum hassle This might be a dumb question, but if you are really looking for minimal hassle, why not just statically link everything? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or g ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
On Tue, Feb 17, 2009 at 2:25 PM, Sukender suky0...@free.fr wrote: 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... CMake supports integration with NSIS. Not sure if there is support for MSI yet. Wix looks like a promising candidate. 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-389c36f85647x86], [ http://www.microsoft.com/downloads/details.aspx?FamilyID=eb4ebe2d-33c0-4a47-9dd4-b9a6d7bd44dax64] or [ http://www.microsoft.com/downloads/details.aspx?FamilyID=747aad7c-5d6b-4432-8186-85df93dd51a9IA64]; 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? No arguments here. Until an installer is once again available for casual end-users just linking the URLs you provided seems reasonable to me. -- Philip Lowman ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
[osg-users] problem with Windows debug binaries?
I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Cory, I built these binaries. Do you have the SP1? If the problem is still ther, I'll may recompile entirely (who knows?)... Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Mon, 16 Feb 2009 17:18:36 +0100, Cory Riddell c...@codeware.com a écrit: I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Do you have SP1 installed for VS __ Gordon Tomlinson gor...@gordontomlinson.com IM: gordon3db...@3dscenegraph.com www.vis-sim.com www.gordontomlinson.com __ -Original Message- From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Cory Riddell Sent: Monday, February 16, 2009 11:19 AM To: OpenSceneGraph Users Subject: [osg-users] problem with Windows debug binaries? I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/b inaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Yes, I have SP1. I just noticed that none of the dll's have the execute bit set. My cacls knowledge isn't good enough to know exactly what it is that should be set. It's easy to just grant everyone full control (and it does fix the problem), but I suspect that isn't the correct solution. Cory Sukender wrote: Hi Cory, I built these binaries. Do you have the SP1? If the problem is still ther, I'll may recompile entirely (who knows?)... Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Mon, 16 Feb 2009 17:18:36 +0100, Cory Riddell c...@codeware.com a crit: I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
A couple of notes: 1. I don't run as administrator all the time (it still amazes me how many Windows users always operate as an admin) 2. I untarred with cygwin's tar. Perhaps that does something funky with the permissions? Cory Sukender wrote: Hi Cory, I built these binaries. Do you have the SP1? If the problem is still ther, I'll may recompile entirely (who knows?)... Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Mon, 16 Feb 2009 17:18:36 +0100, Cory Riddell c...@codeware.com a crit: I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Cory, I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I just downloaded all the binaries and unzipped them all to the same directory, and I can run osgversion and osgviewer fine (without any other OSG binaries on my PATH). You don't mention if you have SP1 installed on your installation of VC8. That could well be the problem. You need to have either the VC 2005 SP1 redist or VC 2005 SP1 itself for binaries built with VC 2005 SP1 to run. J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Hi Cory, 2. I untarred with cygwin's tar. Perhaps that does something funky with the permissions? Perhaps... Can you try with another tool? For example 7-zip, which is F/OSS. J-S -- __ Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com http://www.cm-labs.com/ http://whitestar02.webhop.org/ ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Cory Riddell writes: A couple of notes: 1. I don't run as administrator all the time (it still amazes me how many Windows users always operate as an admin) 2. I untarred with cygwin's tar. Perhaps that does something funky with the permissions? My guess is you don't have the sp1 runtime http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14- 984d-389c36f85647displaylang=en HTH Norman Cory Sukender wrote: Hi Cory, I built these binaries. Do you have the SP1? If the problem is still ther, I'll may recompile entirely (who knows?)... Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ Le Mon, 16 Feb 2009 17:18:36 +0100, Cory Riddell c...@codeware.com mailto:c...@codeware.com a écrit: I downloaded the debug and release binaries from http://www.openscenegraph.org/downloads/stable_releases/OpenSc eneGraph-2.8/binaries/Windows/VisualStudio8/. When I try to run any of the exe's, I get a message that says: The application failed to initialize properly (0xc0022). Click on OK to terminate the application. I've seen this before and it has either been a permissions problem or a CRT version mismatch problem. I'm running Visual Studio 2005 which (AFAIK) is generally called version 8, so it shouldn't be a version problem. If I use runas to run osgversion.exe as administrator, I get the same error, so it shouldn't be a privileges problem. So now I really don't know what it could be. Up until today, I've always been running exe's that I compiled myself. This is the first time I've run OSG from a prebuilt binary. Is anybody else having this problem? Any troubleshooting suggestions? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce negraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce negraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
Jean-Sébastien Guay wrote: Hi Cory, 2. I untarred with cygwin's tar. Perhaps that does something funky with the permissions? Perhaps... Can you try with another tool? For example 7-zip, which is F/OSS. Wow- when I untar with 7-zip I get different results than when I untar with cygwin (the file permissions are different). Cygwin gives me exe files with the execute bit set, but none of the dlls have that bit set. 7-zip just gives everyone full control. After searching through the 7-zip forums, it seems that it doesn't support maintaining ACL's. Just out of curiousity, what tool was used to create the tarballs? Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] problem with Windows debug binaries?
I just did a little experiment with 7-Zip and ACL's. I created a file and gave it weird privileges. I tar'd it with cygwin. When I untar with cygwin, the ACL for the file is restored correctly. When I untar with 7-Zip, the ACL has been replaced with one that grants full access to everyone. Likewise, if I tar with 7-Zip, it trashes the ACL for the file (in the archive). It doesn't matter what I use to extract with. The privileges information has been lost. 7-Zip might be a wonderful compression tool, but I don't think much of it's archiving capabilities. I would not recommend it. Cory ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
