I think it would be great to have an automated build process, which tries to create weekly builds.
> Here are some aspects I thought about: > - For which VS versions do we want to provide binaries? for all available > VS releases since 2005, just 2010 and above, or only the newst version, > currently VS2012? > I've been providing back to 2008. I can't run 2005 anymore on my virtual machines. I'd like to provide up to 2013 as soon as it's available. I also intend to provide iOS and Android. > - Do we want to provide only the basic framework toolsets (v80, 90, 100, > 110 120) or also the XP compatible versions like v110_xp and v120_xp? > I don't have any interest in the _xp flavors, but it wouldn't be impossible. > - How should we handle the VS 2012 builds regarding the Compiler bug > (please see below), since every source code need to be checked and > eventually patched? > I don't know. > - What kind of build env has to be used? A Win 7 machine with all required > tools installed and a scripted build process? > I use a Win7 virtual machine, a Linux virtual machine and an OSX virtual machine all controlled by a Linux master controller. > - Which libraries do we want to provide? - I recommend to identify the > most ugly ones and to discuss if they are required. Example: In V7, I used > iconv and gettext, but I dropped it in V8 since it is a nightmare to build > and I forgot all the pitfalls in detail - learning it again would cost me a > day I suppose.. In contrast, all the image format libraries aer compiling > like a charm. > We have to make compromises -- some things are just too difficult to build. For example, I build the DICOM libraries, but the OSG DICOM support tends to break a lot. > From Chris and my experience with the binaries, I suppost it wont be 100% > scriptable ever - I think it will always require monitoring and > administration effort to keep it running. > > What can I contribute: > - Storage up to TB size for hosting files (100 mbit uplink) > I think having a European mirror is a great idea. > - A linux VM if required > - A windows VM if required. But HVM windows is a bit slow in my opinion - > however, it would be a central build machine with access for all involed > participants. > We can use my Windows VM. It seems to perform ok. > - Mailing solution to develop and provide a email notification about new > releases to listeners. > - Knowledge (but time is my bottleneck since it has to be done on my spare > time). > Same here. Knowledge is the key element here. Maybe I can set up a side discussion group to work on this. One of my critical guys is busy until after SIGGraph, so I can't do much until then. -- Chris 'Xenon' Hanson, omo sanza lettere. [email protected] http://www.alphapixel.com/ Training • Consulting • Contracting 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL Digital Imaging • GIS • GPS • osgEarth • Terrain • Telemetry • Cryptography • Digital Audio • LIDAR • Kinect • Embedded • Mobile • iPhone/iPad/iOS • Android @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) 623-PIXL [7495]
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
