Pick up codingstd.txt in dist; point interested waf users to build-waf.txt in the development branch
--- a/SConstruct Fri May 18 10:27:42 2007 -0700
+++ b/SConstruct Fri May 18 11:13:57 2007 -0700
@@ -12,6 +12,7 @@
ns3.add_extra_dist ('doc/architecture.pdf')
ns3.add_extra_dist ('doc/contributing.txt')
ns3.add_extra_dist ('doc/build.txt')
+ns3.add_extra_dist ('doc/codingstd.txt')
ns3.add_extra_dist ('doc/mercurial.txt')
ns3.add_extra_dist ('README')
ns3.add_extra_dist ('RELEASE_NOTES')
--- a/doc/build.txt Fri May 18 10:27:42 2007 -0700
+++ b/doc/build.txt Fri May 18 11:13:57 2007 -0700
@@ -16,8 +16,9 @@
the right libraries. This saves you the pain of having to
setup environment variables to point to the right libraries.
-(Note: An experimental, alternative build system is described
-in build-waf.txt)
+(Note: An alternative build system (Waf) is being
+evaluated in the development branch of ns-3-dev on our server
+only (i.e., not in the release tarballs)-- see doc/build-waf.txt)
1) Options
----------