> Yea, I'm still running Ubuntu Jaunty (9.04) on my dev machine, which > has swig 1.3.36 as the latest version. Not that I couldn't/wouldn't > upgrade, but it would be a pain if I were a new user. > > What's the feature that you're relying on?
It's the package= parameter to %module. Basically the issue is that when one swig module refers to another, it needs to be able to know how to import that other module. If they are in different packages, then the import needs to include some path information which the package= parameter provides. Versions prior to 1.3.39 seem to do this incorrectly even though they supposedly support it. One workaround is to put all of the generated modules into the same package so they can use relative imports (without package information) to import each other. This should hopefully work in older versions. This will take me a couple of days to get done. I hope people are willing to wait so I don't have to back out the code. I must say that I'm getting more and more frustrated with swig (and scons). I really wish they were better. They both try to do too much and end up doing what I need in a crufty way. One of these days, I'm going to take a serious look at boost::python. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
