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

Geschlossen
geöffnet vor 3 Monaten von Ghost · 2 Kommentare
Ghost hat vor 3 Monaten kommentiert

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
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 hat sich das Issue vor 3 Monaten selbst zugewiesen
damien hat vor 3 Monaten kommentiert
Ersteller
Besitzer

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.

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.
Ghost hat vor 3 Monaten kommentiert
Ersteller

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.

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 hat diesen Issue vor 3 Monaten geschlossen
Anmelden, um an der Diskussion teilzunehmen.
Kein Label
Kein Meilenstein
Niemand zuständig
2 Beteiligte
Nachrichten
Fällig am

Kein Fälligkeitsdatum gesetzt.

Abhängigkeiten

Dieses Issue hat momentan keine Abhängigkeiten.

Laden…
Hier gibt es bis jetzt noch keinen Inhalt.