Skip to content

README: fix dependencies #375

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.

Sign up for GitHub

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

README: fix dependencies #375

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d7a6a6a
README: fix dependencies
AndreiCherniaev Mar 24, 2025
8efafb3
README: fix example
AndreiCherniaev Mar 24, 2025
b62f031
README: make multi-threaded
AndreiCherniaev Mar 24, 2025
a938ff5
README: fix typo in folder name
AndreiCherniaev Mar 24, 2025
5c8b505
README: fix dependencies
AndreiCherniaev Mar 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ If you compile Gpredict from source you will also need the development packages
often with -dev or -devel in the package name, e.g. libgtk-3-dev. On Debian and
Ubuntu systems you can install the build dependencies using:

sudo apt install libtool intltool autoconf automake libcurl4-openssl-dev
sudo apt install dh-autoreconf intltool libcurl4-openssl-dev make
sudo apt install pkg-config libglib2.0-dev libgtk-3-dev libgoocanvas-2.0-dev


Expand All @@ -50,17 +50,17 @@ To build and install gpredict from source, first unpack the source package:
Then change to the gpredict-x.y.z directory and build gpredict:

./configure
make
make -j$(( $(nproc) + 1))
make install

The last step usually requires you to become root, otherwise you may not have
the required permissions to install gpredict. If you can not or do not want to
install gpredict as root, you can install gpredict into a custom directory by
adding --prefix=somedir to the ./configure step. For example

./configure --prefix=/home/user/predict
./configure --prefix="$HOME/predict"

will configure the build to install the files into /home/user/gpredict folder.
will configure the build to install the files into /home/user/predict folder.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
will configure the build to install the files into /home/user/predict folder.
will configure the build to install the files into $HOME/predict folder.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Main question is. Install the files into /home/user/gpredict folder or predict folder?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AsciiWolf any news?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, but I am not sure what the correct folder is. This is a question for @csete.


If you are building directly from the git repository, you have to run
./autogen.sh instead of of configure. You can pass the same options to the
Expand Down