From: Hartmut S. <ha...@gm...> - 2006-06-20 22:13:48
|
Thank you for this hint. I briefly had a look into the cvs HEAD and it seems that Lua::classHandler() needs some work :). What is actually the recommended toolchain with SWIG on Windows? I had no luck with MinGW, anybody has some VS project files? Regards, Hartmut On 6/21/06, William S Fulton <ws...@fu...> wrote: > > I think your problem is exhibited by the imports test case in the > test-suite. Go to the Examples/test-suite/lua directory and run: > > make -s imports.multicpptest > > Try it in the other language directories as well, eg in > Examples/test-suite/python. > > I'd compare the generated code from Lua with the other scripting > languages. Any major differences are going to be down to > missing/different code in the language module files (lua.cxx vs > python.cxx/ruby.cxx etc) or possibly, but unlikely in this case in the > typemaps in the Lib directory. > > William > > Hartmut Seichter wrote: > > Well, after all SWIG is open source :). I would go the extra mile and > > fix that problem if I only could find a comprehensive documentation > > about how to hack the SWIG scripts. At the moment I have no clue how > > these scripts work. Any pointers there? > > > > Regards, > > Hartmut > > > > On 6/16/06, Bill Baxter <wb...@gm...> wrote: > >> Hey Hartmut, > >> I don't have any sort of answer for you, but I think the current user base > >> of Lua/SWIG is either very small or nonexistent. I asked a Lua question a > >> few months back and heard zilch in reply. And I haven't heard another Lua > >> question since then, until yours. I think Lua users must all be using tolua > >> or tolua++ or luabind. It's too bad. The promise of SWIG -- one wrapper > >> generator for all your scripting needs -- is nice, but it only works if > >> everyone buys into it. > >> > >> Regards > >> --Bill > >> > >> > >> > >> On 6/16/06, Hartmut Seichter <ha...@gm...> wrote: > >>> Hi, > >>> > >>> SWIG newbee question ahead. I have a quite large project for wrapping in > >>> multiple scripting languages. I love to see Lua being supported. But i > >>> ran into problems with the Lua generator does not handle imported > >>> headers correctly, much unlike the Ruby wrapper which does exactly whats > >>> intended. To illustrate: > >>> > >>> file a.i > >>> -------- > >>> %module a_mod > >>> > >>> %include headers/stuff.h // using the headers directly - class A {} > >>> > >>> > >>> file b.i > >>> -------- > >>> %module b_mod > >>> > >>> %import a.i // import from a.i > >>> > >>> %include headers/based_on_stuff.h // classes declared are inherited, > >>> class B : public A {} > >>> > >>> > >>> ... > >>> > >>> What happens with the lua wrapper is that it "forgets" to implement > >>> _wrap_class_A even though it references to it. > >>> > >>> Any toughts or pointers on that? > >>> > >>> > >>> Regards, > >>> Hartmut > >>> > >>> > >>> > >> > >> > >> _______________________________________________ > >> Swig-user mailing list > >> Swi...@li... > >> https://lists.sourceforge.net/lists/listinfo/swig-user > >> > >> > >> > > > > > > > > _______________________________________________ > Swig-user mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-user > -- technotecture labs, technotecture.com |