search

bootchk / resynthesizer

Suite of gimp plugins for texture synthesis
GNU General Public License v3.0
1.47k stars 163 forks source link

Python scripts are not installed to the proper location on a 64-bit system #15

Open garrett opened 11 years ago

garrett commented 11 years ago

I couldn't find any of the Python scripts in Gimp on my system, until I looked around the filesystem.

With ./configure --prefix=/usr (to make sure Gimp did see the plugin when installing it), I noticed the scripts were installed to /usr/lib/gimp/2.0/ instead of /usr/lib64/gimp/2.0/.

This seems to have only affected the Python scripts, and not the actual plugin itself.

bootchk commented 11 years ago

On 03/21/2013 05:53 AM, Garrett LeSage wrote:

I couldn't find any of the Python scripts in Gimp on my system, until I looked around the filesystem.

With |./configure --prefix=/usr| (to make sure Gimp did see the plugin when installing it), I noticed the scripts were installed to |/usr/lib/gimp/2.0/| instead of |/usr/lib64/gimp/2.0/|.

This seems to have only affected the Python scripts, and not the actual plugin itself.

— Reply to this email directly or view it on GitHub https://github.com/bootchk/resynthesizer/issues/15.

Thanks.

I did a little research. If you already know how to change the install scripts so that they work for 32 or 64 bit, please let me know.

It seems to me that there might not yet be a "standard" way of fixing this in the install scripts. Maybe I just need to do some more research.

bam80 commented 7 years ago

Don't know why it doesn't set by default, but I forced proper 64-bit library path with: ./configure --libdir=/usr/local/lib64 Until then, the scripts didn't find out by Gimp, so this bug is critical.

PS: actually, my configure string in .SlackBuild file is:

./configure --prefix=$PKG/usr --libdir=$PKG/usr/lib64

so I didn't hardcode it. Not sure how to make it properly

bootchk commented 7 years ago

AFAIK it should be working. I briefly looked at the install scripts. The file configure.ac does: GIMP_LIBDIR=$PKG_CONFIG --variable=gimplibdir gimp-2.0 which should define a symbol properly so that plugins are installed in the correct place. (There is another tool gimptool2-0 that can be used to find where GIMP is installed, but its man page recommends using PKG_CONFIG directly.) I mostly inherited those scripts, so I might need to bump it up to the GIMP project. But there is an ongoing mess with 32/64. One might have a 64 bit OS with a 32-bit GIMP. I suspect that for most 64 bit users, it does install properly (otherwise I would have heard more about it.) Is your system pure 64-bit, and what distribution? I do appreciate your reporting it.

bam80 commented 7 years ago

Lloyd, I have latest Slackware64 with multlib installed, and of course I run 64-bit GIMP. Is the path detected right on your system?

bam80 commented 7 years ago

Funny, in the Slackware, the library path also somewhat hard-coded for Gimp:

./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \

bootchk commented 7 years ago

My system is Ubuntu16.04 64-bit. I just checked that Resynthesizer installs properly, but to /usr/local/lib/... (which is an Ubuntu quirk AFAIK and requires one to change preferences 'Folder' in GIMP as discussed in the README.) I also don't see a /usr/lib64 but do see a /lib64 (other Ubuntu quirks?) I don't know enough about standards for Linux filesystem structure, especially re 64 bit. I would guess that some of the world has moved to using /usr/lib (not /usr/lib64) as the proper place when the OS is 64-bit. I could be wrong. I will be glad to change the Resynthesizer scripts if I knew what the change should be.