Re: [E-devel] [PROPOSAL] [Evas] Optimizing smooth scaling of Evas in software backend

[Adrien N. <ad...@no...>]

Hi,

On Thu, Dec 18, 2014, Krishnaraj Raghavendra Bhat wrote:
> Yes, probably it won't be packaged by any distro because it's used only in
> chromium browser & lollipop as of now.
> The current cmakefile compiles it to a static library. If we statically link
> libyuv to evas,
> runtime dependencies can be avoided. The size of libevas.so(after stripping)
> increased by 0.3 MB in this case

Please, don't go that way. Absolutely everything that comes from google
for use in chrom* is packaging crap. It's not even meant to be packaged:
it's code dumps without a build system usable for anything besides
chrom*.

We are already seeing this with Angle (OpenGL API implemented on top of
DirectX to work-around drivers with crappy OpenGL implementations on
Windows). The result is that it's not usable at all.

The right way is to have it packaged separately and to pressure upstream
to accept build system improvements. The threshold to get packages into
distributions is usually not very high; the main trouble is with crappy
build systems and these must be solved or they'll come back to bite hard
rather sooner than later.

Note that the only problem here is Google. I'm not sure what is the use
in pushing code with a BSD license and make is to annoying to use. It
almost feels like it's meant to not displease their employees who want
to work on free software, while not making free software in practice.

Regards,
Adrien Nader