From: bugzilla-daemon@ecoscentric.com
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1000740] Public Domain Curses for eCos
Date: Tue, 05 May 2009 16:19:00 -0000 [thread overview]
Message-ID: <20090505161931.DA3FF3B40030@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1000740-104@http.bugs.ecos.sourceware.org/>
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000740
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Extra Info|--- |REQUESTED
Ever Confirmed|0 |1
--- Comment #8 from John Dallaway <john@dallaway.org.uk> 2009-05-05 17:19:30 ---
So far, I have seen output from the "tuidemo" and "firework" demos. I can
navigate the menus and the fireworks are recognisable.
Sergei, correct operation of the demos seems to be dependent on resetting
minicom between each demo. Otherwise, no output is observed. Have you seen this
behaviour?
I am using eCos target pc_i82559 and minicom in VT102 mode.
A few comments so far:
The following CDL options need CDL "description" strings and should be "flavor
bool", not "flavor data":
CYGDAT_PDCURSES_DRIVER_USE_KEYPAD_KEYS
CYGDAT_PDCURSES_DRIVER_USE_ANSI_COLORS
CYGDAT_PDCURSES_DRIVER_USE_VT100_ATTR
I think it would be preferable (and more consistent with other eCos packages)
to build the demo programs as eCos tests under the control of the
CYGBLD_PDCURSES_DEMOS option. Something like this should work (untested):
cdl_option CYGPKG_PDCURSES_TESTS {
display "PDCurses tests"
no_define
flavor data
calculated { CYGBLD_PDCURSES_DEMOS ? src/demos/xmas src/demos/... : "" }
}
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
next prev parent reply other threads:[~2009-05-05 16:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 18:55 [Bug 1000740] New: " bugzilla-daemon
2009-04-28 12:33 ` [Bug 1000740] " bugzilla-daemon
2009-04-28 13:46 ` bugzilla-daemon
2009-04-28 16:03 ` bugzilla-daemon
2009-04-28 16:21 ` bugzilla-daemon
2009-05-05 12:02 ` bugzilla-daemon
2009-05-05 15:38 ` bugzilla-daemon
2009-05-05 16:14 ` bugzilla-daemon
2009-05-05 16:19 ` bugzilla-daemon [this message]
2009-05-05 16:43 ` Sergei Gavrikov
2009-05-05 20:28 ` Sergei Gavrikov
2009-05-05 19:28 ` bugzilla-daemon
2009-05-05 19:31 ` bugzilla-daemon
2009-05-05 19:53 ` bugzilla-daemon
2009-05-06 8:34 ` bugzilla-daemon
2009-05-08 13:19 ` bugzilla-daemon
2009-05-08 13:27 ` bugzilla-daemon
2009-05-08 14:01 ` bugzilla-daemon
2009-05-08 14:08 ` bugzilla-daemon
2009-05-08 14:21 ` bugzilla-daemon
2009-05-08 14:34 ` bugzilla-daemon
2009-05-08 14:41 ` bugzilla-daemon
2009-05-08 20:06 ` bugzilla-daemon
2009-05-08 20:28 ` bugzilla-daemon
2009-05-09 16:55 ` bugzilla-daemon
2009-05-09 17:12 ` bugzilla-daemon
2009-05-10 8:34 ` bugzilla-daemon
2009-05-10 8:39 ` bugzilla-daemon
2009-06-13 8:15 ` bugzilla-daemon
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=20090505161931.DA3FF3B40030@mail.ecoscentric.com \
--to=bugzilla-daemon@ecoscentric.com \
--cc=ecos-patches@ecos.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).