From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sdcc: enable cross and add nonfree build option.
Date: Mon, 20 Jul 2020 05:57:27 +0200 [thread overview]
Message-ID: <20200720035727.DDIXvQB3HO5aKjwx2JCX9hAHN9lMuiToPfH0LCs5WbY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22784@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
There's a merged pull request on the void-packages repository
sdcc: enable cross and add nonfree build option.
https://github.com/void-linux/void-packages/pull/22784
Description:
- Enabling cross is done by disabling building the device libraries
during packaging.
- Some PIC headers and files are nonfree, so they shouldn't be
included in the free version.
- Add gc-devel for better memory behavior.
So, it doesn't automatically build a device lib if it needs one, which means it's a bit useless in this state (I think). Should we ship it in this state? The example I've found online for cross compiling uses the native builder to create the libraries and then copies that over.
https://github.com/ekawahyu/sdcc-CC2530/blob/master/sdcc-build-for-windows-from-osx.sh
parent reply other threads:[~2020-07-20 3:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22784@inbox.vuxu.org>]
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=20200720035727.DDIXvQB3HO5aKjwx2JCX9hAHN9lMuiToPfH0LCs5WbY@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).