[ndnSIM] Modifying ndnSIM, compiling/building a single file (or small subset) rather than everything?

John Baugh jpbaugh at umich.edu
Sun May 14 22:22:19 PDT 2017


Spyros,


Thank you for the reply.  It seems much of ndnSIM's output are shared
object files, so I wasn't sure if just the modified file(s) would need to
be rebuilt.

Thanks,

John

On May 14, 2017 8:47 PM, "Spyridon (Spyros) Mastorakis" <
mastorakis at cs.ucla.edu> wrote:

> Hi John,
>
> unfortunately, this is the way that a compiler (gcc/g++, clang, Intel’s
> C/C++ compiler, etc.) and linker work.
>
> When you change a file that is (explicitly or implicitly) included by a
> number of other files, all these files have to recompiled and linked again.
>
> Thanks,
>
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> UCLA
>
> On May 13, 2017, at 11:13 PM, John Baugh <jpbaugh at umich.edu> wrote:
>
> Greetings again ndnSIM friends,
>
> Whenever I use the ./waf command, it compiles essentially all (or nearly
> all) the source code in ndnSIM...  even if I just modify a single file.
>
> Is there any way to get it to only build / compile / link relevant files?
>
> For example, I'm modifying the forwarder.cpp class (Forwarder class.)
>
> Even if I put a simple print out statement as a change, I really should
> only have to recompile this file (I assume it becomes a shared object
> somewhere...)  - but ./waf recompiles and relinks nearly everything.
>
> Ideas?
>
>
> Thanks,
>
> John
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20170515/b09e5066/attachment-0001.html>


More information about the ndnSIM mailing list