On Thu, 2011-10-13 at 18:20 -0400, Aaron M. Ucko wrote: > Soeren Sonnenburg <so...@debian.org> writes: > > > Yeah I know... version 1.0 currently requires (depending on language) > > between 1.5 and 3.5 GB (for C++ heavy octave) to compile... > > Yikes!
I hate that too... Before 1.0 we had multiple swig modules which generated lots of issues (octave crashes, compiler errors for the newly supported languages) so we are now better using what is well tested... > > I am not really sure what to do about this - the generated swig wrappers > > are ~18MB (>500 kLoC) in size. > > Good question. Reducing the wrappers' optimization level might help, > and not even necessarily impact runtime performance too heavily, as the > underlying library will remain fully optimized. That indeed helps a bit already (and also speeds up compilation by a couple of factors). > Another option could be to split the wrappers into multiple compilation > units; I don't know how involved that would be in this case, though. Hmmhh, I also thought about that. I think this is the only real chance without loosing functionality - so I will ask on the swig mailinglist... Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962
signature.asc
Description: This is a digitally signed message part
