[Ns-bugs] [Bug 434] build system revisions

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=434





--- Comment #6 from Gustavo J. A. M. Carneiro <gjcarneiro at gmail.com>  2008-12-16 13:28:13 EDT ---
(In reply to comment #5)
> I would suggest to do skip pybindgen and print out a error message like we have
> now ("PybindGen missing and could not be retrieved)"  However, it would be nice
> to allow the user to manually move over pybindgen installation from somewhere
> else and have ./waf configure in the ns-3-dev directory later find it
> successfully.  
> 
> The rationale is, users may be running simulations on machines where they do
> not have privileges to install bzr.  But maybe they can download it on another
> machine and move it over.

With those requirements I think we just need to make download.py skip pybindgen
with a warning but otherwise proceed and ignore it.  Then when ./build.py is
run, the option --with-pybindgen=../pybindgen is passed, even if ../pybindgen
isn't actually there.  Finally, ns-3's waf configure will use the
--with-pybindgen option and test to see if pybindgen is there or not, and
disable python bindings if not found.

To summarize, ./build.py is stateless, i.e. it does not care whether or how
pybindgen was obtained.  At the moment, the only state saved between
download.py and build.py is the name of the branch we are working on, stored in
the BRANCH file.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.