Sorry, everyone. I hit "Send" too fast before I could remember something else import to my experience.
There were some minor changes discussed in the list about adding an include directive to a few header files. Try referring to http://groups.google.com/group/osg-users/browse_thread/thread/459e4bc93cc6922c/1fe07b41ff8b02de?lnk=gst&q=iterator+build#1fe07b41ff8b02de for the details (subject line in that thread reads "VS 2010 and OSG v2.8.3"). This discusses how the iterator header is required in a few places under the VS2010 build of OSG 2.8.3. Good luck... D.J. On Thu, Mar 17, 2011 at 2:13 PM, D.J. Caldwell <[email protected]>wrote: > Hi, Chris. > > I have been using OSG 2.8.3 built as 64 bit shared libraries with VS2010 > (no SP1) on 64 bit Windows 7 for several weeks now, with no real "problems". > > Specifically with OSG, using CMake 2.8.3, I only had problems with the > INSTALL target; it appears the .lib, .dll, and .exe files weren't where > INSTALL was looking to copy from, so I had to move things manually to where > INSTALL could find them. (There's probably been chatter on this, and I just > missed it). > > I didn't suffer from the Hotfix issue that Qt 2.7.x calls out because I > also use Qt in my app, and I built Qt first (so I got the hotfix). > > I won't go into the performance comments; you guys have pretty much covered > all the bases. > > Hope this helps... > > D.J. > > > On Thu, Mar 17, 2011 at 1:47 PM, Anders Backman <[email protected]> wrote: > >> I second the one about performance. >> I have a 4 Core Machine (8 with HT) with 6GB memory. >> Since I started using VS2010, I feel kidnapped by Microsoft. The >> Intellisense is extremely slow for larger projects. >> VS is an editor, but sometimes it feels like a CAD application, it >> commonly uses 700-800Mb, and it is locks up now and then. >> Reloading a solution with 30-some projects takes forever... >> So its not really a huge leap forward from VS2008, which feels like a >> Ferrari in comparison. >> >> Seems that they have merged the Word team with the VS2010 development >> team... >> VS2010, is more like Microsoft Word, but with a compiler. >> >> For day to day C++ development (not using .NET), its a pain...waiting for >> the circle most of the time. >> But the fonts are nicer :-) >> >> The one and only thing that really sticks out as a positive improvement is >> the performance profiler. Thats really really nice. Although it only works >> for 32bit apps :-( >> >> /A >> >> >> On Thu, Mar 17, 2011 at 6:29 PM, Paul Sherman <[email protected]>wrote: >> >>> Chris, >>> >>> I have not, as of yet, gotten around to building OSG with VS2010SP1, but >>> in general I would say that if you are using VS2010, get the service pack. >>> It fixes quite a few bugs and there are some drastic improvements in >>> performance. The one woefully horrible piece of functionality is "Go To >>> Definition" which is still pretty slow even after the one time, murderously >>> slow database rebuild. I use 3rd party tools instead. Other than that, I >>> think it is a good set of fixes. >>> >>> -Paul >>> >>> >>> On 3/17/2011 10:09 AM, Chuck Seberino wrote: >>> >>>> Chris, >>>> >>>> I haven't been impressed at all with VS2010. The IDE tends to crash >>>> quite a bit - annoying, but not the end of the world. I did have an issue >>>> with 64-bit builds, particularly with Qt-4.7.x. Seems that there were >>>> byte-alignment issues (http://support.microsoft.com/kb/2280741). After >>>> installing the hotfix everything seems OK, at least no problems that I >>>> could >>>> blame on the compiler :). I haven't tried SP1 yet. I even tried looking >>>> for a list of fixes, but it seems that MS doesn't want to publish them. >>>> >>>> So my suggestion - if there is nothing wrong with the current >>>> development setup, don't upgrade. The IDE is slower and buggier than ever. >>>> That being said, it is (finally) generating proper binaries in x64 with >>>> the >>>> hotfix. The last item I forgot to mention is that there are duplicate >>>> symbols between osgDB::fstream and std::fstream that require the >>>> /FORCE:MULTIPLE linker option to work around. Only an issue on 2010 >>>> builds. >>>> >>>> HTH >>>> Chuck >>>> >>>> On Mar 16, 2011, at 7:06 PM, Chris 'Xenon' Hanson wrote: >>>> >>>> VC++2010 SP1 is apparently out now. >>>>> >>>>> >>>>> https://www.microsoft.com/downloads/en/details.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 >>>>> >>>>> >>>>> I have one client who really wants to use OSG on 2010 (64-bit even!) >>>>> and I'm curious >>>>> about people's experiences with stability. Is 2010 generating good >>>>> solid binaries from the >>>>> OSG codebase, or are there still issues that we'll need to see if the >>>>> SP1 fixes? >>>>> >>>>> -- >>>>> Chris 'Xenon' Hanson, omo sanza lettere. [email protected] >>>>> http://www.alphapixel.com/ >>>>> Digital Imaging. OpenGL. Scene Graphs. GIS. GPS. Training. Consulting. >>>>> Contracting. >>>>> "There is no Truth. There is only Perception. To Perceive is to >>>>> Exist." - Xen >>>>> _______________________________________________ >>>>> osg-users mailing list >>>>> [email protected] >>>>> >>>>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >>>>> >>>> _______________________________________________ >>>> osg-users mailing list >>>> [email protected] >>>> >>>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >>>> >>>> >>> _______________________________________________ >>> osg-users mailing list >>> [email protected] >>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >>> >> >> >> >> -- >> __________________________________________ >> Anders Backman, HPC2N >> 90187 Umeå University, Sweden >> [email protected] http://www.hpc2n.umu.se >> Cell: +46-70-392 64 67 >> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> >> >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
