From: Richard Moore <me@ricmoo.com>
To: crossgcc@sourceware.org
Subject: Using Emscripten?
Date: Sun, 13 Aug 2023 21:58:52 -0400 [thread overview]
Message-ID: <4E963AD5-239E-4E7D-922B-03C0C2EA32E3@ricmoo.com> (raw)
Hi all!
I’ve been trying to figure out how to configure CC and CXX for the “internal” build (meta build?), or possible make a custom host?
In a nutshell, the goal is to create the dev tools as a bunch of emscripten (using emcc) blobs that I can string together with JavaScript wrappers so that I can compile C to RISC-V in JavaScript, both in the browser and in node, for a platform-independent build system.
I’ve been working with the Espressif fork thus far, since that is what the final target will be; write C in your browser and deploy directly to an ESP32-C3 from the browser.
I’ve tried changing the CT_CC to emcc (from gcc) without luck. Any guidance or suggestions would be greatly appreciated.
Thanks! :)
RicMoo
Sent from my self-aware iPhone
.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>
Richard Moore ~ Founder
Genetic Mistakes Software Inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes.com
www: http://GeneticMistakes.com
reply other threads:[~2023-08-14 1:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E963AD5-239E-4E7D-922B-03C0C2EA32E3@ricmoo.com \
--to=me@ricmoo.com \
--cc=crossgcc@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).