
|
[openbeosnetteam]
||
[Date Prev]
[11-2002 Date Index]
[Date Next]
||
[Thread Prev]
[11-2002 Thread Index]
[Thread Next]
[openbeosnetteam] Re: One small step for net team, but... but onesmall step forward?
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Wed, 13 Nov 2002 18:21:53 +0100 (MET)
On Wed, 13 Nov 2002, Philippe Houdoin wrote:
> Small changes on the net team front.
>
> RECENT CHANGES DONE:
[...]
> PENDING CHANGES:
>
> a) make the userland stack debug platform run ASAP.
>
> My main focus. So that we could see internal code running/crashing,
> learn how it (expect to) works, understand it, and then make
> it really works as expected. Or dump it and rewrite it.
> Hopefully, only partially.
>
> As a net_server is already there, and build, it's mostly
> a matter of building network modules as userland add-ons too, now.
> From same source code.
> What I'm trying at home is, for each module, to symlink all source code
> into corresponding directory under src/tests/add-ons/net_server at
> build time (RelSymlink jam rule?), then build with the "Addon" rule
> a userland add-on, without forgotten to link it against our net_server,
> which exported the module API and some other KernelExport.h stuff expected
> by our network modules code.
>
> Unfortunnatly, currently:
> - I couldn't manage to (re)create the symlink at build time
> *before* running the "Addon" rule on them.
> Please, Jamfile guru(s), help me! :-)
I don't think it is a good idea to generate anything in the `src' subtree.
But I suppose, you simply want to make jam find the respective source
files. This can be done by adding their directory to the search paths for
source files, like:
SEARCH_SOURCE += [ FDirName $(OBOS_TOP) src foo bar ] ;
CU, Ingo
|

|