unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Building an open source cross development chain
Date: Thu, 11 Feb 2016 02:01:11 +0100	[thread overview]
Message-ID: <87y4asysa0.fsf@debian.uxu> (raw)
In-Reply-To: 56BB4979.4010007@javaxpert.com

deadbrain <jerome@javaxpert.com> writes:

> Hi all, I'd like to know if someone succeed in
> building a full open source development chain around
> Emacs for embedded cross development(with
> gcc-arm-none-eabi cross compiler& deboger, openocd).
> Can you debog directly from Emacs ? All ideas are
> welcome...

What's the first link in a "full open source
development chain"? I think that is a natural place to
start... You can worry about "deboging" later.

In general, on a Unix system, there are files that can
execute and files that cannot. The files that can
execute can produce and modify the files that are
static.

With Emacs, you can write files that can turn into
files that can execute. When the files can execute,
you can use Emacs as an interface to have them execute
in different ways and on different targets.

So assuming your tools are Unix tools, then *yes*, you
can operate them completely from Emacs.

And I really think you are onto something because that
is also the best way to operate things :)

-- 
underground experts united
http://user.it.uu.se/~embe8573




      reply	other threads:[~2016-02-11  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 14:30 Building an open source cross development chain deadbrain
2016-02-11  1:01 ` Emanuel Berg [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4asysa0.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.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).