Re: printf from application not displayed in target control
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 28 Aug 2008 08:24:53 -0700
If the device has user interface, I'd be inclined to build a windowed
application, not a command-line one, especially for Windows Mobile. In that
case, you don't need to connect with Platform Builder or anything else; you
simply need to copy the test to the device, or run it from a storage card
plugged into the device. Much less-intrusive (and less likely to give
different results in the real usage and when running the test).
Paul T.
"Gammaraman" <Gammaraman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D92291B-E952-4F42-B366-39A4B0A1DC3D@xxxxxxxxxxxxxxxx
Thanks, Paul.
Actually I think I can live with the DEBUGMSG as this is just for testing
purposes. It is just the clutter which makes it difficult to see messages
of
interest but it is not that bad :)
Regarding what I am trying to do, I am exposing some custom OIDs from my
miniport driver and want to develop a test application which can exercise
this custom functionality.
"Paul G. Tobey [eMVP]" wrote:
So, you are a Windows Mobile device OEM? I don't know what's available
for
that (and discussion of the adaptation kit is not allowed in public
forums
such as this, as I understand it). There could be something specific to
Windows Mobile for that, but, no, generally not.
What are you actually trying to do? I mean, this isn't a production
operation anyway. What's wrong with DEBUGMSG? Or logging the result to
a
file? Or sending it out a serial port or over the network? You could do
any of those by just providing your own functions, rather than printf(),
to
use.
Paul T.
"Gammaraman" <Gammaraman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3064EE90-6C82-4834-82F8-54EA2CAD51F8@xxxxxxxxxxxxxxxx
Thank you Paul. I will be sure not to be so vague in the future.
I am using Platform Builder for WinCE 5 to talk to a device running
WinMob
6.1.
I could use the RETAILMSG/DEBUGMSG mechanism to display messages in
Platform
Builder over KITL but I am looking for a way to have these messages be
displayed on the target control shell where I am invoking the
application
from. Is this possible?
Thanks.
"Paul G. Tobey [eMVP]" wrote:
No, it won't do that. The output will go to standard I/O which, if
you
included the console (Command Processor/Console Window in the CE5
catalog),
will cause that output to go to a new window on the screen of the
device,
just like it would do if you were running a DOS program on a PC. If
your
OS
does not include the console components, the output goes into the
ether,
I
think.
Take a look at this page to make sure that you put the necessary
information
in your question that we need to answer it (what's the OS version, for
example?), for future reference:
http://guruce.com/blogpost/howtoaskquestionsonnewsgroups
Paul T.
"Gammaraman" <Gammaraman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9942172E-B746-473B-983D-E269B12F960F@xxxxxxxxxxxxxxxx
I am running an application from the target control shell in Platform
Builder
like this
s app_name
the app is trivial and simply does a printf of say hello world but I
do
not
see this displayed in the shell. Where is this output going? Do I
need
to
set
something up for it to show in the shell windows?
Thanks.
.
- Follow-Ups:
- Re: printf from application not displayed in target control
- From: Gammaraman
- Re: printf from application not displayed in target control
- References:
- printf from application not displayed in target control
- From: Gammaraman
- Re: printf from application not displayed in target control
- From: Gammaraman
- Re: printf from application not displayed in target control
- From: Gammaraman
- printf from application not displayed in target control
- Prev by Date: Re: How to copy Hive based registry into CF?
- Next by Date: Re: How to copy Hive based registry into CF?
- Previous by thread: Re: printf from application not displayed in target control
- Next by thread: Re: printf from application not displayed in target control
- Index(es):
Relevant Pages
|