Linked by Thom Holwerda on Fri 20th Aug 2010 21:40 UTC, submitted by koki
BeOS & Derivatives This summer, too, the Haikuproject is part of the Google Summer of Code event. One of the more interesting projects is the Services Kit (draft document!) by Christophe "Shusui" Huriaux, which is an API to facilitate the creation of native web-enabled programs using standard web protocols and data exchange mechanisms.
Thread beginning with comment 437662
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Forward thinking
by umccullough on Sat 21st Aug 2010 03:32 UTC in reply to "RE: Forward thinking"
umccullough
Member since:
2006-01-26

"They also use GPL code wherever necessary, thereby eliminating the need to re-invent the wheel.


That's not entirely accurate, that license is pretty much a last resort for us. Generally most code in Haiku tries to work from sources with friendlier licenses such as BSD/MIT or LGPL. The only major GPLed piece is gcc, most everything else is disabled in the default build (you have to explicitly configure your build to include GPL-based code).
"

Indeed. And several GPL pieces have even been replaced in favor of BSD-licensed code (such as several network drivers, etc.)

It will be nice to release Haiku from glibc eventually as well ;)

Reply Parent Score: 3

RE[3]: Forward thinking
by ZeuZ on Sat 21st Aug 2010 04:43 in reply to "RE[2]: Forward thinking"
ZeuZ Member since:
2010-08-02

Not that I might work on it, because my aptitude in this subject is still limited, but what about calling it hlibc? ;)

Reply Parent Score: 1

RE[3]: Forward thinking
by kaiwai on Sat 21st Aug 2010 10:18 in reply to "RE[2]: Forward thinking"
kaiwai Member since:
2005-07-06

Indeed. And several GPL pieces have even been replaced in favor of BSD-licensed code (such as several network drivers, etc.)

It will be nice to release Haiku from glibc eventually as well ;)


I was under the impression that Haiku was still using the FreeBSD libc except that there were a couple of functions that were changed so that they operate like the glibc implementation rather than the FreeBSD implementation.

Reply Parent Score: 2

RE[4]: Forward thinking
by umccullough on Sat 21st Aug 2010 15:11 in reply to "RE[3]: Forward thinking"
umccullough Member since:
2006-01-26

I was under the impression that Haiku was still using the FreeBSD libc except that there were a couple of functions that were changed so that they operate like the glibc implementation rather than the FreeBSD implementation.


I believe they started off with the BSD libc, but switched to glibc for compatibility reasons (since BeOS had used glibc for its "libroot" support).

http://dev.haiku-os.org/browser/haiku/trunk/src/system/libroot/posi...

Recent discussion suggests that glibc may still be retained only for the BeOS compatibility (i.e. a gcc2-compiled set of libs will still remain optionally-installed for BeOS compatibility) while a non-GPL libc replacement will be grafted in moving forward.

Reply Parent Score: 3