Am Wed, 13 Feb 2013 15:56:57 +0900 schrieb Carsten Haitzler (The
Rasterman):
> > Could you please tell me how to disable threading support as in
> > 1.7.5? Maybe even by hacking build environment. I played around,
> > but some of the m4 macros are really a nightmare!
>
> we removed the ability - we're threading only now. we're removing
> optional untested codepaths and reality is as we work more on things
> inside of evas and edje, we'll use threads more and more to
> parallelize things behind the scenes, so it's better to figure out
> how to make it work on bionic, than avoid it.
After going much deeper into the problem I found out that going to a
newer Android API solves the problem so far that nearly all code
compiles. There're some minor functions that I need to port later or
simply don't support.
The reason for not always taking the latest Android API is for sure to
support old devices on the market..
Finaly I got efl trunk compiled and running (buffer engine) after many
hacks in the build system. If my port is more complete I'll propose some
changes here on this list. Most times some additional checks which
could be done by configure if android platform is found. I hope not to
create any new configure options.
> > never tried to compile with 1.7.5 (e.g. eeze or emotion) for
> > Android. The NEON detected also doesn't work for me (It worked with
> > 1.7.5). I
>
> it will work if your CFLAGS have -mfpu=neon in them (ie u CAN compile
> neon code). :)
Thanks I'll try this. Thanks!
> > liked to idea of the separate libraries. But I'm sure there were
> > good reasons for the design change...
>
> years of complaints that efl is too hard to build (too many libs).
>
> too much overhead for releases (having to release 12+ libs each time
> and fix up versions/readmes/headers/whatever for each), and having to
> create layers and hoops to jump through - eg feature goes into evas -
> then we expose in ecore evas then expose again in elm.... - we make
> more and more apis and layers where reality is we just wanted the
> feature up in elm but it had to LIVE in evas.
>
> also this allows us to eventually inline across efl libs, gaining
> efficiency (eg make a libefl.so ... right now this is on the list of
> stuff for efl 2.0 possibilities). also now we need to be creating
> efl-wide interfaces (multiple-inheritance) and that just wouldnt fit
> into any specific lib in the old efl setup.. now with a single tree..
> it is easy as its general efl infra stuff.
This is correct. Compiling without easy_e17.sh was a pain even after
years of knowledge. So in general it was good. But I just like to point
of to the responsible developers that "maybe" it's a good idea to
separate at least that "general purpose part" from the "platform
specific stuff". It was not so funny to fight against problems to get
the build system NOT to compile eeze, edbus and other stuff. That is
really not needed.
In my eyes the chain up to edje is so general purpose as graphic stack
that also projects complete independent from E17 may use it. (e.g. as I
use it for a project). Only my point. We don't need to discuss it
here...
> > How ever - from some ones point who does a cross compiler platform
> > port it's a torture. But I don't like to cry...
>
> right now the efl tree is in bad shape for cross-compiling and even
> for general rebuilds. it's linking out-of-tree libs for example. it's
> not in good shape and need massaging into shape, but i have no time
> right now as i already have a backlog of like 200 mails (questions,
> patches etc. - like this mail of yours), and frankly my backlog is
> not shrinking...
Sorry to bring even more work to your desk!
This was the reason why I started the port with stable 1.7.5. But after
first success I've seen that many things changed in trunk so much that
I don't like to maintain this and switched to EFL trunk.
My next big milestone is to write a software_android engine. I looked
into the sources yesterday and think this it's not so hard. But I'll
see... If problems will occur I'll ask here. Feel free to answer them
or not. :-)
regards
Andreas
--
Technical Blog <http://andreasvolz.wordpress.com/>
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
