[About going from Makefiles to configure]
> Let's see the goods first, shall we :)
Stupid of me to promise a patch when I'm just about to make a trip for
the next couple of days. :^/
I'll see if I can get it ready over the weekend.
> By the way, Morten, aren't you also in the Coin development team?
> What's going on there?
I'm talking with management about us supporting SGI's effort with
Inventor, and it looks like it will be ok for them. I guess what will
happen now (with 90% probability, have to get it "OK"'ed first):
* we start contributing the good parts of Coin to SGI's
Inventor (fix up the horrible build-system, provide fixes
(or at least reports) for a long list of Inventor bugs we've
seen, and there're certain features (and probably also
optimizations) present in Coin not available in Inventor)
* libCoin gets re-released under LGPL
* our GUI-binding libraries libSoQt, libSoXt, libSoGtk,
libSoWin, libSoBe, etc will _probably_ get re-licensed under
LGPL
* we'll keep the Coin sourcecode around in low maintenance
mode (kill bugs etc). This will be done to have an
"unencumbered" Inventor implementation around for
"proprietary licensing" in case anyone can't work with the
restrictions of LGPL for a certain project.
* we re-design our www.coin3d.org website to focus on
- Systems in Motion as a consulting/services company
handling large & complex visualization projects,
extensions to SGI Inventor, etc etc
- GUI-binding libraries (SoQt, SoGtk, etc)
- language-binding libraries (like the Scheme
Ivy-binding), example code, maybe even tutorials
etc, in short: lots of various support stuff not
present on the oss.sgi.com-site
We[1] want to make an effort to be a major player in the Inventor
community.
Regards,
Morten
[1] That's "we" as in "the Coin developers at SIM" -- I still have to
get this through management, but they seem very positive so far.
|