Sorry, I don't know what SCons is. I modified xorp building process a little bit. Each file needed to build a libarary is compiled in two versions (PIC and non-PIC) and SOME library is built in both static and shared form after I add "-rpath /usr/local/xorp/lib" since my platform (LINUX VM on x86) supports shared library.
My initial plan was to build xorp executibles selectively i.e. my new protocol process would be built linking shared libaries and the original xorp processes would be built linking static libaries. But it is not that easy to achieve this. So if one library has a shared version, the shared libary will be linked with each process which depends on it. So some processes are linked with some libaries which are shared but with others which are static. The build is running good. Now I am testing if they are working as before. --- On Thu, 11/12/09, Bruce Simpson <[email protected]> wrote: > From: Bruce Simpson <[email protected]> > Subject: Re: [Xorp-hackers] autotool > To: "Li Zhao" <[email protected]> > Cc: [email protected] > Date: Thursday, November 12, 2009, 7:16 AM > Li Zhao wrote: > > I figured it out. in config/ltmain.sh there are two > Parameters (VERSION, TIMESTAP) > > which control what libtool will be built. in > configure.in the AC_DISABLE_SHARED option was turned on. > > If we comment this out, the PIC code will be > compiled. > > > > Do you see any issues like this with the SCons build? AFAIK > the SCons framework does not use libtool in any way, and > should use the appropriate -fPIC vs -fpic flags for the > target. > > cheers, > BMS > _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
