
|
[openbeos]
||
[Date Prev]
[06-2004 Date Index]
[Date Next]
||
[Thread Prev]
[06-2004 Thread Index]
[Thread Next]
[openbeos] Re: need help with jam
- From: Jérôme Duval <korli@xxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 5 Jun 2004 23:15:45 +0200
Selon Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>:
>
> I'm not sure, if I understand what you mean by that.
>
I meant using .def files as sources for the static library
> >
> > I now use UserObject rule to have my own extension built.
>
> Please don't. AFAIK `.def' isn't a common extension, so UserObject is not
> the right place.
>
I'm using this now in Jamfiles. Is it a problem ? I don't understand what you
mean by common extension.
> > It seems to work better.
>
> There shouldn't be that many differences. Probably the only one is that you
> use a higher level rule now, which automatically adds grist.
>
Could be right.
> > The big problem i have now is 'mkbuiltins' only
> > outputs in the current directory (which can be anything in current
> > current/src ... ).
> > I didn't find how to go around this (changing current directory makes tool
> > and targets paths wrong).
> >
> > I think I should modify 'mkbuiltins' to have it output somewhere else.
>
> That's probably the most sensible way. But you can also have a look at the
> RelSymlink rule and how it constructs a relative path between two
> directories using SplitPath and FRelPath. Or check out how e.g. the Yacc
> rule is implemented in Jambase (by moving the generated file to the right
> place).
>
I did modify 'mkbuiltins'. The reason is if i don't, it generates files which
can replace existing .c files in the src directory.
I'll commit this ASAP. We will better discuss the best way to do things then.
Thanks,
Jerome
|

|