On Fri, Nov 28, 2008 at 01:09:10PM +0100, Stefan Reinauer wrote:
Carl-Daniel Hailfinger wrote:
Can we make this optional, please? 700MB is already quite a lot, let alone 1.6GB.
The changes are fine with me, but there should be some option somewhere to not generate the extra 900MB of debug output if you don't want it.
That's also one of the reasons why I didn't ack the complete patch. I do coreboot development on my work machine which happens to be a laptop with not enough hard disk space. I would have to delete some stuff to run the new abuild.
AFAICS abuild images are not fully bootable anyway because they have no payload. I may be wrong, though. However, if I'm right, the debug symbols in abuild don't help anyone. Debug symbols in "real" builds would make sense.
Even with the most expensive laptop disks, the price per gigabyte is at 20-60 euro cents.
Are we really having this discussion in 2008?
Yes, I'm with Carl-Daniel on this issue. I'm also working on a laptop almost always (but this also applies to desktop PCs as well), and even though I upgraded my drive to be double the size recently, that space was consumed away in just 1-2 days. There's never be enough disk space, no matter how big the drive.
As an example, I currently have less than 1 GB of free disk space. I'm already using up ca. 1.2 GB just for v2 and v3 checkouts, let alone various other git/svn/cvs checkouts of other projects I'm involved with or interested in, and lots of other stuff of course. So yes, disk space issues cannot be ignored, not even in 2008, IMHO.
However, another way to solve this may be to delete each board again after it has been built with abuild. As a developer using abuild you usually only want to know if all boards will still build fine after your patch, you don't really need to keep all the build output around. Shall we add such an abuild option maybe?
Uwe.