On Fri, 08 Aug 2025 17:39:34 +0000 dep <d...@drippingwithirony.com> said:
> said i...@bandshed.net:
> | Hi,
> |
> | Is there something you need specifically in Enlightenment GIT? If you're
> | on Debian, Trixie has Enlightenment 0.27.1 which is the current release,
> | further to that if you install the mentioned efl-dev package then
> | building most common E add-ons (rage, entice, evisum, etc..) is very
> | easy.
>
> My thoughts were these: First, to move it to /opt. Second, to make an
> environment to build Enlightenment applications. While the Trixie
> repository contains Enlightenment, Terminology, and Ephoto, it has nothing
> else. Third, it was suggested as a good idea, and if I'm going to use it
> that's a good suggestion. Fourth, I've been slack about such things: the
> last thing I compiled was the kernel, on Christmas Eve 2000. ("make
> mrproper" anyone?)
>
> Efl-dev remains a mystery to me. I cannot find it, and if I can't do that,
> how can I make it fail to compile here?<g>
you don't need it - it's a side effect of debian packaging that splits out
header files and developer files only needed when building something to link to
efl. as you compiled and installed from source these files are not split into
another package and you have them.
your issue is precisely what the readme on building things like efl and e talk
about:
https://git.enlightenment.org/enlightenment/enlightenment/src/branch/master/README.md
specifically PKG_CONFIG_PATH
as you installed in the default /usr/local prefix then you will need to teach
pkg config to look there by setting PKG_CONFIG_PATH. the .pc files efl
installed will be somewhere like /usr/local/lib/pkgconfig
or /usr/local/lib/x86_64-linux-gnu/pkgconfig - have a look around until you
find things like eina.pc and elementary.pc etc ... you then need to have a
search path like the readme indicates ... you might ALSO want to update PATH
too so efl binaries are found and don't forget ld.so.conf so the runtime linker
can find libraries(libsomething.so files) in your /usr/local prefix ... the
README covers these ld.so.conf things too. they apply to building e against efl
- they will apply to anything else too. it's generic "always have to do this
stuff for anything you compiled and want to link against". complain to distros
if you don't like that a default /usr/local prefix location is not supported by
default :)
> --
> dep
>
> Pictures: http://www.ipernity.com/doc/depscribe/album
> Column: https://ofb.biz/author/dep/
>
>
>
> _______________________________________________
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - ras...@rasterman.com
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
