Hey,
I have an ubuntu 64 bits, so I have to compile myself cegcc (the cegcc and
mingw32ce tools).
I have remarked that in build-mingw32ce.sh, the target
"arm-wince-mingw32ce" has been commented and replaced by "arm-mingw32ce"
(lines 436 and 437)
The problem is that some tools (in trunk/tools
I assume they call WCETRACEGETENV() as a first call in the main() function.
I gave up and called WCETRACESET(WCE_ALL) in my program. But it seems
to me that cegcc prologue code, or library init code should call
WCETRACEGETENV() to allow tracing of arbitrary programs without
modifying them, and also
On Tue, 2008-09-02 at 14:47 +0200, Vincent Torri wrote:
> Hey,
>
> as windows ce does not support environment variables, is it normal that
> putenv and unsetenv are in arm-wince-cegcc/include/stdlib.h ?
In our newlib implementation, these functions are present. So they
should be in that include
Maybe the (ush) setenv command did what the ush tools expect, but not
what our newlib expects ?
Danny
On Tue, 2008-09-02 at 23:03 -0700, Pawel Veselov wrote:
> Hi !
>
> I'm really sorry, but I can't any meaningful source on how to
> make tracing print what it suppose to print... I'm usin
On Wed, Sep 3, 2008 at 11:37 AM, Danny Backx <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-09-02 at 18:41 -0700, Pawel Veselov wrote:
>> Hi,
>>
>> I was looking at sys directory in newlib libc, and it seems
>> that stuff like "io.h" doesn't really belong there. The headers
>> get exported into public i
On Tue, 2008-09-02 at 18:41 -0700, Pawel Veselov wrote:
> Hi,
>
> I was looking at sys directory in newlib libc, and it seems
> that stuff like "io.h" doesn't really belong there. The headers
> get exported into public include/sys directory, and io.h contains
> definitions for internal functions,
Hi,
Pedro always referred to gdbserver, I never got a chance to play with
that. My new iPAQ urged me to try it, because I don't have synce to
provide a connection to it. (I don't feel like connecting it via the USB
cable - the wireless connection should do the trick.)
Anyway, I took gdb 6.8 from
Hello,
> Jerome Decoodt found a workaround to get applications working on Windows
> Mobile 6.1.
> It seems that you can ask system not to load DLL in high memory :
I precise this is just a workaround/ugly hack because DLL will probably
be loaded in Slots 0&1 instead of slots > 60, so you'll not
Good news!
Jerome Decoodt found a workaround to get applications working on Windows
Mobile 6.1.
It seems that you can ask system not to load DLL in high memory :
Danny could please update FAQ and add something like :
19. I get an "Invalid Pocket PC application" when I try to run my program
on W
