#2 It would be nice to have a COMPILING document with directions on the dependencies

Closed

opened 5 months ago by Ghost · 2 comments

I had to stumble on somebody's comments on another project listing a similar error to the one I had gotten to find the right set of steps.

I've tested a similar set of steps in a Dockerfile that worked well, but wasn't sure how familiar people would be with using a container to compile software for their host system.

sudo apt update && apt install -y --no-install-recommends \
        ca-certificates \
        gnupg \
        autoconf \
        automake \
        build-essential \
        libtool \
        shtool  \
        libgcrypt20-dev \
        libassuan-dev \
        libgpg-error-dev \
        git

git clone https://git.incenp.org/damien/scdtools.git
cd scdtools

autoreconf --install && \
    ./configure && \
    make && \
    sudo make install

damien self-assigned this 5 months ago

I can explicitly mention the dependencies on the README. I didn’t do that because I had assumed it was obvious the project was dependent on GnuPG and its libraries.

Yeah, the dependencies weren't too hard to find since someone created a Gentoo ebuild that listed out the libassuan and libgcrypt. It was the autoconf/libtool/shtool requirements and invocations that were sneaky since it had been a while since I built a project from scratch.

damien referenced this issue from a commit 5 months ago

Add install instructions. Add the autoconf-provided INSTALL file containing generic instructions about how to use the Autotools. Also explicitly list the required libraries in the README file. Closes #2

damien closed this issue 5 months ago

No Label

No Milestone

damien

2 Participants

Notifications

Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.