Skip to content
This repository has been archived by the owner on Jan 26, 2019. It is now read-only.

More detailed instructions on building from source #85

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

Conversation

seanthegeek
Copy link

  • Adds specific ./configure options for building on Debian/Ubuntu
  • Adds instructions for using checkinstall to install a source build as a deb/RPM package
  • Adds commands for installing autoconf, automake, and libtool

Sean Whalen added 2 commits December 18, 2017 11:46
- Adds specific `./configure` options for building on Debian/Ubuntu
- Adds instructions for using `checkinstall` to install a source build as a deb/RPM package
- Adds commands for installing `autoconf`, `automake`, and `libtool`
Copy link
Contributor

@horgh horgh left a comment

Choose a reason for hiding this comment

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

Hi @seanthegeek! Thanks for contributing! I have a few small suggestions.

Then, configure the build build. The `configure` script takes the standard options to set where files are
installed such as `--prefix`, etc. See `./configure --help` for details.

On Debain/Ubuntu a few options need to be passed:
Copy link
Contributor

Choose a reason for hiding this comment

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

There is a minor typo in Debian here.


On Debain/Ubuntu a few options need to be passed:

$ ./configure --prefix=/usr --bindir=/usr/sbin --sysconfdir=/etc --sharedstatedir=/usr/share --localstatedir=/var --mandir=/usr/share/man
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, do we need to specify all of these on Debian/Ubuntu? Normally I go with the defaults. I think it's really dependent on how one wants to install it on one's system. As such, it might be more appropriate leaving this at simply ./configure for Debian/Ubuntu/Centos/RHEL, and point to the options provided by ./configure --help to adjust the paths.

We could say something more about what paths there are to configure, or what the defaults usually are on a particular system, if that would be helpful.

$ make
$ sudo make install

To install the freshly-built program as a package, you can use `checkinstall`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Neat idea! I'm a bit leery of having a suggested packaging method in the main instructions though. It can be a big topic on its own! What do you think about having the package part in a separate section, and referring to it as an alternative to sudo make install? For example, a ## Creating a package section might work.


## Installing From GitHub

To install from Git, you will need automake, autoconf, and libtool installed.
To install from Git, you will need `autoconf`,`automake`, and `libtool` installed.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we might want to add a space between "autoconf," and "automake"

To install from Git, you will need automake, autoconf, and libtool installed.
To install from Git, you will need `autoconf`,`automake`, and `libtool` installed.

On Debain/Ubuntu, run:
Copy link
Contributor

Choose a reason for hiding this comment

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

There is a similar typo here

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

Successfully merging this pull request may close these issues.

2 participants