[Ns-developers] Proposed examples directory hierarchy

[craigdo@ee.washington.edu]

[ ... ]

> > If you --disable-examples none of the examples are built, 
> none of the
> > examples are tested in test.py, and regression testing 
> won't run (since it
> > depends on the examples).
> 
> How about, instead of a configure time option, a build option 
> that does 
> not try to link examples?   Building the examples is not the typical 
> recurring delay, it is linking them.

I'm afraid I don't understand this comment.  If you don't build the
examples, you don't compile the source code and you don't link with
anything.

> It seems that "./waf" and "./waf build" are functionally the 
> same now-- 
> could we, for instance, make "./waf build" not try to link 
> all examples?

I don't have a big problem with adding a flag to exclude the examples (and
maybe one for samples) since the change is quite small.  The deeper this
goes, the more problem I have, though.  We are talking about a change the
day before code freeze now.

> It would then be nice if there were an easy test.py option 
> that avoided 
> examples, including their linking, such as "test.py -i" (e.g. for 
> internal, or pick your favorite option argument) that was 
> equivalent to 
> "test.py -c unit -c bvt -c system".  So, for instance, this would 
> support a workflow such as "edit file in src/, ./waf build, ./test.py 
> -i" (or even have test.py figure out what needs to be built) 
> that avoids 
> linking and testing examples at each development step.

I really don't understand your comments.  If you "./waf configure
--disable-examples" you get exactly this behavior.  The examples aren't
built (or linked) and test.py doesn't run them.

What am I missing?

Anyway, if it turns out not straightforward and obvious, we should just mark
this "P3 Enhancement" and move on.

-- Craig