Skip to content
Snippets Groups Projects

added compilation instructions

Closed added compilation instructions
update_readme into main
4 unresolved threads
Closed Etor Lucio Eceiza requested to merge update_readme into main
4 unresolved threads

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
README.md
9 9 appropriate binary from the latest release for your OS and architecture (currently only x86_64 Linux is built
10 10 automatically), unzip the download, and place the binary in your `PATH`.
11 11
12 ## Compilation of the `freva-ingest` binary
13
14 In order to locally compile the binary you will need Rust's package manager
15 [cargo installed previously](https://doc.rust-lang.org/cargo/getting-started/installation.html).
16 Then, simply clone this repo and:
17
18 - for development: `make build`. The `freva-ingest` binary will be placed in `./target/debug/freva-ingest`.
  • G
    Ghost User @ghost ·
    Contributor

    I don't think these instructions are necessary and I kind of wonder why I added a make build target at all when cargo build is one character longer. This being a rust project, the output directory will be well known so doesn't need to be mentioned.

  • Please register or sign in to reply
  • Ghost User @ghost started a thread on the diff
    • README.md
    9 9 appropriate binary from the latest release for your OS and architecture (currently only x86_64 Linux is built
    10 10 automatically), unzip the download, and place the binary in your `PATH`.
    11 11
    12 ## Compilation of the `freva-ingest` binary
    13
    14 In order to locally compile the binary you will need Rust's package manager
    15 [cargo installed previously](https://doc.rust-lang.org/cargo/getting-started/installation.html).
  • Ghost User @ghost started a thread on the diff
    • README.md
    9 9 appropriate binary from the latest release for your OS and architecture (currently only x86_64 Linux is built
    10 10 automatically), unzip the download, and place the binary in your `PATH`.
    11 11
    12 ## Compilation of the `freva-ingest` binary
    13
    14 In order to locally compile the binary you will need Rust's package manager
    15 [cargo installed previously](https://doc.rust-lang.org/cargo/getting-started/installation.html).
    16 Then, simply clone this repo and:
    17
    18 - for development: `make build`. The `freva-ingest` binary will be placed in `./target/debug/freva-ingest`.
    19 - for production: `make release` for an optimized compilation. The `freva-ingest` binary will be placed in
    • G
      Ghost User @ghost ·
      Contributor

      This can be done with cargo install --path freva-ingest --locked which will also put it in the binary directory that was created during rustup's installation meaning no need to move it around afterwards.

    • Please register or sign in to reply
  • Ghost User @ghost started a thread on the diff
    • README.md
    9 9 appropriate binary from the latest release for your OS and architecture (currently only x86_64 Linux is built
    10 10 automatically), unzip the download, and place the binary in your `PATH`.
    11 11
    12 ## Compilation of the `freva-ingest` binary
  • G
    Ghost User @ghost ·
    Contributor

    I'll take another crack at getting a statically linked version built so we stop having to do that. In general, I would prefer if we can avoid recommending people to build this from source and this should be unnecessary on most systems running recentish kernels.

  • K
    Etor Lucio Eceiza @k204229 ·
    Author Owner

    Sure, what you comment makes total sense. Thanks for taking the time

  • Etor Lucio Eceiza closed

    closed

  • Etor Lucio Eceiza reopened

    reopened

  • Etor Lucio Eceiza closed

    closed

    • Please register or sign in to reply

    Imprint | Privacy Policy