Dear Chris, Luc, Laurens 

you are right, the question is what we _could_ do ;)

Thanks for your offer, maybe we can set up such an automated build system.
What in detail does the software you call Conductor?

On my side, I built the package very sporadic, usually triggered by new 
libraries I require, new versions of single libraries or due to compiler 
updates.
In the source package I documented the build process quite extensive, in V8a 
more details than in V7 (which Laurens used to build up his system afaik).


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?
- 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?
- 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? 
- What kind of build env has to be used? A Win 7 machine with all required 
tools installed and a scripted build process?
- 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.

>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.

Your thoughts?


What can I contribute:
- Storage up to TB size for hosting files (100 mbit uplink)
- 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.
- 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).


Thank you!

Cheers,
Torben

------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=55284#55284





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

Reply via email to