Re: [e-users] error on statically linked programs that use imlib2 static libraries

this make things clear. thankyou. so, shared only.
i tried build it static because in configure --help there is:
--enable-shared[=PKGS]  build shared libraries [default=yes]
--enable-static[=PKGS]  build static libraries [default=yes]

------- Original Message -------
On Thursday, July 27th, 2023 at 4:49 AM, Carsten Haitzler <[email protected]> wrote:


> On Wed, 26 Jul 2023 18:36:45 +0000 ruivlea via enlightenment-users
> [email protected] said:
>
> > hello,
> >
> > i tried to statically build programs (scrot and nsxiv) that use imlib2. They
> > can be built. But unusable. *scrot:
> > % scrot -s
> > scrot: Saving to file 2023-07-26-181818_137x107_scrot.png failed
> >
> > *nsxiv:
> > % nsxiv /home/ruivlea/downloads/sample-1.gif
> > nsxiv: /home/ruivlea/downloads/sample-1.gif: Error opening image
> > nsxiv: no more files to display, aborting
> >
> > tried open png and jpg, same result.
> > But both scrot and nsxiv usable and works well if shared linked.
> > is imlib2 designed only for shared linked programs? or is there a bug on
> > imlib2 static libraries?
>
>
> You can't do this due to the way imlib2 was designed to work with loader
> modules. So shared lib linking only. Evas is similar but actually can be built
> in a way to inline loaders too and then allow for functional static linking.
> Evas is what replaced Imlib2.
>
>
> --
> ------------- Codito, ergo sum - "I code, therefore I am" --------------
> Carsten Haitzler - [email protected]