2015-02-27, 10:16
Running software and compiling software have different requirements, but the GCC present in Ubuntu Trusty now makes compiling a debug build of Kodi somewhat of a nightmare, if like me you thought 4GB ram would be ok, because it use to work just fine with older Ubuntu releases on same x86 hardware.
Now however you need the ol swap partition/file back if you want to achieve this, else it will indeed eat your babies and kill your kittens.
I've identified several high risk areas on the compile procedure that will slurp the ram like it was going out of fashion.
When compiling
DVDPlayer will suck 3.1 to 3.9GB + swap
Bluray around 3.1GB to 3.5GB +
_Others_ that like DVDplayer also go beyond.
So if you want to --enable--debug you going to need swap else it will crash and hang your machine during compile.
Ideas/thoughts and possible workarounds or fixes welcome.
Now however you need the ol swap partition/file back if you want to achieve this, else it will indeed eat your babies and kill your kittens.
I've identified several high risk areas on the compile procedure that will slurp the ram like it was going out of fashion.
When compiling
DVDPlayer will suck 3.1 to 3.9GB + swap
Bluray around 3.1GB to 3.5GB +
_Others_ that like DVDplayer also go beyond.
So if you want to --enable--debug you going to need swap else it will crash and hang your machine during compile.
Ideas/thoughts and possible workarounds or fixes welcome.
