On Wed, 27 Jun 2012 19:40:45 +0200 Tomas Cech <tc...@suse.cz> said: > On Thu, Jun 28, 2012 at 01:51:20AM +1000, David Seikel wrote: > >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. > > > >Your 5 minutes would just be for the EFL and E17 itself, probably with > >no docs. Lots of people build more. > > > >Personal time to start it might not be the issue. The kids might want > >to reboot the family computer into Windows to play WoW, and are pissed > >off at dad for keeping it busy with this useless compile thingy. > > Almost correct :) > > I build this on the same machines as openSUSE is built. It's so called > openSUSE Build Sevice (http://build.opensuse.org), openSUSE > deployement of Open Build Service > (http://www.open-build-service.org/). > It has several consequences: > > 1] I'm not the only one who builds on these machines > > 2] as security measure each build host is virtual machine created for > this purpose and containing only necessary dependencies > > 3] RPM build is not the same as `./configure && make && make install' > > 4] at the end some additional checks on RPM and build log are > performed > > 5] packages are signed, there is (re)created RPM repository with new > metadata > > > For me is updating also 1s of my time to refresh packages, only the > build takes a while.
that seems like a very round-about way of doing stuff. i know obs. it i one of those things that i avoid BECAUSE it massively impacts development speed/time to the point of going on my "blacklist of stuff not to use". that same as the workflow of "hey - lets build a package, then install it and test it to see if the bug is gone". been there. done that. obs and "make a package to test" is the workflow i have only ever used *IF* the code itself it totally fine - app/lib is great and nothing left to hunt for and it's time to package and test the packaging hasn't missed something/messed something up. it's just advice. you'll be many many many times more productive having a "fastpath". it's worth it. you can use different prefixes for src installed (eg /opt/e) and use PATH.LD_LIBRARY_PATH and PKG_CONFIG_PATH to isolate your 2 worlds (pkg vs src). -- ------------- 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
