I fixed the problem (for me).  I'm still not sure why I wasn't able to
compile the loader obj files as shared libraries, but I went into the
directory with them and compiled them as shared by hand.  (e.g.: gcc
-shared loader_png.o -o png.so && cp png.so /usr/lib/imlib2/loaders.) 
Everything seems to work now.


On Wed, 2 Feb 2005 12:35:01 -0600, robotron:2084 <[EMAIL PROTECTED]> wrote:
> I have a problem that I spent a good part of last night trying to
> debug, so bear with me...
> 
> I downloaded a cvs snapshot of e17 on Jan 25.  I've installed the
> libs, and set myself to compiling some of the apps, and ran across a
> problem with edje_cc.  It reported that it couldn't load a png file as
> a part of theme.eet in elation, for example.  Two hours later, I
> pinned the problem down to the loaders that imlib2 uses.  Imlib2
> constructs a list of loaders to use searching through (for me)
> /usr/lib/imlib2/loaders, which is a directory that exists and is
> populated by the different image formats ... except that imlib2 is
> looking for shared object loaders ending in .so, and no loaders get
> compiled as shared objects when I compile imlib2 + imlib2_loaders.
> Imlib2 then returns NULL from imlib_load_image(...), causing major
> borkage to edje_cc.  (And imlib2_show, and imlib2_view, ...)  I tried
> configuring with --enable-shared, even though it's listed in --help as
> defaulting to yes, but to no avail.
> 
> Any ideas?
>


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to