RECESSIM

Gr-smart meters Setup on other distros: Difference between revisions

← Older editNewer edit →
VisualWikitext
→Arch: added detail about the proper use of sudo if required.
reorganized structure of page to put only distro-specific things under each distro heading.
Line 1: Line 1:
The [[Gr-smart meters Setup Guide]] describes how to build the gr-smart meters setup on Ubuntu.  This page documents how to do so on other Linux distributions.  Note that the patches applied (<code>pull_23</code> for <code>gr-pdu_utils</code> and <code>pull_9</code> for <code>gr-timing_utils</code>) apply pull requests that have not yet been accepted into the respective Sandia Labs repositories.  If and when they are ever merged into the main line code, these patches will no longer be necessary.  Also note that with these patches applied, it is no longer necessary to build or use the <code>gr-sandia_utils</code> code.
The [[Gr-smart meters Setup Guide]] describes how to build the gr-smart meters setup on Ubuntu.  This page documents how to do so on other Linux distributions.  Note that the patches applied (<code>pull_23</code> for <code>gr-pdu_utils</code> and <code>pull_9</code> for <code>gr-timing_utils</code>) apply pull requests that have not yet been accepted into the respective Sandia Labs repositories.  If and when they are ever merged into the main line code, these patches will no longer be necessary.  Also note that with these patches applied, it is no longer necessary to build or use the <code>gr-sandia_utils</code> code.


== Arch ==
For each distribution below, what is shown is a container file (for use with Docker or Podman) that shows how to build the relevant modules within a container based on the relevant distro.  This is done to both make it absolutely clear which steps need to be done and which order, and also to provide a convenient way to test and these recipes to other Linux distributions.
This is a container file (for use with Docker or Podman) that shows how to build the relevant modules under Arch Linux.


<syntaxhighlight lang="docker">
To run these commands on a real distribution (that is, not in a container), you can simply execute each "RUN" command exactly as it appears and then substitute `cd` commands for the "WORKDIR" lines (or use <code>pushd</code>/<code>popd</code> pairs as shown in the example below).  You can ignore the "FROM" line.  You will want to adjust the directories for your own computer.  So for example, for Arch could use the following commands:
FROM archlinux:base-20240101.0.204074
RUN mkdir -p /tmp/work
WORKDIR /tmp/work
RUN pacman --noconfirm -Sy git make cmake gcc gnuradio boost doxygen graphviz pybind11
RUN git clone https://github.com/sandialabs/gr-pdu_utils.git
RUN git clone https://github.com/sandialabs/gr-timing_utils.git
RUN git clone https://github.com/sandialabs/gr-fhss_utils.git
RUN for fn in * ; do pushd $fn && git checkout maint-3.10 && popd ; done
WORKDIR /tmp/work/gr-pdu_utils
RUN git fetch origin refs/pull/23/head:pull_23
RUN git checkout pull_23
RUN cmake -B build && cmake --build build -t install
WORKDIR /tmp/work/gr-timing_utils
RUN git fetch origin refs/pull/9/head:pull_9
RUN git checkout pull_9
RUN cmake -B build && cmake --build build -t install
WORKDIR /tmp/work/gr-fhss_utils
RUN cmake -B build && cmake --build build -t install
</syntaxhighlight>
 
To run these commands on a real distribution (that is, not in a container), you can simply execute each "RUN" command exactly as it appears and then substitute `cd` commands for the "WORKDIR" lines (or use <code>pushd</code>/<code>popd</code> pairs as shown in the example below).  You can ignore the "FROM" line.  You will want to adjust the directories for your own computer.  So for example, one could use the following commands:


<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
Line 62: Line 40:


It's recommended to build an ordinary user and only use <code>sudo</code> for installing, as shown above. To speed up compiling on multicore machines, you can append <code>-j</code> to build commands as in <code>cmake --build build -j</code>.
It's recommended to build an ordinary user and only use <code>sudo</code> for installing, as shown above. To speed up compiling on multicore machines, you can append <code>-j</code> to build commands as in <code>cmake --build build -j</code>.
These notes generally apply to all of the distributions listed below.
== Arch ==
<syntaxhighlight lang="docker">
FROM archlinux:base-20240101.0.204074
RUN mkdir -p /tmp/work
WORKDIR /tmp/work
RUN pacman --noconfirm -Sy git make cmake gcc gnuradio boost doxygen graphviz pybind11
RUN git clone https://github.com/sandialabs/gr-pdu_utils.git
RUN git clone https://github.com/sandialabs/gr-timing_utils.git
RUN git clone https://github.com/sandialabs/gr-fhss_utils.git
RUN for fn in * ; do pushd $fn && git checkout maint-3.10 && popd ; done
WORKDIR /tmp/work/gr-pdu_utils
RUN git fetch origin refs/pull/23/head:pull_23
RUN git checkout pull_23
RUN cmake -B build && cmake --build build -t install
WORKDIR /tmp/work/gr-timing_utils
RUN git fetch origin refs/pull/9/head:pull_9
RUN git checkout pull_9
RUN cmake -B build && cmake --build build -t install
WORKDIR /tmp/work/gr-fhss_utils
RUN cmake -B build && cmake --build build -t install
</syntaxhighlight>
Retrieved from "https://wiki.recessim.com/view/Gr-smart_meters_Setup_on_other_distros"