Respect "--prefix" parameter for ./configure

[lig]

make install installs into /usr prefix always.

Steps

1. ./configure --prefix=/usr/local wich is default value according to ./configure --help
2. make
3. make install

Output

install -D bin/telegram-purple.so /usr/lib64/purple-2/telegram-purple.so
install -D tg-server.pub /etc/telegram-purple/server.pub
install -D imgs/telegram16.png /usr/share/pixmaps/pidgin/protocols/16/telegram.png
install -D imgs/telegram22.png /usr/share/pixmaps/pidgin/protocols/22/telegram.png
install -D imgs/telegram48.png /usr/share/pixmaps/pidgin/protocols/48/telegram.png

Expected output

install -D bin/telegram-purple.so /usr/local/lib64/purple-2/telegram-purple.so
install -D tg-server.pub /etc/telegram-purple/server.pub
install -D imgs/telegram16.png /usr/local/share/pixmaps/pidgin/protocols/16/telegram.png
install -D imgs/telegram22.png /usr/local/share/pixmaps/pidgin/protocols/22/telegram.png
install -D imgs/telegram48.png /usr/local/share/pixmaps/pidgin/protocols/48/telegram.png

[majn]

Hi,
the installation directory is determined by the pkg-config variables of libpurple. If you copy it to a different directory it won't load the plugin or the plugin data anymore, so there is no point in being able to change the prefix.

If you want to install your plugins to /usr/local you need to compile libpurple for yourself, so the plugin directory will be somewhere in /usr/local

[lig]

Well, just wondering. What the behavior is for two different versions of
libpurple on one machine with different prefixes. Will one be able to set
the correct prefix via ./configure?

Personally basing on your mention I expect that it will throw error on
./configure invocation if there is no libpurple compiled with provided
prefix.

On Thu, Nov 27, 2014 at 2:22 PM, mj notifications@github.com wrote:

Hi,
the installation directory is determined by the pkg-config variables of
libpurple. If you copy it to a different directory it won't load the plugin
or the plugin data anymore, so there is no point in being able to change
the prefix.

If you want to install your plugins to /usr/local you need to compile
libpurple for yourself, so the plugin directory will be somewhere in
/usr/local

—
Reply to this email directly or view it on GitHub
#24 (comment).

Serge Matveenko
mailto: serge@matveenko.ru
github: http://lnkfy.com/1
linkedin: http://lnkfy.com/S

[majn]

Configure will check for the pkg-config entries and should fail if libpurple is missing.

Unfortunately I can't tell you how pkg-config behaves if you've two separate versions of libpurple installed, it will probably overwrite the old settings and take the path to the latest installation of libpurple, but thats just a guess, I have never tested that.

Currently I simply ignore --prefix completely when installing, so you won't be able to choose where you install it. Can you think of a concrete situation where this could cause problems? I guess if you take the time to compile libpurple it from source you only want to use only that version and not the older version from the package manager.

[ndias]

Hi,

I'm creating an rpm of telegram-purple, and because of --prefix is not honored the rpm creation is aborted.

[majn]

@ndias does it work with this patch? 87fad25

I tested the patch with rpmbuilder and it ran through just fine.

[ndias]

Yes, it works, thanks :)