[haiku-development] Re: [PATCH] libroot improvements

  • From: Dustin Howett <alaricx@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Thu, 26 Feb 2009 22:36:08 -0500

On Thu, Feb 26, 2009 at 10:02 PM, Artur Wyszynski <aljen-mlists@xxxxxxx> wrote:
> Hey,
> Don't worry, it won't break binary compatibility, because it's ported &
> enabled only for gcc4 build, gcc2 is still using old
> libroot+glibc&friends.
>
> Current status:
> * old libroot is moved from src/system/libroot to
> src/system/libroot/compatibility and gcc2 builds it from there
> * new libroot is now in src/system/libroot
> * headers/posix is moved to headers/compatibility/beos/posix and they are
> used in buildtools scripts to instruct gcc2
> where headers are and in build/jam/HeadersRules where they are when building
> Haiku
> * new posix headers are in headers/posix
>

My only concern would be having to maintain multiple versions (legacy
and new-fangled), as the gcc2 and gcc4 builds are built from pretty
much the same code.
Also, breaking binary compatibility with gcc4-built binaries isn't the
best, but it might have to be accepted.

It sounds great, though!
Don't take my word as law, I'm not a developer :), but very nice work
and a big +1.

-- Dustin L. Howett

Other related posts: