On Mon, Jan 14, 2013 at 10:34 AM, Arvind R <arvin...@gmail.com> wrote:
> On Mon, Jan 14, 2013 at 4:01 PM, Gustavo Sverzut Barbieri
> <barbi...@profusion.mobi> wrote:
>> On Mon, Jan 14, 2013 at 1:54 AM, Arvind R <arvin...@gmail.com> wrote:
>>> On Mon, Jan 14, 2013 at 6:16 AM, Gustavo Sverzut Barbieri
>>> <barbi...@profusion.mobi> wrote:
>>>> On Sat, Jan 12, 2013 at 8:08 PM, Arvind R <arvin...@gmail.com> wrote:
>>>>> fix compile failure due to missing definitions
>>>>
>>>> applied, but I wonder how you got these if generic module just builds
>>>> statically and thus uses the definitions given to libemotion.la :-/
>>>>
>>> I dislike static builds and generally try to build shared if I can -:)
>>> Patched, of course.
>>
>> While I understand that, what about actually discuss this with the ML
>> first to understand the reasons?
>>
>> We have been putting lots of effort to get efl single tree right, and
>> this includes the review of module linkage. In this case it's
>> unexpected to have the generic loader as a module as it's not a real
>> one. We just kept the code split to avoid the merge effort, but in
>> reality it's just a different kind of loader, thus makes 0 sense to
>> have it out -- IOW: remove your patch  :-)
> OK.
>>
>> It's the same with evas, the generic loader will always be builtin. As
>> is the buffer engine.
> U mean I don't have to build the evas-generic-loaders and install?

Argh, too close names causing confusion.

trunk/efl/src/modules/emotion/generic and
trunk/efl/src/modules/evas/loaders/generic should be static and always
enabled. Never patch to make it optional/libs_LTLIBRARY

trunk/emotion_generic_players and trunk/evas_generic_loaders will
still be independent and built separate.



>>For ecore-evas I even merged buffer engine backin libecore_evas.so
> Ran into trouble in previous packaging and elevated buffer-engine to
> debian's recommended (mandatory dependency status).

yeah, now it's built in and this shouldn't happen.

the whole reason is to avoid problems. It's like E17 that ran into
problems with packaging in the past and during startup will check if
you have JPEG and EET loaders... this can go away as there is no more
way to build without those :-)


--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbi...@gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to