[openbeos] Re: bison and other build issues
- From: "Andrew Bachmann" <shatty@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 27 Jun 2004 01:17:50 -0700 PDT
Jérôme Duval <korli@xxxxxxxx> wrote:
> Hello Haiku people,
>
> i was facing several issues when building. I thought i should ask before
> doing
> anything.
>
> 1/
>
> The version 1.875 of bison in our cvs is behaving differently comparing to
> the
> R5 one. In fact, produced headers are no longer called parser.cpp.h but
> parser.hpp. At the moment, i can fix this in our Bison actions to rename the
> file parser.hpp to parser.cpp.h and all goes well.
I think this is okay.
> 2/
>
> To copy a simple file to our distro directory, i personally use a File rule
> call. I should add a Clean rule call so that it behaves correctly. I know
> some
> of you use a OBOSInstall rule call.
>
> Is there a common way of doing this task ?
Use File to copy inside our tree (under common). Use OBOSInstall to copy
to outside of our tree. Note that the default build should *never* copy to
outside of our tree. Doing so can break someone's beos install and even has
been known to lead people to think they're networking died for a week. :-)
> 3/
>
> Some of the bin utilities i checked in are usually configured to find their
> system data files in a directory /usr/local/share.
> What should we do ?
> - /share and /boot/beos/share (need to add a /share link to the root ...)
> - /etc and /boot/beos/etc (not a common place but why not)
> - another directory ?
I have no /boot/beos/share but I do have both /boot/home/config/etc and
/boot/home/config/share, which would lead me to believe that we should
have a /boot/beos/share separate from /boot/beos/etc.
Andrew
> Jérôme
>
>
Other related posts:
