[Ns-developers] Python Bindings for optional ns-3 features

[Raj Bhattacharjea]

On Fri, Mar 20, 2009 at 1:35 PM, Gustavo Carneiro <gjcarneiro at gmail.com> wrote:
>
> OK, maybe this is a confusion with terminology.  There three stages in
> creating bindings:
>
> 1. "scanning": waf --python-scan uses pybindgen+pygccxml+gccxml to scan
> header files and generate the files bindings/python/ns3_module_*.py
>
> 2. "generation": during build, the bindings/python/ns3_module_*.py are read
> and files build/<variant>/bindings/python/ns3_module_*.cc are generated
>
> 3. "compiling": the build/<variant>/bindings/python/ns3_module_*.cc are
> compile into a .so file
>
> Right now, and for a long time, the result of 1 is shipped in tarballs (and
> mercurial repos).  But not the "generated" .cc files; those were never
> shipped.
>
> When generating the .cc files, the bindings generated scripts already take
> into account which features are enabled or disabled.  Of course for new
> added features some python code to do this disabling of bindings for
> disabled features needs to be added.  See bindings/python/ns3modulegen.py.
>

Mathieu, does anything need to be disabled like this for the XML config store?

-- 
Raj Bhattacharjea
Georgia Institute of Technology
School of Electrical and Computer Engineering
Ph.D. Candidate
Systems Analyst
404.894.2955