[plt-scheme] Inter-extension dependancies

From: Dmitriy.Zavin at infineon.com (Dmitriy.Zavin at infineon.com)
Date: Sat Oct 23 14:16:39 EDT 2004



 >-----Original Message-----
 >From: plt-scheme-admin at list.cs.brown.edu 
 >[mailto:plt-scheme-admin at list.cs.brown.edu] On Behalf Of Matthew Flatt
 >Sent: Saturday, October 23, 2004 6:55 AM
 >To: Zavin Dmitriy (IFNA COM)
 >Cc: plt-scheme at list.cs.brown.edu
 >Subject: Re: [plt-scheme] Inter-extension dependancies
 >  For list-related administrative tasks:
 >  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
 >At Fri, 22 Oct 2004 09:53:55 -0700, Dmitriy.Zavin at infineon.com wrote:
 >> I have 2 sets of extensions linked as shared libs (A and 
 >B). A uses some
 >> functions from B.
 >> So I (load-extension B) first. When I try to (load-extension A),
 >> mzscheme complains that it cannot find the symbol which was actually
 >> loaded as part of extension B. What gives? Is there any way 
 >to achieve
 >> the above without compiling them both into 1 monolithic extension?
 >Under Unix, MzScheme opens extensions using dl_open() with RTD_GLOBAL.
 >So when you lead extension A, it can't see the exports of extension B.
 >But if you supply extension B when *linking* extension A, then I think
 >it will work the way you want.

Posted on the users mailing list.