http://imgs.xkcd.com/comics/compiling.png
^^ I kind of identify with that, although I'm not that bad. :D
Printable View
http://imgs.xkcd.com/comics/compiling.png
^^ I kind of identify with that, although I'm not that bad. :D
I normally make a fort. I find swords bring too much violence
We used to play hackey sack in the office when we were waiting for long builds.
Half the programmers in our office started working on a project in Java. They could no longer use that excuse.
So, what is their excuse now?
No excuses. They don't get to play.
I think they occasionally crash our source code control server on purpose, though.
How long have ye guys had to wait? As in longest? 14 hours is the longest build I've had to wait for :)
[edit] I didn't wait, of course. I let it run overnight.
And you can also add optimasations to the prefrences of the compiler too... this can vary the build process time...
So lets say ID had to build all the C files from Doom 1... I mean right from scratch original build... wonder how long that took? I wonder if such a deditcated team of proffesionals would play sword fighting games on chairs... well some of them may of done :p
I had to wait two days to compile the Boost libraries on a 33 MHz HP-UX box.Quote:
Originally Posted by twomers
hehe.....Ised that excuese a couple of time, writing a SQL report, then restort to some pointless time consumpting activity. When the boss asks if i dont have any work, I just sya the report is running...works like a charm....hehehe
Forgot to say the 14 hour wait was one step of 6 I had to do. Most of the others would take about an hour at most but there was another one which brought the time it took to about a day. Also, tweren't in C. It was HDL (hardware), stuff. Heh. Boost in a 33MHz ... why?
Compiled a whole AMPP setup on a 486, max optimizations. Using source from about 1 year ago... took ages, defianly would have been tracked in days, not hours.