On Mon, 10 Sep 2012 12:25:39 -0300 Gustavo Sverzut Barbieri <barbi...@profusion.mobi> said:
> On Mon, Sep 10, 2012 at 9:59 AM, Carsten Haitzler <ras...@rasterman.com> > wrote: > > On Sun, 9 Sep 2012 21:53:48 -0300 Gustavo Sverzut Barbieri > > <barbi...@profusion.mobi> said: > > > > hmmm. this is indeed going to be a cross-compile problem. it will ALSO be a > > bootstrap problem. in that a totally efl-free system can't easily bootstrap > > itself as we need to compile edj files for things like elementary to work. > > > > so we have 2 situations. > > > > 1. cross-compile. this can't ever be fixed without ALSO having a native efl > > build to provide a working edje_cc. there is nothing much we can do here. > > BUT in this situation we CAN'T use the edje_cc we just compiled ever - we > > must use an externally provided edje_cc > > > > 2. native bootstrap. this is where we have an efl-free system needing to > > execute tools it just created (edje_cc) during build. i think we need to > > consider a "bootstrap" stage. literally this stage builds SOME of efl then > > installs it in $top_builddir and THEN it uses this to continue compiling the > > rest. otherwise we do complicate things - we need to move all edje tests, > > elementary themes and tests and so on totally out-of-tree. this means u can > > compile a working src tree that cant work at all due to missing edj files. > > this isn't pretty and i think it is out job to handle some kind of > > bootstrap stage. in the cross-compile case this bootstrap stage needs to be > > built for the os doing the compiling not the target arch. > > You don't need to install, just use as I did in edje examples > ($(top_builddir)/src/bin/@EDJE_CC_PROG@). However we need eina_prefix > to work properly with that situation so it will work without being > installed (and also aware of libtool's .libs directories) that's seriously not sane. eina_prefix is about finding your install prefix at runtime. the software hasn't been installed yet. the clean way to go is to do a quick install in the builddir of the components u need so they are in correct relative paths and can be used. otherwise eina_prfix has to have hacks in it for every possible build tree setup we have or may have in the future and keep those at runtime. > Note this is NOT a problem only for bootstrap... it's also in regular > development: Let's assume I added a commit that adds a feature to > edje-cc and uses that same feature in some edc. People that "svn up && > make" would get a failure as the system edje_cc does not know about > that feature yet. yeah - i know. tho its still under the bootstrap class of problems. :) > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -------------------------------------- > MSN: barbi...@gmail.com > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > -- ------------- 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
