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

[Raj Bhattacharjea]

On Fri, Mar 20, 2009 at 1:26 PM,  <craigdo at ee.washington.edu> wrote:
>
>> You are not supposed to ship generated bindings to another
>> system.  Let each system generate its own python bindings
>> using pybindgen (but no gccxml or pygccxml needed).
>> Therefore, I see no problem here.
>
> This is not how I remember the bindings story unfolding.  This is also not
> how things have worked since July 8, 2008 when the first Python bindings
> were checked into ns-3-dev.  I believe that ever since then bindings were
> generated on one system and distributed along with everything else.
>
> So I think we have a problem that needs to be fixed one way or the other
> (either stop checking in bindings or start filtering them).
>
> I don't recall ever making bindings without using --python-scan (which does
> use gccxml, right?).  What are you suggesting doing?  I don't get it.

I have a sense that this is terminology issue.  Perhaps Gustavo will
clear it up?  We certainly ship a bunch of py files in
bindings/python/, and these change when our C++ API changes (and a
developer runs python-scan and checks in the resulting changes to
these py files).  This is what Craig and I are talking about, but
we're probably calling it the wrong thing.

It still seems to me as if the updates to these files might be
dependent on how your system and ns-3 were configured.  Is this not
true?
-- 
Raj Bhattacharjea
Georgia Institute of Technology
School of Electrical and Computer Engineering
Ph.D. Candidate
Systems Analyst
404.894.2955