[openbeosnetteam] Re: Open-beos-cvs digest, Vol 1 #1752 - 7 msgs

On Wed, 16 Jul 2003 11:51:24 GMT "Philippe Houdoin" <
philippe.houdoin@xxxxxxx> wrote:
> 
> > From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxxxxxxxx>
> > Date: Sun, 13 Jul 2003 08:23:47 -0700
> > Subject: [Open-beos-cvs]CVS: current Jamrules,1.81,1.82
> > 
> > Update of /cvsroot/open-beos/current
> > In directory sc8-pr-cvs1:/tmp/cvs-serv9750
> > 
> > Modified Files:
> >     Jamrules 
> > Log Message:
> > LinkSharedOSLibs now strips the grist <nogrist> off targets. 
> > Otherwise one couldn't use target names that don't have a grist 
> > (like 
> > applications, against which their add-ons need to link).
> 
> Hum? What about linking against pseudo _APP_ target?
> I'm looking after Jamifying my current/src/tests/kits/net/new_stack 
> BeIDE projects files.
> 
> The stack net modules add-ons needs to be linked against the network 
> userland stack host application to find the kernel emulated functions 
> (get_module() & co)...
> I tried to write a jamfile, specifying the _APP_ in the *linklib* 
> last 
> argument of AddOn rule, but it didn't works as it seems to link 
> against 
> _KERNEL_ too, something I really don't want!
> 
> Another issue I've is how to create, for each addon to build, the 
> local 
> _APP_ symlink pointing at the "net_server" userland stack host 
> application.
> How can I add this creation to each module add-on jamfiles?

AFAIK, the symlinks are only a work-around for PEF. ELF supports a 
shared object name (settable via `-soname') which is intended to do the 
same trick. It currently isn't set properly for the applications we 
build (will fix this), but it should be of interest only when you 
rename the app you originally linked against, anyway, or when your 
application loads add-ons originally written for another application.

Well, that's at least how I believe it works. Please correct me, if I'm 
wrong.

CU, Ingo

Other related posts: