From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Building Docker Containers
Date: Sun, 29 Mar 2020 13:51:12 -0700
Message-ID: <09CE786B-DB06-49FE-88F1-AD2316DC25BA@getmailspring.com> (raw)
In-Reply-To: <CAC2bXD4P_1ZONMmqQ+tc92JiOTB4JHVW96akVwDvtZgX+HWvvg@mail.gmail.com>
On Mar 29 2020, at 1:02 pm, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Sun, Mar 29, 2020, 12:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>> it would be good to have Makefiles and/or install.sh scripts and other
>> automated install things which can be called by people setting up from
>> scratch.
>
> The gitlab CI can be set up such that it just runs the install script, if
> needed. currently, the script is short enough that I don't think that's
> necessary.
> The install script and/or gitlab CI just runs the required make, setup.py,
> and/or cargo build commands.
>
> Jacob
Luke, I'm doing this on the Kazan gitlab in the libre-soc-dev-env-setup
repository
(https://salsa.debian.org/Kazan-team/libre-soc-dev-env-setup). I'm
planing on making many smaller scripts that each do only one spefic
thing (eg. install yosys, install all general software prereqs from apt,
etc.). These scripts can then be combined as needed for specific
purposes/set-ups. I will write the basic use cases as these
purpose-specific aggregations, specifically the entirety of the HDL
workflow setup.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 13:48 Immanuel, Yehowshua U
2020-03-29 15:26 ` Luke Kenneth Casson Leighton
2020-03-29 16:03 ` Immanuel, Yehowshua U
2020-03-29 16:14 ` Luke Kenneth Casson Leighton
2020-03-29 16:19 ` Immanuel, Yehowshua U
2020-03-29 16:24 ` Luke Kenneth Casson Leighton
2020-03-29 17:21 ` Jacob Lifshay
2020-03-29 18:48 ` Luke Kenneth Casson Leighton
2020-03-29 18:59 ` Jacob Lifshay
2020-03-29 19:33 ` Immanuel, Yehowshua U
2020-03-29 19:56 ` Jacob Lifshay
2020-03-29 19:57 ` Luke Kenneth Casson Leighton
2020-03-29 20:02 ` Jacob Lifshay
2020-03-29 20:51 ` Cole Poirier [this message]
2020-03-29 21:12 ` Luke Kenneth Casson Leighton
2020-03-29 21:34 ` Cole Poirier
2020-03-30 8:59 ` Luke Kenneth Casson Leighton
2020-03-30 18:13 ` Jacob Lifshay
2020-03-30 18:43 ` Cole Poirier
2020-03-30 18:58 ` Luke Kenneth Casson Leighton
2020-03-30 19:08 ` Jacob Lifshay
2020-03-30 19:31 ` Cole Poirier
2020-03-29 16:19 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09CE786B-DB06-49FE-88F1-AD2316DC25BA@getmailspring.com \
--to=colepoirier@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git