Geany plugins now build if configured --prefix=/home/lex/geany_meson --with-geany-libdir=/home/lex/geany_meson/lib and install to $PREFIX/lib/geany but do not appear in plugin manager.

You have to use the correct libdir, obviously, i.e. --with-geany-libdir=/home/lex/geany_meson/lib/x86_64-linux-gnu. Typically you avoid setting --with-geany-libdir and instead point pkg-config to the correct geany.pc. Under ubuntu, geany.pc has this line: libdir=${exec_prefix}/lib/x86_64-linux-gnu

As I said configuring --with-geany-libdir=/home/lex/geany_meson/lib/x86_64-linux-gnu fails. According to @hyperair when this option was added, this is the "proper" way of configuring this for Debian and derivative systems. But anyway until G-P is mesoned (meson subprojects might be a good fit?) it needs to work.

On this system all the system pkg-configs are under x86_64-linux-gnu/pkgconfig so a geany installed to the system would be out of place and not found if it installed in lib/pkgconfig.

It seems like there are still things being installed in a mixture of lib and lib/x86_64-linux-gnu whereas it should all be the latter if thats the system default determined by meson. I guess its hard to notice on your system if lib is the default, but the meson build should never force lib.

Maybe my meson-geany gets the icons from my system-geany from /usr/local/... ?

The advantage of my habit of only using prefixed geanys and having no system install :-)

The meson build isn't installing $PREFIX/share/icons which is likely the problem.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.