We just pushed an update to the build structure on master and next to
try to help with the memory consumption and possibly even build time.
I split gr-blocks up into multiple smaller swig builds and put them
together in the end. So you don’t have to try to compile the gigantic
c++ file that swig created for it. Now, it’s just 3 files a third of
gigantic.
This has definitely helped things on my systems, even the only with
less RAM that I could drive to its knees if I asked it to parallelize
the build too much. It should help everyone with build and swap
issues.
The technique is rather general and simple now that the full syntax
has been tested, so we could split it up even further or do similar to
other components if they grow too large. I’d rather not, but this is a
possibility.
Tom
Thanks a lot, it greatly helped and the build now succeeds.
But since you asked…
On 04/05/13 20:43, Tom R. wrote:
The technique is rather general and simple now that the full syntax
has been tested, so we could split it up even further or do similar to
other components if they grow too large. I’d rather not, but this is a
possibility.
The files
gnuradio-core/src/lib/swig/CMakeFiles/_gnuradio_core_general.dir/gnuradio_core_generalPYTHON_wrap.cxx
and
gnuradio-core/src/lib/swig/CMakeFiles/_gnuradio_core_gengen.dir/gnuradio_core_gengenPYTHON_wrap.cxx
take approximately four hours to compile on a 500 MB RAM
machine so I suspect it would speed up things a lot if you split up this
file too.
Regards,
Marc Hlscher
take approximately four hours to compile on a 500 MB RAM machine so I
suspect it would speed up things a lot if you split up this file too.
Regards, Marc Hlscher
That’s not a lot of RAM. I recommend 2GB
–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium