[Ns-developers] ns-3-allinone and NSC

Sam Jansen sam.jansen at gmail.com
Fri Jan 9 17:16:03 PST 2009


2009/1/9 Tom Henderson <tomh at tomh.org>

> Gustavo, thanks for implementing allinone.  Are you ready to move it to
> ns-3-allinone (from gjc/ns-3-allinone)?
>
> Gustavo Carneiro wrote:
>
>> Looking more closely at ns-3-allinone, which was kind of dormant, I
>> realize
>> there is an issue left unsolved regarding integration with NSC.
>>
>> Currently NSC is built from within the ns-3 wscript file.  I propose to
>> build NSC only from within the allinone build script, exclusively.
>>
>> In addition, currently the ns-3 wscript creates symbolic links to the NSC
>> libXXX.so files into the toplevel ns-3 build dir.  I think this was meant
>> to
>> allow dlopen in NscTcpL4Protocol::SetNscLibrary to be able to find the
>> lib.
>> But looking at the dlopen man page it says that LD_LIBRARY_PATH can also
>> be
>> used to specify a search path for dlopen.  In that case, I would like to
>> remove the symbolic links hacks and instead add the relevant NSC subdirs
>> to
>> the LD_LIBRARY_PATH for waf check/--run/--regression/--shell.  That should
>> take care of the problem more elegantly.
>>
>> Any objections?
>>
>>
Sounds good to me.


>
> None from me.
>
> - Tom
>


More information about the Ns-developers mailing list