[ndnSIM] ndn-cxx or ndnSIM/ndn-cxx?

[Alex Afanasyev]

Hi Anil,

I may have misread your original question.  You don't need to install ndn-cxx bundled with ndnSIM.  You just need to configure ns-3/ndnSIM as you would normally do.  All necessary detection for dependencies derived from ndn-cxx is done as part of normal configure and build procedure.

So. The steps, as per ndnsim.net are just:
cd <ns-3-folder>
./waf configure ...any-configure-flags-you're-using...
./waf


> On Dec 3, 2015, at 10:24 AM, Anil Jangam <anilj.mailing at gmail.com> wrote:
> 
> Thanks Alex for your comments.
> 
> So in this regard, is it proposed to remove the ndnSIM's dependency on ndn-cxx since configure fails if no ndn-cxx libraries are found. So your last statement isn't completely true OR it would justify the above proposed removal.
> 
> /anil.
> 
> On Wed, Dec 2, 2015 at 3:17 PM, Alex Afanasyev <aa at cs.ucla.edu <mailto:aa at cs.ucla.edu>> wrote:
> 
>> On Dec 1, 2015, at 7:50 PM, Anil Jangam <anilj.mailing at gmail.com <mailto:anilj.mailing at gmail.com>> wrote:
>> 
>> Thanks Spyros for the reply.
>> 
>> Curious to know what is the difference between the ndn-cxx (its main source) and the one which is part of ndnSIM? This is the question from my below post, which I believe is not answered yet.
>> 
>> When we configure/compile ndnSIM one of the prerequisite is ndn-cxx otherwise configure script fails. So my question is: do we install ndn-cxx from its main source or do we install it from the version which is part of ndnSIM source?
>> 
>> When I install ndn-cxx it from the main source its compile goes through fine. However, when I try to compile and install ndn-cxx from the ndnSIM sources, I hit the error I reported in this thread.
>> 
>> Can you please comment?
> 
> Hi Anil,
> 
> ndnSIM bundles (as a submodule) a specific version of ndn-cxx.  This is to ensure that ndnSIM can be compiled even there are changes of the mainstream library.  The actual bundled code is almost exactly the same as the mainstream, there is a very minor change and it is just not the most recent version.
> 
> Same applies to the bundled NFD source code.  It is a fixed version of NFD codebase with a few minor modifications.
> 
> Installation of a stand-alone ndn-cxx/NFD will not have any effect on ndnSIM 2.1+.
> 
> ---
> Alex
> 
>> 
>> /anil.
>> 
>> 
>> On Mon, Nov 30, 2015 at 9:53 AM, Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>> Hi Anil,
>> 
>> there was another thread about this issue. You may want to take a look at it:
>> 
>> http://www.lists.cs.ucla.edu/pipermail/ndnsim/2015-November/002208.html <http://www.lists.cs.ucla.edu/pipermail/ndnsim/2015-November/002208.html>
>> 
>> Hope that this helps!
>> 
>> Spyridon (Spyros) Mastorakis
>> Personal Website: http://cs.ucla.edu/~mastorakis/ <http://cs.ucla.edu/~mastorakis/>
>> Internet Research Laboratory
>> Computer Science Department
>> UCLA
>> 
>> 
>> 
>> 
>>> On Nov 30, 2015, at 9:44 AM, Anil Jangam <anilj.mailing at gmail.com <mailto:anilj.mailing at gmail.com>> wrote:
>>> 
>>> Hi,
>>> 
>>> Before we compile ndnSIM 2.1, do we have to install the ndn-cxx from it sources or should we be installing it from the sources provided under ndnSIM, which I think is slightly modified version? If I just do not install it, ndnSIM configure obviously gives configure error (Checking for 'libndn-cxx'                                 : not found).
>>> 
>>> When I try to configure and install ndn-cxx which is included in ndnSIM, I hit the following error.
>>> 
>>> Checking for 'sqlite3'                                : yes
>>>  hecking Crypto++ lib                                 : 563
>>> Checking if CryptoPP library works                    : no
>>> Checking if CryptoPP library works                    : no
>>> CryptoPP is present, but is not usable
>>> (complete log in /home/anilj1/sandbox/ndnSIM/ns-3/src/ndnSIM/ndn-cxx/build/config.log)
>>> 
>>> As can be seen I have already compiled and installed the latest version (5.6.3) of the cryptopp from its source. (Got the reference from here: http://redmine.named-data.net/issues/1700 <http://redmine.named-data.net/issues/1700>) but it is not helping.
>>> 
>>> This redmine change is about an year old. However is there any change made in recent past to ndnSIM in this regard?
>>> 
>>> /anil.
>> 
>> _______________________________________________
>> ndnSIM mailing list
>> ndnSIM at lists.cs.ucla.edu <mailto:ndnSIM at lists.cs.ucla.edu>
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim <http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20151203/7e110e10/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20151203/7e110e10/attachment.bin>