[openbeos] Re: bison and other build issues
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 26 Jun 2004 23:59:03 +0200
On 2004-06-26 at 19:17:13 [+0200], Jérôme Duval wrote:
>
> 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.
>
> So is it a good solution ? Or could it be better to go the other way, ie
> renaming .cpp.h to .hpp and fix all our references to a .cpp.h file to a
> .hpp
> file ?
Mmh, as long as both versions of bison work with our build system and with
the files to be compiled, it doesn't really matter. In doubt embracing the
new version is probably best for the future.
> 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 ?
AFAIK the *Install* rules were originally intended to install things in the
host system. So File is probably more appropriate for the time being. At any
rate this part of the build system will be reworked in the not so distant
future.
> 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 wonder, where are those files located in BeOS?
CU, Ingo
Other related posts:
