Since the latest elm colorclass changes we need eldbus-codegen to generate
some files. Not all setups have this in their normal $PATH so let allow these
setups to set the correct path during configure. This allows our Jenkins setup
as well as others to work again.
Summary:
This small application for quick testing main features and changes in Evas 3D.
Main features: effects shadow, fog, measuring fps, load 3D model, panel for change
sets light and camera.
Reviewers: Hermet, raster, cedric
Differential Revision: https://phab.enlightenment.org/D1953
Signed-off-by: Cedric BAIL <cedric@osg.samsung.com>
When adding xz as third compression format in May 2014 I mentioned that I'm
going to remove bzip2 in favor of xz in 1.12.
I heard no complains but I left it in for 1.12. With 1.13 starting its time
to remove it. From now on it will be only gz and xz compressed tarballs.
ecore_x, ecore_wl, ecore_drm etc. were being linked to clients as they
were added to the pc file - they should not have been. elm hides
these. it's meant to hide them. remove them from the pc file.
I'll reintroduce this in a moment, was just easier this way in order to
merge Vincent's changes.
This reverts commit d46fa601ef45d579d1448b19887d02ff2dfbb576.
thre are still all the old engines supported inside, but docs dont say
so so effectively deprecated. also handle a NULL engine. this is part
of our engine/display system cleanup.
Especially the -fvisibility=hidden would be needed here for our EAPI handling.
I never realised we miss this here but Lukasz Stanislawski pointed me to it
when we wondered why it linked ofr him with missing EAPI but not for me.
I'v compiling and releasing elm like this for a long time now so I don't
expect any trouble but if something strange comes up we can still revert it
before 1.11 final.
The -shared option in LDFLAG somehow is poisoning the configure run inside
distcheck. This results in the compiler test getting a segfault and failing.
I would really like to understand why this is needed to be set here manually
anyway. Same for fPIC and dPIC. I would expect that we leave this to the user
compiling the code or the packager. Skimming through the log only brought up
fixing c++11 globally. Not really a commit message that helps me to
understand why this is needed...
Stefan Schmidt
Daniel Juyung Seo
Oleksandr Shcherbina
Cedric BAIL
Carsten Haitzler
Savio Sena
Vincent Torri
Tom Hacohen
Vincent Torri
Kai Huuhko
q66