From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Re: Synth target spawning external processes
Date: Mon, 17 Oct 2011 21:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1110172344410.14302@vostro> (raw)
In-Reply-To: <4E9C9032.40703@intefo.ch>
On Mon, 17 Oct 2011, Simon Kallweit wrote:
> Hello
>
> I was wondering if anyone has written some Tcl/Tk code to spawn
> external processes when running the synth target. We currently have a
> few external processes to simulate a GPS receiver among other things.
> These processes are currently started independent of ecossynth and
> need to be up and running when starting the application. This works,
> but it'd be nicer to automatically spawn these processes when the
> application is started, especially when doing so from the debugger. I
> think I'll wrap something up unless there is already a solution out
> there which I can build upon.
Hi Simon,
If I understood you correctly that one (lazy) way is to use ecos target
definition files (.tdf files). You can put Tcl code there (= what you
need).
My brief test was
% cat >test.tdf<<EOF
exec notify-send Hello &
exec gksudo &
puts hello
EOF
% watchdog2 -io -t test.tdf
and it worked as I could expect. I saw/got all things.
Well, it looks like a hack. But, as I said that is one and lazy way to
get the needed things in Tcl/Tk (=quickly).
Also, IMO, the same things can be done through .gdbinit.
HTH
Sergei
>
> Best regards,
> Simon
>
prev parent reply other threads:[~2011-10-17 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 20:29 Simon Kallweit
2011-10-17 21:29 ` Sergei Gavrikov [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=alpine.DEB.2.00.1110172344410.14302@vostro \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=simon.kallweit@intefo.ch \
/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).