From: Jean-Pierre De Jesus Diaz <jean@foundation.xyz>
To: 73277@debbugs.gnu.org
Cc: manolis837@gmail.com
Subject: [bug#73277] [PATCH 1/2] gnu: Add mipsel-none-elf-toolchain variant.
Date: Mon, 16 Sep 2024 12:00:17 +0000 [thread overview]
Message-ID: <CAG1gdUoivp3tRQKiMWqAQWb90VnkO0tQpskQKmbOk-3Qo2a40g@mail.gmail.com> (raw)
In-Reply-To: <7c35f8694833a9371d84c51ce4a07119358e187e.1726426231.git.manolis837@gmail.com>
Hello,
Just letting you know that using `cross-gcc-toolchain` is preferred
and since the usage
is to provide a PS1 SDK I think you can add this to the list of bare
metal targets in Guix.
See `guix build --list-targets', for example it contains avr,
xtensa-ath9k-elf and or1k-elf.
This can be done by adding a variable to:
- `guix/platforms/mips.scm'
So, this should allow to add this target as an argument to your
`psn00bsdk' package:
For example:
(arguments
(list #:target "mipsel-none-elf"
...))
And the build system will:
1. Automayically add the cross-gcc compiler.
2. Will also cross-compile inputs (excluding native-inputs, of course).
So that will allow you to unbundle the dependencies as you could just build
each one independently for that target (or for all ones, if the
library supports it).
With this though you'll probably need to create a separate package for
the tools and
one for the code that runs on the PS1 itself.
You can take inspiration from the existing bare-metal targets and
packages compiled
like this (which are few), there is firmware on
`gnu/packages/firmware.scm' that does
this. Also the QMK firmware for keyboards use the Guix
cross-compilation mechanism
too.
Additionally, you can provide the toolchain as a package on the
`gnu/package/cross-toolchain.scm` module.
prev parent reply other threads:[~2024-09-16 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 19:03 [bug#73277] [PATCH 1/2] gnu: Add mipsel-none-elf-toolchain variant manolis837
2024-09-15 19:03 ` [bug#73278] [PATCH 2/2] gnu: Add ps1 homebrew development kit manolis837
2024-09-15 19:09 ` Liliana Marie Prikler
2024-09-16 12:00 ` Jean-Pierre De Jesus Diaz [this message]
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=CAG1gdUoivp3tRQKiMWqAQWb90VnkO0tQpskQKmbOk-3Qo2a40g@mail.gmail.com \
--to=jean@foundation.xyz \
--cc=73277@debbugs.gnu.org \
--cc=manolis837@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.