[openbeosstorage] Re: Volume.h?
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 7 May 2002 16:22:32 +0200 (MET DST)
On Mon, 6 May 2002, Tyler Dauwalder wrote:
> > BTW, I'm a bit surprised, that it compiles. It seems, that the Be headers
> > are in the compilers include path. I think, that should be fixed,
> > otherwise some day strange thing might happen...
>
> Yeah, I was bit concerned myself when I was first messing with Jam.
> However, it always seems to use our headers first (when they exist), so I
> haven't worried about it too much since (mostly because it worked and I had
> other things to do other than figure out how to yank the standard dirs from
> the search paths).
>
> Also, we need to be binary and source compatible anyway, so it shouldn't
> really make a difference one way or the other, right? Up until you had to
> split compilation for the test programs due to BSymLink, we were linking in
> the R5 Storage Kit without incident to stuff compiled with our headers.
Yep, but I rather would like to make this compatibility stuff more
explicit. E.g. we might want to cross link the test app, i.e. the objects
compiled with our headers with libbe.so and vice versa).
Anyway, this might not have a great priority right now...
CU, Ingo
Other related posts:
