Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Upgrade Go-For-It? #121

Open
hc128168 opened this issue Oct 8, 2020 · 3 comments
Open

[Feature request] Upgrade Go-For-It? #121

hc128168 opened this issue Oct 8, 2020 · 3 comments

Comments

@hc128168
Copy link

hc128168 commented Oct 8, 2020

Hi,

I built and installed the previous version from this repository on CentOS 7.

Now, I want to install the latest from this repository. What's the cleanest way to remove old one as the old one doesn't work (launching it via gnome 3 shows nothing)?

@JMoerman
Copy link
Owner

JMoerman commented Oct 8, 2020

I do push changes to https://github.com/mank319/Go-For-It, though not on a regular basis. So aside from possibly being a bit out of date it shouldn't matter that you downloaded the code from there. What version did you download, did you download the code from the master branch or did you download a release?

As https://github.com/mank319/Go-For-It doesn't contain any additional changes it isn't strictly necessary to remove the previous installation, you can just install a new version.

As for uninstalling: CMake generates a file install_manifest.txt in the root of the build directory. This file lists all files that were installed. (this is also the case for other software using the CMake build system)
You should only have to remove these files to fully uninstall the application.

Could you post the command line output when you launch the application from the command line? Assuming you didn't specify -DAPP_SYSTEM_NAME:STRING=<something> at build time you should be able to launch the application by running com.github.jmoerman.go-for-it (even if you got it from https://github.com/mank319/Go-For-It).
This can provide essential information on why it doesn't start.
If you compiled a development version (master branch) it is better to first compile install the current version on the master branch.

@hc128168
Copy link
Author

hc128168 commented Oct 8, 2020

$ com.github.jmoerman.go-for-it com.github.jmoerman.go-for-it: error while loading shared libraries: libcom.github.jmoerman.go-for-it-0.so.0: cannot open shared object file: No such file or directory

So the problem is that libcom.github.jmoerman.go-for-it-0.so.0 is installed in /usr/local/lib64, which isn't in LD_LIBRARY_PATH. I think /usr/local/lib64 and /usr/local/lib have been deprecated in CentOS since CentOS 6 or so.

Thanks for the pointer!

@JMoerman
Copy link
Owner

JMoerman commented Oct 8, 2020

Readme.md instructs to build with -DCMAKE_INSTALL_PREFIX=/usr. The default is set to /usr/local for some reason. Version 1.8.x would still work as it doesn't generate a separate .so file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants