Hi Gerrit, The reason for using VS2003 is that we have an existing VS2003 project and want to integrate OpenSG 2. Probably it could be transfered to 2005 but I would prefer to keep it running on 2003. Another reason for sticking at 2003 is that - afaik - the current version of OpenSG 2.0 for VS2005 is only compilable in debug mode. But thats a minor reason because I think this will be resolved in the future.
One more issue regarding QT: In OpenSG 1.x QT was supported with the WindowQT lib. Are there any plans in the near future to provide OpenSG 2 with that package as well or is there an exisiting solution available? Best Regards Marcus Marcus Hoffmann Dipl. Ing. für Medientechnologie Abt. Echtzeitlösungen für Simulation und Visual Analytics Fraunhofer Institut für Graphische Datenverarbeitung Phone: +49 (0)6151 155 - 639 Mail: [EMAIL PROTECTED] >-----Ursprüngliche Nachricht----- >Von: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Im Auftrag >von Gerrit Voss >Gesendet: Montag, 20. August 2007 15:28 >An: [email protected] >Betreff: Re: [Opensg-users] OpenSG 2.0 Build Errors with VS .Net 2003 > > >Hi, > >On Mon, 2007-08-20 at 13:27 +0200, Marcus Hoffmann wrote: >> Hi all, >> >> I tried to compile OpenSG 2.0 (current source from SVN) using Scons, >> Boost >> 1.33.1 etc. on Windows XP (32-bit) with the VS .Net 2003 Compiler. >> Unfortunately I got several build errors, that seem to point to a >> problem in OSGFieldContainerMFields. >> Attached the build-error print outs. >> >> Any suggestions how to solve the problem? ;-) > >Actually two, it really might be a problem, I will have a look >tomorrow in office if the windows build has a problem. This >can happen as windows is not the primary development platform >so once in a while the windows build is not working properly. >Especially these days where the head is changing fast. > >But it also could be that we hit one of the notorious VS2003 >compiler problems. > >Is there any particular reason why you need to use VS2003 and not >VS2005 ? > >2.x is mainly developed and verified against VS2005 and we >intend to drop VS2003 support. > >Actually, in reality we practically already dropped it because >none of the 2.x developers builds against VS2003 anymore. > >Just a question to everyone : > >Is there really still the need to support VS2003 ? > >kind regards > gerrit > > > > > >--------------------------------------------------------------- >---------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> >http://get.splunk.com/ _______________________________________________ >Opensg-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/opensg-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
