Re: [Adonthell-devel] SWIG Advanced topics

[Alexandre Courbot]

> But what we'll do is using classes from other modules in a module. Which
> means that plenty of classes will be wrapped a number of times.
> Moreover, the SWIG code will be contained in each module. As long as all
> SWIG functions are declared static, that doesn't hurt, but the new item
> code for example already requires access to SWIG functions (so they
> can't be static). I fear there will be conflicts when linking.

Mmm. In my recent tests, I can say that I've used classes of a module in
another module (argument passing) without a poroblem. And the classes
were wrapped only once.

> That is the problem. It wouldn't be on the developer side :(. Unless we
> include the code for the library like we did with SDL Mixer. Shouldn't
> be a problem at all, I think. Look at SWIG-1.3.xx/Runtime/Makefile.in.
> It's a single file that needs be assembled and compiled. We could easily
> ship that file with Adonthell's source code.

Isn't the swig library static? So why would the end user need it?

Alex.
-- 
http://www.gnurou.org