[openbeos] Re: haiku svn tree
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 27 Feb 2007 22:27:59 +0100
On 2007-02-27 at 21:56:42 [+0100], Urias McCullough <umccullough@xxxxxxxxx>
wrote:
> On 2/27/07, Curtis Wanner <katisu@xxxxxxxxxxx> wrote:
> >
> >
> > Ingo Weinhold wrote:
> > >Rest assured as soon as building things greater than a "Hello World"
> > becomes
> > >viable we'll see that we make it an option to include build tools in the
> > >image. But at the moment it doesn't help anyone, if we include the tools,
> > >people run them, and hit KDL pretty soon. Our kernel devs are aware of
> > those
> > >issues (and others) and will fix them. Please bear with us... :-)
> >
> > If I'm not mistaken, I believe umccullough already is working on this
> > exact thing. Of course he is waiting for the kernel issues to be cleared
> > up
> > before submitting anything.
> >
> > Curtis
> >
> > Slight correction:
>
> I'm not doing it with jam though - I just have a "late-image-script" that
> executes when the image is almost done and copies a lot of stuff to the
> image (Firefox, Vision, etc.) - I'm simply copying an R5 version of
> GCC/binutils currently, but it would be nice if these were compilable with
> Haiku as the target as well and could be generated as part of the image.
Copying the R5 tools is OK for the time being. I also don't think we'll ever
integrate the binutils/GCC build into the image creation process. We'll
probably provide a script to build the tools for Haiku and add an option to
our build system to copy the respective files to the image.
> Also, I've found that the Haiku public POSIX headers don't seem to be
> complete-enough to build R5-targetted stuff quite yet (jam for example) from
> within Haiku - so I've been using the R5 headers from my BeOS Max edition
> instead.
Please don't forget to file a bug report, if you encounter those. :-)
CU, Ingo
Other related posts:
