[openbeos] Re: BIG change in progress

this is targeted to all the developes currently working on OpenBeOS.

I wanted to inform you that I'm making a large change to the whole
OpenBeOS source tree. It will touch nearly every kit, and also the kernel.

Thanks. Michael, this is just the thing a dev only list would be good for. =)

What I'm doing is this:

- I'm adding the libnet to the build system
- I'm fixing the network headers

OK, fine.

- I'm making the build independed of the header files from /boot/develop/headers
- I'm making the kernel build use BeOS headers where applicable.
- I'm adding header files for the kits when they are required for the build.

OK, but why? As header files become available in our tree, they won't be pulled in from /boot/develop/headers anyway, so I don't understand the need for this.

- I'm merging ktypes.h sys/types.h OS.h SupportDefs.h

Why? Will those headers still be available and simply refer to the new "master" header?

- I'm adding posix include files as needed, taken from FreeBSD or OpenBSD.
- I'm fixing current and added posix header files to make them BeOS compatible

Fine.

- I'm correcting all build problems that result from this changes

I should think so. ;)

- This means, I'm probably going to change "int" into "status_t" or into "int32" where required.

Is there a technical reason for doing this?

- If needed, I'm looking how to create a libroot.so replacement, but this is 
will come later.
- As source for C++ headers im useing the header-src.tgz file from 
ftp.be.com/public
  it was made open source by Be a while ago (during R3), and updated with each 
release.
- I'm not going to use the posix header from that file, since they are LGPL. I 
don't want to
  mix them with the kernel
- I know and understand the difference between MIT, GPL and LGPL licenses.

My big question is "why the heck are you doing this?" ;P What problem does this solve or goal does it achieve? I'm not trying to be antagonistic, I just want to understand your motivation -- if for no other reason than to help me avoid making a necessary task more difficult for you. =)

e


This change will take a few days, and I'm not going to commit the change to CVS tree until it's compiling again.

After it is committed, all you should need to do to get up to date is
cvs co current

If you have been working on files, cvs should in most cases automatically merge 
the
files with your changed.

Of cause, if you have valid reasons to stop me from doing all this changes, you 
can post
here. I'm open for any suggestions. But please don't suggest to do it later.

I think we had some time ago some people responsible for posix and libroot. If you have something prepared/done, please let me know.

I'm trying to do this changes as smothly as possible.

Marcus






Other related posts: