On Thu, 28 Jun 2012 10:15:00 +1000 David Seikel <onef...@gmail.com> said:
> On Thu, 28 Jun 2012 08:38:36 +0900 Carsten Haitzler (The Rasterman) > <ras...@rasterman.com> wrote: > > > On Thu, 28 Jun 2012 01:51:20 +1000 David Seikel <onef...@gmail.com> > > said: > > > > > On Thu, 28 Jun 2012 00:32:15 +0900 Carsten Haitzler (The Rasterman) > > > <ras...@rasterman.com> wrote: > > > > > > > On Thu, 28 Jun 2012 01:19:14 +1000 David Seikel > > > > <onef...@gmail.com> said: > > > > > > > > it TAKES me sub 1 second to do it. i do: > > > > > > > > rbe.sh > > > > > > > > thats it. that svn updates, runs make clean and make with my > > > > master makefile. it takes ME as long as it takes to type in the > > > > above command. the rest happens automatically. all my machines > > > > i've had for the past 3 years can compile all of this in sub 10 > > > > mins. today its around 5. i'm wondering why it takes a PERSON > > > > that long to do it. (i'm getting at something here. eg - maybe he > > > > is wasting tonnes of his personal time whenever he rebuilds > > > > because he never invested the few minutes needed to automate it > > > > and never have to spend the time again). > > > > > > Until he answers, we can only speculate. > > > > > > Only takes me one second to start up the build script as well, but > > > on my ancient 32 bit computer I had to make sure I had a block of > > > time where I was not doing anything else that needed much CPU or > > > memory for the next hour. > > > > > > On my embedded x486 it takes nine hours to compile the half of EFL > > > it uses for the embedded project on it. Usually I run that on an > > > emulator, which is much faster. > > > > > > On my current multi core 64 bit system with tonnes of RAM, I don't > > > have to worry about freeing up the computer itself to build EFL and > > > friends, coz it usually has plenty of grunt to spare. Still takes > > > a long time, coz I try to build most things in SVN as well as the > > > docs. > > > > yes yes. i know. i have arm boxen too and they can sit and spend a day > > compiling. it's stilly but hey - that's what it takes. if you want to > > just try and test new efle bugs and features u dont need to do it > > there unless that is the only place the bug turns up. the fast path > > is to use that multi-core i5/i7/whatever u have there and streamline > > your build/install process. :) otherwise u have a nasty lag on being > > able to update. :) > > That will be why I only ever built on the x486 to try it. I normally > build on the emulator when I need to package it up for the x486 or > other slow embedded device. Most of the time I build and test on the > work station. I can hold my breath while the embedded software builds > on the workstation. B-) why emulator? you can just have a chroot with the appropriate dependencies installed + toolchain and u can build at full native speed. just ensure CFLAGS has -march=486 :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
