[haiku] Re: Idea for getting attention and possibly more ported software
- From: "Thomas Mueller" <mueller6723@xxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Sat, 15 Aug 2015 02:50:17 +0000
On 14.08.2015 11:56, Thomas Mueller wrote:
But still, even with the resulting toolchain, the source-tree
infrastructure looks to be geared for specific host operating systems, and
using NetBSD, even if intrinsically capable, runs into one of these booby
traps.
Certain APIs and paths are different even on similar OSs. Since we don't use
the GNU autotools or something else that does the OS specific checks and/or
performs feature-based checks, we need to do some OS specific handling in our
build system. Grepping for linux I find only a handful of such checks in the
Jam part of the build system. There are probably a few more in build tools
code, but that should be about it to support a yet unsupported OS.
Since you mentioned xattr support a few times. Building with xattrs, while
recommended, is not required.
CU, Ingo
Natural inclination is to use xattr when the file system is supposed to support
it.
Building from NetBSD, there was a problem with a missing endian.h due to the
macros in the source tree.
It would be good if one could attempt to cross-build haiku not only from
NetBSD, but also other OS that might have the proper software: Bitrig (forked
from OpenBSD), maybe Minix3, DragonFlyBSD, and possibly other up-and-coming OS.
That would of course be at user's own risk, but I think that is generally true
in open-source software.
DragonFlyBSD seems not compatible with my system; I currently only have NetBSD
and FreeBSD to cross-build from.
I can tweak configure, and jam/BuildSetup, but can't find all the other needles
in the haystack.
There is also the concern about updating with "git pull" when part of the tree
has been modified by user.
Tom
Other related posts:
