Re: [Cegcc-devel] Compiling for PocketPC 2000

View: New views
20 Messages — Rating Filter:   Alert me  
< Prev | 1 - 2 | Next >

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
That sounds like a logical approach.  I'll follow up on it.

Rob

----- Original Message -----
From: "Max Kellermann" <max@...>
To: <rob@...>
Sent: Friday, September 18, 2009 12:55 PM
Subject: Re: [Cegcc-devel] Compiling for PocketPC 2000


> On 2009/09/18 17:37, Danny Backx <danny.backx@...> wrote:
>> On Fri, 2009-09-18 at 01:24 +0200, Max Kellermann wrote:
>> > Hi cegcc folks,
>> >
>> > I'm a new developer on the XCSoar project (www.xcsoar.org).  We try to
>> > support all PocketPC versions.  The fellow developer who maintains the
>> > XCSoar PPC2000 port claims that cegcc cannot produce binaries for that
>> > platform.  This forces us to use EVC, including all the pain attached
>> > to that.
>> >
>> > Is that correct?  Is that a known limitation?
>>
>> Not known to me.
>
> Hi Rob,
>
> what do you think about Danny's response?
>
>
>> > Unfortunately, I cannot test myself, because my only PDA runs Windows
>> > Mobile 5.
>>
>> "It doesn't work" is not a very informative claim.
>>
>> I see a few steps that we could take :
>> 1. Identify someone who can run a few tests.
>>    I assume that your co-developer would be willing to help?
>> 2. Get a very minimalistic test to work. Example : something
>>    that'll just pop up a dialog. One call in WinMain.
>> 3. Build from there.
>>
>> I have two things I suspect :
>> - either use of a DLL that's just not there
>> - or use of some function that's in our development images,
>>   but not in the DLL on that system
>>
>> The latter can be detected with a variant of my testapi program (see
>> under the tools directory in SVN) that we can tweak to run through the
>> whole set of expected APIs for e.g. coredll.
>>
>> Danny
>> --
>> Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Scott Penrose :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hey Guys

I have an old iPaq doing nothing, but up at Benalla. I should be up  
there in a few weeks time. I will grab it. It is running either Win  
CE3 or WinCE2 - not sure.

Scott


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Just subscribed to the xcsoar-devel to keep track on this, and because
my reply didn't make it on that list without help.

My first minimalistic program is this :
  #include <windows.h>

  int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
lpCmdLine, int nCmdShow)
  {
          MessageBoxW(0, L"HELLO!", L"H3LLO!", 0);
  }

I've compiled it with
  arm-mingw32ce-gcc -o d2a.exe d2.c
  arm-mingw32ce-gcc -s -o d2b.exe d2.c

Examining it shows that it uses more than just the one call :
  % arm-mingw32ce-objdump -x d2b.exe
  ...
        DLL Name: COREDLL
        vma:  Hint/Ord Member-Name Bound-To
        50b0      746  MessageBoxW
        50be      770  OutputDebugStringW
        50d4     1125  TerminateProcess
        50e8     1166  VirtualProtect
        50fa     1167  VirtualQuery
        510a     1274  _fcloseall
        5118     1282  _fpreset
        5124     1403  fflush
        512e     1420  free
        5136     1508  malloc
        5140     1509  mbstowcs
        514c     1512  memcpy
        5156     1557  realloc
        5160     1574  strlen
        516a     1642  wcslen
        5174     1657  wsprintfW
  ...

which indicates that it can probably be trimmed even more. Not going
that path right now though. Let's see if this works.

I've put up both executables at
  http://danny.backx.info/download/cegcc/d2a.exe
  http://danny.backx.info/download/cegcc/d2b.exe

They should both work (or both fail), because they're basically
identical.

If that works, then I'd like to use my testapi program, or a variation
of it, to figure out what the DLLs on your PDA offer.

What your DLLs offer should match the requirements of your development
environment, or you have a chance that applications that you build don't
work.

Examples of how to run this :
  % rcp testapi.exe ipaq:/temp/testapi.exe
  % rsh ipaq /temp/testapi coredll OutputDebugStringW
        coredll implements OutputDebugStringW (0x03F66A48)
  % rsh ipaq /temp/testapi coredll VirtualProtect
        coredll implements VirtualProtect (0x03F65C6C)

You may not have rcp and rsh so we may have to fiddle with the testapi
source to get things to work.
  http://danny.backx.info/download/cegcc/testapi.c
  http://danny.backx.info/download/cegcc/testapi.exe

  Danny


On Fri, 2009-09-18 at 21:59 +0000, rob@...
wrote:

> That sounds like a logical approach.  I'll follow up on it.
>
> Rob
>
> ----- Original Message -----
> From: "Max Kellermann" <max@...>
> To: <rob@...>
> Sent: Friday, September 18, 2009 12:55 PM
> Subject: Re: [Cegcc-devel] Compiling for PocketPC 2000
>
>
> > On 2009/09/18 17:37, Danny Backx <danny.backx@...> wrote:
> >> On Fri, 2009-09-18 at 01:24 +0200, Max Kellermann wrote:
> >> > Hi cegcc folks,
> >> >
> >> > I'm a new developer on the XCSoar project (www.xcsoar.org).  We
> try to
> >> > support all PocketPC versions.  The fellow developer who
> maintains the
> >> > XCSoar PPC2000 port claims that cegcc cannot produce binaries for
> that
> >> > platform.  This forces us to use EVC, including all the pain
> attached
> >> > to that.
> >> >
> >> > Is that correct?  Is that a known limitation?
> >>
> >> Not known to me.
> >
> > Hi Rob,
> >
> > what do you think about Danny's response?
> >
> >
> >> > Unfortunately, I cannot test myself, because my only PDA runs
> Windows
> >> > Mobile 5.
> >>
> >> "It doesn't work" is not a very informative claim.
> >>
> >> I see a few steps that we could take :
> >> 1. Identify someone who can run a few tests.
> >>    I assume that your co-developer would be willing to help?
> >> 2. Get a very minimalistic test to work. Example : something
> >>    that'll just pop up a dialog. One call in WinMain.
> >> 3. Build from there.
> >>
> >> I have two things I suspect :
> >> - either use of a DLL that's just not there
> >> - or use of some function that's in our development images,
> >>   but not in the DLL on that system
> >>
> >> The latter can be detected with a variant of my testapi program
> (see
> >> under the tools directory in SVN) that we can tweak to run through
> the
> >> whole set of expected APIs for e.g. coredll.
> >>
> >> Danny
> >> --
> >> Danny Backx ; danny.backx - at - scarlet.be ;
> http://danny.backx.info
> >
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________ Xcsoar-devel mailing list Xcsoar-devel@... https://lists.sourceforge.net/lists/listinfo/xcsoar-devel
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Parent Message unknown Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Danny, thanks for the reply.
 
The code you sent below works.  But, if I modify it to call the MessageBox function twice, it fails: it displays the first message box, but not the second.  It does not terminate the program properly either as there remains a file system lock on the .exe.  This is executed on Wince3.0 ARM ipaq 3600.
The compiler used is arm-mingw32ce 4.1.2 running on ubuntu.
 
int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
lpCmdLine, int nCmdShow)
 {
         MessageBoxW(0, L"HELLO!", L"H3LLO!", 0);
         MessageBoxW(0, L"HELL1!", L"H3LLO!", 0);   // does not execute second messagebox
 }

arm-mingw32ce-objdump returns:
...
 DLL Name: COREDLL
 vma:  Hint/Ord Member-Name Bound-To
 5078   741  MessageBoxW
 5086  1120  TerminateProcess
 509a  1269  _fcloseall
 50a8  1277  _fpreset
 50b4  1398  fflush
 50be  1415  free
 50c6  1503  malloc
 50d0  1552  realloc

I ran a hex dump on the executable and it contains the string COREDLL (as opposed to COREDLL.DLL). 
 
I had no luck w/ the testapi code you sent -- I attempted to modify it to output using messagbox, but ran into the same wall as before.  Not sure how to run it with rcp.
 
Rob
 
 
----- Original Message -----
From: "Danny Backx" <danny.backx@...>
To: <rob@...>
Sent: Saturday, September 19, 2009 4:08 AM
Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000

> Just subscribed to the xcsoar-devel to keep track on this, and because

> my reply didn't make it on that list without help.
>
> My first minimalistic program is this :
>  #include <windows.h>
>
>  int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
> lpCmdLine, int nCmdShow)
>  {
>          MessageBoxW(0, L"HELLO!", L"H3LLO!", 0);
>  }
>
> I've compiled it with
>  arm-mingw32ce-gcc -o d2a.exe d2.c
>  arm-mingw32ce-gcc -s -o d2b.exe d2.c
>
> Examining it shows that it uses more than just the one call :
>  % arm-mingw32ce-objdump -x d2b.exe
>  ...
>        DLL Name: COREDLL
>        vma:  Hint/Ord Member-Name Bound-To
>        50b0      746  MessageBoxW
>        50be      770  OutputDebugStringW
>        50d4     1125  TerminateProcess
>        50e8     1166  VirtualProtect
>        50fa     1167  VirtualQuery
>        510a     1274  _fcloseall
>        5118     1282  _fpreset
>        5124     1403  fflush
>        512e     1420  free
>        5136     1508  malloc
>        5140     1509  mbstowcs
>        514c     1512  memcpy
>        5156     1557  realloc
>        5160     1574  strlen
>        516a     1642  wcslen
>        5174     1657  wsprintfW
>  ...
>
> which indicates that it can probably be trimmed even more. Not going
> that path right now though. Let's see if this works.
>
> I've put up both executables at
http://danny.backx.info/download/cegcc/d2a.exe
http://danny.backx.info/download/cegcc/d2b.exe
>
> They should both work (or both fail), because they're basically
> identical.
>
> If that works, then I'd like to use my testapi program, or a variation
> of it, to figure out what the DLLs on your PDA offer.
>
> What your DLLs offer should match the requirements of your development
> environment, or you have a chance that applications that you build don't
> work.
>
> Examples of how to run this :
>  % rcp testapi.exe ipaq:/temp/testapi.exe
>  % rsh ipaq /temp/testapi coredll OutputDebugStringW
>        coredll implements OutputDebugStringW (0x03F66A48)
>  % rsh ipaq /temp/testapi coredll VirtualProtect
>        coredll implements VirtualProtect (0x03F65C6C)
>
> You may not have rcp and rsh so we may have to fiddle with the testapi
> source to get things to work.
http://danny.backx.info/download/cegcc/testapi.c
http://danny.backx.info/download/cegcc/testapi.exe
>
>  Danny
>
>
> On Fri, 2009-09-18 at 21:59 +0000, rob@...
> wrote:
>> That sounds like a logical approach.  I'll follow up on it.
>>
>> Rob
>>
>> ----- Original Message -----
>> From: "Max Kellermann" <max@...>
>> To: <rob@...>
>> Sent: Friday, September 18, 2009 12:55 PM
>> Subject: Re: [Cegcc-devel] Compiling for PocketPC 2000
>>
>>
>> > On 2009/09/18 17:37, Danny Backx <danny.backx@...> wrote:
>> >> On Fri, 2009-09-18 at 01:24 +0200, Max Kellermann wrote:
>> >> > Hi cegcc folks,
>> >> >
>> >> > I'm a new developer on the XCSoar project (www.xcsoar.org).  We
>> try to
>> >> > support all PocketPC versions.  The fellow developer who
>> maintains the
>> >> > XCSoar PPC2000 port claims that cegcc cannot produce binaries for
>> that
>> >> > platform.  This forces us to use EVC, including all the pain
>> attached
>> >> > to that.
>> >> >
>> >> > Is that correct?  Is that a known limitation?
>> >>
>> >> Not known to me.
>> >
>> > Hi Rob,
>> >
>> > what do you think about Danny's response?
>> >
>> >
>> >> > Unfortunately, I cannot test myself, because my only PDA runs
>> Windows
>> >> > Mobile 5.
>> >>
>> >> "It doesn't work" is not a very informative claim.
>> >>
>> >> I see a few steps that we could take :
>> >> 1. Identify someone who can run a few tests.
>> >>    I assume that your co-developer would be willing to help?
>> >> 2. Get a very minimalistic test to work. Example : something
>> >>    that'll just pop up a dialog. One call in WinMain.
>> >> 3. Build from there.
>> >>
>> >> I have two things I suspect :
>> >> - either use of a DLL that's just not there
>> >> - or use of some function that's in our development images,
>> >>   but not in the DLL on that system
>> >>
>> >> The latter can be detected with a variant of my testapi program
>> (see
>> >> under the tools directory in SVN) that we can tweak to run through
>> the
>> >> whole set of expected APIs for e.g. coredll.
>> >>
>> >> Danny
>> >> --
>> >> Danny Backx ; danny.backx - at - scarlet.be ;
>> http://danny.backx.info
>> >
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
>> http://p.sf.net/sfu/devconf
>> _______________________________________________ Xcsoar-devel mailing list Xcsoar-devel@... https://lists.sourceforge.net/lists/listinfo/xcsoar-devel
> --
> Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This is normal : MessageBoxW only returns when the user clicks that
dialog away.

So the first dialog appears, you need to act on it, it'll go away. Then
the second one appears, you act on it, then the program terminates.

Failure to do so will indeed lock the executable because it's still
running.

        Danny

On Sat, 2009-09-19 at 20:03 +0000, rob@...
wrote:

> Danny, thanks for the reply.
>  
> The code you sent below works.  But, if I modify it to call the
> MessageBox function twice, it fails: it displays the first message
> box, but not the second.  It does not terminate the program properly
> either as there remains a file system lock on the .exe.  This is
> executed on Wince3.0 ARM ipaq 3600.
> The compiler used is arm-mingw32ce 4.1.2 running on ubuntu.
>  
> int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
> lpCmdLine, int nCmdShow)
>  {
>          MessageBoxW(0, L"HELLO!", L"H3LLO!", 0);
>          MessageBoxW(0, L"HELL1!", L"H3LLO!", 0);   // does not
> execute second messagebox
>  }
>
>
> arm-mingw32ce-objdump returns:
> ...
>  DLL Name: COREDLL
>  vma:  Hint/Ord Member-Name Bound-To
>  5078   741  MessageBoxW
>  5086  1120  TerminateProcess
>  509a  1269  _fcloseall
>  50a8  1277  _fpreset
>  50b4  1398  fflush
>  50be  1415  free
>  50c6  1503  malloc
>  50d0  1552  realloc
>
>
> I ran a hex dump on the executable and it contains the string COREDLL
> (as opposed to COREDLL.DLL).  
>  
> I had no luck w/ the testapi code you sent -- I attempted to modify it
> to output using messagbox, but ran into the same wall as before.  Not
> sure how to run it with rcp.
>  
> Rob
>  
>  
> ----- Original Message -----
> From: "Danny Backx" <danny.backx@...>
> To: <rob@...>
> Cc: <max@...>; <xcsoar-devel@...>
> Sent: Saturday, September 19, 2009 4:08 AM
> Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000
>
>
> > Just subscribed to the xcsoar-devel to keep track on this, and
> because
> > my reply didn't make it on that list without help.
> >
> > My first minimalistic program is this :
> >  #include <windows.h>
> >
> >  int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
> > lpCmdLine, int nCmdShow)
> >  {
> >          MessageBoxW(0, L"HELLO!", L"H3LLO!", 0);
> >  }
> >
> > I've compiled it with
> >  arm-mingw32ce-gcc -o d2a.exe d2.c
> >  arm-mingw32ce-gcc -s -o d2b.exe d2.c
> >
> > Examining it shows that it uses more than just the one call :
> >  % arm-mingw32ce-objdump -x d2b.exe
> >  ...
> >        DLL Name: COREDLL
> >        vma:  Hint/Ord Member-Name Bound-To
> >        50b0      746  MessageBoxW
> >        50be      770  OutputDebugStringW
> >        50d4     1125  TerminateProcess
> >        50e8     1166  VirtualProtect
> >        50fa     1167  VirtualQuery
> >        510a     1274  _fcloseall
> >        5118     1282  _fpreset
> >        5124     1403  fflush
> >        512e     1420  free
> >        5136     1508  malloc
> >        5140     1509  mbstowcs
> >        514c     1512  memcpy
> >        5156     1557  realloc
> >        5160     1574  strlen
> >        516a     1642  wcslen
> >        5174     1657  wsprintfW
> >  ...
> >
> > which indicates that it can probably be trimmed even more. Not going
> > that path right now though. Let's see if this works.
> >
> > I've put up both executables at
> >  http://danny.backx.info/download/cegcc/d2a.exe
> >  http://danny.backx.info/download/cegcc/d2b.exe
> >
> > They should both work (or both fail), because they're basically
> > identical.
> >
> > If that works, then I'd like to use my testapi program, or a
> variation
> > of it, to figure out what the DLLs on your PDA offer.
> >
> > What your DLLs offer should match the requirements of your
> development
> > environment, or you have a chance that applications that you build
> don't
> > work.
> >
> > Examples of how to run this :
> >  % rcp testapi.exe ipaq:/temp/testapi.exe
> >  % rsh ipaq /temp/testapi coredll OutputDebugStringW
> >        coredll implements OutputDebugStringW (0x03F66A48)
> >  % rsh ipaq /temp/testapi coredll VirtualProtect
> >        coredll implements VirtualProtect (0x03F65C6C)
> >
> > You may not have rcp and rsh so we may have to fiddle with the
> testapi
> > source to get things to work.
> >  http://danny.backx.info/download/cegcc/testapi.c
> >  http://danny.backx.info/download/cegcc/testapi.exe
> >
> >  Danny
> >
> >
> > On Fri, 2009-09-18 at 21:59 +0000, rob@...
> > wrote:
> >> That sounds like a logical approach.  I'll follow up on it.
> >>
> >> Rob
> >>
> >> ----- Original Message -----
> >> From: "Max Kellermann" <max@...>
> >> To: <rob@...>
> >> Sent: Friday, September 18, 2009 12:55 PM
> >> Subject: Re: [Cegcc-devel] Compiling for PocketPC 2000
> >>
> >>
> >> > On 2009/09/18 17:37, Danny Backx <danny.backx@...> wrote:
> >> >> On Fri, 2009-09-18 at 01:24 +0200, Max Kellermann wrote:
> >> >> > Hi cegcc folks,
> >> >> >
> >> >> > I'm a new developer on the XCSoar project (www.xcsoar.org).
> We
> >> try to
> >> >> > support all PocketPC versions.  The fellow developer who
> >> maintains the
> >> >> > XCSoar PPC2000 port claims that cegcc cannot produce binaries
> for
> >> that
> >> >> > platform.  This forces us to use EVC, including all the pain
> >> attached
> >> >> > to that.
> >> >> >
> >> >> > Is that correct?  Is that a known limitation?
> >> >>
> >> >> Not known to me.
> >> >
> >> > Hi Rob,
> >> >
> >> > what do you think about Danny's response?
> >> >
> >> >
> >> >> > Unfortunately, I cannot test myself, because my only PDA runs
> >> Windows
> >> >> > Mobile 5.
> >> >>
> >> >> "It doesn't work" is not a very informative claim.
> >> >>
> >> >> I see a few steps that we could take :
> >> >> 1. Identify someone who can run a few tests.
> >> >>    I assume that your co-developer would be willing to help?
> >> >> 2. Get a very minimalistic test to work. Example : something
> >> >>    that'll just pop up a dialog. One call in WinMain.
> >> >> 3. Build from there.
> >> >>
> >> >> I have two things I suspect :
> >> >> - either use of a DLL that's just not there
> >> >> - or use of some function that's in our development images,
> >> >>   but not in the DLL on that system
> >> >>
> >> >> The latter can be detected with a variant of my testapi program
> >> (see
> >> >> under the tools directory in SVN) that we can tweak to run
> through
> >> the
> >> >> whole set of expected APIs for e.g. coredll.
> >> >>
> >> >> Danny
> >> >> --
> >> >> Danny Backx ; danny.backx - at - scarlet.be ;
> >> http://danny.backx.info
> >> >
> >>
> >>
> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry® Developer Conference in SF,
> CA
> >> is the only developer event you need to attend this year. Jumpstart
> your
> >> developing skills, take BlackBerry mobile applications to market
> and stay
> >> ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> >> http://p.sf.net/sfu/devconf
> >> _______________________________________________ Xcsoar-devel
> mailing list Xcsoar-devel@...
> https://lists.sourceforge.net/lists/listinfo/xcsoar-devel
> > --
> > Danny Backx ; danny.backx - at - scarlet.be ;
> http://danny.backx.info
> >
> >
>
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, 2009-09-19 at 20:03 +0000, rob@...
wrote:
> Danny, thanks for the reply.
>  
> The code you sent below works.

Rob,

Here is more stuff for you to play with.

I've extended my testapi.c and got it to read from and write into files.

I've now compiled it to run in \temp which I believe is a folder any
WinCE device has.

You can pick it up at
  http://danny.backx.info/download/cegcc/testapi2.c
  http://danny.backx.info/download/cegcc/testapi2.exe 
  http://danny.backx.info/download/cegcc/testapi.in.txt
  http://danny.backx.info/download/cegcc/testapi.out.txt

You'll need to put the exe file and the input file on \temp and then run
the exe. It'll create the output file.

The sample output file which I put up contains a few lines mentioning
APIs not implemented by the PDA's coredll, but my development system
does allow me to create executables that expect them :

pavilion: {270} fgrep does *.out.txt
coredll doesn't know about CloseAllDeviceHandles
coredll doesn't know about GetPrivateCallbacks
coredll doesn't know about SetWDevicePowerHandler
coredll doesn't know about SystemStarted
coredll doesn't know about ThreadAttachAllDLLs
coredll doesn't know about ThreadDetachAllDLLs
pavilion: {271}

BTW this is with an iPAQ 214 running Windows Mobile 6.0.

Can you try the same on your device ?

        Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Danny, great utility - thx.

It shows that the only proc that's not supported on wince3 that is
referenece in XCSoar-PPC2002.exe is to "InterlockedCompareExchange".
However, this function is not directly called anywhere in the source code.

This function is listed by the arm-mingw32ce-objdump command in both the
current, and also in the version 5.2.4 (before our current rewrite).  In
neither is it explicitly referenced in the source code.   Do you have any
suggestions about why it is present in the binary and will it cause problems
on platforms like wince3 that don't appear to support it?


Rob


----- Original Message -----
From: "Danny Backx" <danny.backx@...>
To: <rob@...>
Cc: <max@...>; <xcsoar-devel@...>
Sent: Sunday, September 20, 2009 4:49 AM
Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000


> On Sat, 2009-09-19 at 20:03 +0000, rob@...
> wrote:
>> Danny, thanks for the reply.
>>
>> The code you sent below works.
>
> Rob,
>
> Here is more stuff for you to play with.
>
> I've extended my testapi.c and got it to read from and write into files.
>
> I've now compiled it to run in \temp which I believe is a folder any
> WinCE device has.
>
> You can pick it up at
>  http://danny.backx.info/download/cegcc/testapi2.c
>  http://danny.backx.info/download/cegcc/testapi2.exe
>  http://danny.backx.info/download/cegcc/testapi.in.txt
>  http://danny.backx.info/download/cegcc/testapi.out.txt
>
> You'll need to put the exe file and the input file on \temp and then run
> the exe. It'll create the output file.
>
> The sample output file which I put up contains a few lines mentioning
> APIs not implemented by the PDA's coredll, but my development system
> does allow me to create executables that expect them :
>
> pavilion: {270} fgrep does *.out.txt
> coredll doesn't know about CloseAllDeviceHandles
> coredll doesn't know about GetPrivateCallbacks
> coredll doesn't know about SetWDevicePowerHandler
> coredll doesn't know about SystemStarted
> coredll doesn't know about ThreadAttachAllDLLs
> coredll doesn't know about ThreadDetachAllDLLs
> pavilion: {271}
>
> BTW this is with an iPAQ 214 running Windows Mobile 6.0.
>
> Can you try the same on your device ?
>
> Danny
> --
> Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Which version of xcsoar do I need to grab to reproduce this ?

        Danny

On Mon, 2009-09-21 at 11:19 -0400, Rob Dunning wrote:

> Danny, great utility - thx.
>
> It shows that the only proc that's not supported on wince3 that is
> referenece in XCSoar-PPC2002.exe is to "InterlockedCompareExchange".
> However, this function is not directly called anywhere in the source code.
>
> This function is listed by the arm-mingw32ce-objdump command in both the
> current, and also in the version 5.2.4 (before our current rewrite).  In
> neither is it explicitly referenced in the source code.   Do you have any
> suggestions about why it is present in the binary and will it cause problems
> on platforms like wince3 that don't appear to support it?
>
>
> Rob
>
>
> ----- Original Message -----
> From: "Danny Backx" <danny.backx@...>
> To: <rob@...>
> Cc: <max@...>; <xcsoar-devel@...>
> Sent: Sunday, September 20, 2009 4:49 AM
> Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000
>
>
> > On Sat, 2009-09-19 at 20:03 +0000, rob@...
> > wrote:
> >> Danny, thanks for the reply.
> >>
> >> The code you sent below works.
> >
> > Rob,
> >
> > Here is more stuff for you to play with.
> >
> > I've extended my testapi.c and got it to read from and write into files.
> >
> > I've now compiled it to run in \temp which I believe is a folder any
> > WinCE device has.
> >
> > You can pick it up at
> >  http://danny.backx.info/download/cegcc/testapi2.c
> >  http://danny.backx.info/download/cegcc/testapi2.exe
> >  http://danny.backx.info/download/cegcc/testapi.in.txt
> >  http://danny.backx.info/download/cegcc/testapi.out.txt
> >
> > You'll need to put the exe file and the input file on \temp and then run
> > the exe. It'll create the output file.
> >
> > The sample output file which I put up contains a few lines mentioning
> > APIs not implemented by the PDA's coredll, but my development system
> > does allow me to create executables that expect them :
> >
> > pavilion: {270} fgrep does *.out.txt
> > coredll doesn't know about CloseAllDeviceHandles
> > coredll doesn't know about GetPrivateCallbacks
> > coredll doesn't know about SetWDevicePowerHandler
> > coredll doesn't know about SystemStarted
> > coredll doesn't know about ThreadAttachAllDLLs
> > coredll doesn't know about ThreadDetachAllDLLs
> > pavilion: {271}
> >
> > BTW this is with an iPAQ 214 running Windows Mobile 6.0.
> >
> > Can you try the same on your device ?
> >
> > Danny
> > --
> > Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
> >
> >
>
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Max Kellermann :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 2009/09/21 19:59, Danny Backx <danny.backx@...> wrote:
> Which version of xcsoar do I need to grab to reproduce this ?

I guess Rob means current git, i.e.:

 git clone git://xcsoar.git.sourceforge.net/gitroot/xcsoar/xcsoar
 make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe

(The PPC2000 seems broken right now, but I hope we can merge both into
one if mingw32ce works)

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

correct
----- Original Message -----
From: "Max Kellermann" <max@...>
To: "Danny Backx" <danny.backx@...>
Cc: "Rob Dunning" <rob@...>;
<xcsoar-devel@...>
Sent: Monday, September 21, 2009 2:01 PM
Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000


> On 2009/09/21 19:59, Danny Backx <danny.backx@...> wrote:
>> Which version of xcsoar do I need to grab to reproduce this ?
>
> I guess Rob means current git, i.e.:
>
> git clone git://xcsoar.git.sourceforge.net/gitroot/xcsoar/xcsoar
> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
>
> (The PPC2000 seems broken right now, but I hope we can merge both into
> one if mingw32ce works)
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by John Wharington-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

One thing I'm not sure about is whether mingw32ce supports
MIPS; this is one of the processors we were providing XCSoar binaries
for.  Can you shed light on that Danny?

On Mon, 2009-09-21 at 20:01 +0200, Max Kellermann wrote:

> On 2009/09/21 19:59, Danny Backx <danny.backx@...> wrote:
> > Which version of xcsoar do I need to grab to reproduce this ?
>
> I guess Rob means current git, i.e.:
>
>  git clone git://xcsoar.git.sourceforge.net/gitroot/xcsoar/xcsoar
>  make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
>
> (The PPC2000 seems broken right now, but I hope we can merge both into
> one if mingw32ce works)
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Xcsoar-devel mailing list
> Xcsoar-devel@...
> https://lists.sourceforge.net/lists/listinfo/xcsoar-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Max Kellermann :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 2009/09/22 09:08, John Wharington <jwharington@...> wrote:
> One thing I'm not sure about is whether mingw32ce supports
> MIPS; this is one of the processors we were providing XCSoar binaries
> for.  Can you shed light on that Danny?

There are no precompiled cegcc binaries for the MIPS target, but since
it's all based on gcc, I guess (and hope) it's just a matter of
recompiling.

Max

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, 2009-09-21 at 14:44 -0400, Rob Dunning wrote:
> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe

Can you try whether
http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe
works ?

        Danny

--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Danny,

Thanks for your help on this.

Negative - the Wince3 PDA says "Cannot find XCSoarsimulator-PPC2002-ns' (or
one of its components) ..." when I run that.

Note that we have removed two references to LineTo and MoveToEx which
although unused, are not supported by Wince3
according to the testapi utility.  Please download the latest head of the
source code.  This version of the program displays the startup splash
screen, and then exits after creating .  It also writes to the log file so
there is opportunity to debug this version of the program.

I'm in the process of setting up a debugger now, but am struggling with
VirtualBox and USB ports.

Rob


----- Original Message -----
From: "Danny Backx" <danny.backx@...>
To: "Rob Dunning" <rob@...>
Cc: "Max Kellermann" <max@...>; <xcsoar-devel@...>
Sent: Tuesday, September 22, 2009 2:32 PM
Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000


> On Mon, 2009-09-21 at 14:44 -0400, Rob Dunning wrote:
>> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
>
> Can you try whether
> http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe
> works ?
>
> Danny
>
> --
> Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ok I'll look into updating. Not sure how to do that with git :-)

Could you send me the output of the testapi2 run on your ppc2002 device
so I can also look into the calls in the executable that aren't
supported by the dll ?

        Danny

On Wed, 2009-09-23 at 10:24 -0400, Rob Dunning wrote:

> Danny,
>
> Thanks for your help on this.
>
> Negative - the Wince3 PDA says "Cannot find XCSoarsimulator-PPC2002-ns' (or
> one of its components) ..." when I run that.
>
> Note that we have removed two references to LineTo and MoveToEx which
> although unused, are not supported by Wince3
> according to the testapi utility.  Please download the latest head of the
> source code.  This version of the program displays the startup splash
> screen, and then exits after creating .  It also writes to the log file so
> there is opportunity to debug this version of the program.
>
> I'm in the process of setting up a debugger now, but am struggling with
> VirtualBox and USB ports.
>
> Rob
>
>
> ----- Original Message -----
> From: "Danny Backx" <danny.backx@...>
> To: "Rob Dunning" <rob@...>
> Cc: "Max Kellermann" <max@...>; <xcsoar-devel@...>
> Sent: Tuesday, September 22, 2009 2:32 PM
> Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000
>
>
> > On Mon, 2009-09-21 at 14:44 -0400, Rob Dunning wrote:
> >> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
> >
> > Can you try whether
> > http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe
> > works ?
> >
> > Danny
> >
> > --
> > Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
> >
> >
>
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Done.

New version at
http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe.2.bz2

You'll need to bunzip2 it, and rename to remove the .2 suffix. Not a
problem, I hope ?

The old exe did have the two calls you mention below, the new one
doesn't.

When running this on my (WM 6.0) PDA, I get an
        "Assertion failed: 0, at Comm.."
dialog. I can't read enough of it to see where it comes from though.
What can I do ?

        Danny

On Wed, 2009-09-23 at 19:59 +0200, Danny Backx wrote:

> Ok I'll look into updating. Not sure how to do that with git :-)
>
> Could you send me the output of the testapi2 run on your ppc2002 device
> so I can also look into the calls in the executable that aren't
> supported by the dll ?
>
> Danny
>
> On Wed, 2009-09-23 at 10:24 -0400, Rob Dunning wrote:
> > Danny,
> >
> > Thanks for your help on this.
> >
> > Negative - the Wince3 PDA says "Cannot find XCSoarsimulator-PPC2002-ns' (or
> > one of its components) ..." when I run that.
> >
> > Note that we have removed two references to LineTo and MoveToEx which
> > although unused, are not supported by Wince3
> > according to the testapi utility.  Please download the latest head of the
> > source code.  This version of the program displays the startup splash
> > screen, and then exits after creating .  It also writes to the log file so
> > there is opportunity to debug this version of the program.
> >
> > I'm in the process of setting up a debugger now, but am struggling with
> > VirtualBox and USB ports.
> >
> > Rob
> >
> >
> > ----- Original Message -----
> > From: "Danny Backx" <danny.backx@...>
> > To: "Rob Dunning" <rob@...>
> > Cc: "Max Kellermann" <max@...>; <xcsoar-devel@...>
> > Sent: Tuesday, September 22, 2009 2:32 PM
> > Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000
> >
> >
> > > On Mon, 2009-09-21 at 14:44 -0400, Rob Dunning wrote:
> > >> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
> > >
> > > Can you try whether
> > > http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe
> > > works ?
> > >
> > > Danny
> > >
> > > --
> > > Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
> > >
> > >
> >
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Max Kellermann :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 2009/09/23 21:03, Danny Backx <danny.backx@...> wrote:
> When running this on my (WM 6.0) PDA, I get an
> "Assertion failed: 0, at Comm.."
> dialog. I can't read enough of it to see where it comes from though.
> What can I do ?

I think that's the regression I noticed recently, but didn't have the
time for research yet.  Try this hotfix.


diff --git a/Common/Source/GlideComputerTask.cpp b/Common/Source/GlideComputerTask.cpp
index c47e789..3c7cae2 100644
--- a/Common/Source/GlideComputerTask.cpp
+++ b/Common/Source/GlideComputerTask.cpp
@@ -240,6 +240,7 @@ void GlideComputerTask::AltitudeRequired(const double this_maccready,
 double GlideComputerTask::AATCloseBearing() const
 {
   // ensure waypoint goes in direction of track if very close
+  return 0;
   assert(task.getActiveIndex()>0);
   TASK_POINT tp = task.getTaskPoint();
   double course_bearing = Bearing(task.getActiveLocation(), Basic().Location)


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I don't see a difference.

        Danny

On Wed, 2009-09-23 at 21:29 +0200, Max Kellermann wrote:
> On 2009/09/23 21:03, Danny Backx <danny.backx@...> wrote:
> > When running this on my (WM 6.0) PDA, I get an
> > "Assertion failed: 0, at Comm.."
> > dialog. I can't read enough of it to see where it comes from though.
> > What can I do ?
>
> I think that's the regression I noticed recently, but didn't have the
> time for research yet.  Try this hotfix.
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Rob Dunning :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Danny,

Here's the output and input from running testapi on the exe you just sent me
that said "Could not find XCSoarSimulator or one of it's parts":  (note
change to testapi3.c that reads multiple dlls in the input file).

Rob

----- Original Message -----
From: "Danny Backx" <danny.backx@...>
To: "Rob Dunning" <rob@...>
Cc: "Max Kellermann" <max@...>; <xcsoar-devel@...>
Sent: Wednesday, September 23, 2009 3:03 PM
Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000


> Done.
>
> New version at
> http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe.2.bz2
>
> You'll need to bunzip2 it, and rename to remove the .2 suffix. Not a
> problem, I hope ?
>
> The old exe did have the two calls you mention below, the new one
> doesn't.
>
> When running this on my (WM 6.0) PDA, I get an
> "Assertion failed: 0, at Comm.."
> dialog. I can't read enough of it to see where it comes from though.
> What can I do ?
>
> Danny
>
> On Wed, 2009-09-23 at 19:59 +0200, Danny Backx wrote:
>> Ok I'll look into updating. Not sure how to do that with git :-)
>>
>> Could you send me the output of the testapi2 run on your ppc2002 device
>> so I can also look into the calls in the executable that aren't
>> supported by the dll ?
>>
>> Danny
>>
>> On Wed, 2009-09-23 at 10:24 -0400, Rob Dunning wrote:
>> > Danny,
>> >
>> > Thanks for your help on this.
>> >
>> > Negative - the Wince3 PDA says "Cannot find XCSoarsimulator-PPC2002-ns'
>> > (or
>> > one of its components) ..." when I run that.
>> >
>> > Note that we have removed two references to LineTo and MoveToEx which
>> > although unused, are not supported by Wince3
>> > according to the testapi utility.  Please download the latest head of
>> > the
>> > source code.  This version of the program displays the startup splash
>> > screen, and then exits after creating .  It also writes to the log file
>> > so
>> > there is opportunity to debug this version of the program.
>> >
>> > I'm in the process of setting up a debugger now, but am struggling with
>> > VirtualBox and USB ports.
>> >
>> > Rob
>> >
>> >
>> > ----- Original Message -----
>> > From: "Danny Backx" <danny.backx@...>
>> > To: "Rob Dunning" <rob@...>
>> > Cc: "Max Kellermann" <max@...>;
>> > <xcsoar-devel@...>
>> > Sent: Tuesday, September 22, 2009 2:32 PM
>> > Subject: Re: [Xcsoar-devel] [Cegcc-devel] Compiling for PocketPC 2000
>> >
>> >
>> > > On Mon, 2009-09-21 at 14:44 -0400, Rob Dunning wrote:
>> > >> make TARGET=PPC2002 DEBUG=y XCSoarSimulator-PPC2002-ns.exe
>> > >
>> > > Can you try whether
>> > > http://danny.backx.info/download/cegcc/XCSoarSimulator-PPC2002-ns.exe
>> > > works ?
>> > >
>> > > Danny
>> > >
>> > > --
>> > > Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>> > >
>> > >
>> >
> --
> Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
>
>

#include <windows.h>
#include <stdio.h>
#include <stdlib.h>

void (WINAPI *fun)(void);

char *input = "\\temp\\testapi.in.txt",
        *output = "\\temp\\testapi.out.txt";
/*
assumes multiple libraries followed by their Procs
Library names must be preceded with "*"
e.g.
*COREDLL
BeginPaint
BitBlt
*COMMCTRL
InitCommonControls
*/

int main(int argc, char *argv[])
{
        int r, count = 0;
        HINSTANCE dll;
        wchar_t dllname[64], wapi[64];
        char field[64], dllnm[64];
        bool bLibraryOpen=false;

        FILE *infile = NULL,
                *outfile = NULL;

        infile = fopen(input, "r");
        if (infile == NULL) {
                MessageBoxW(0, L"Could not open input file", L"Error", 0);
                exit(1);
        }

        outfile = fopen(output, "w");
        if (outfile == NULL) {
                MessageBoxW(0, L"Could not open output file", L"Error", 0);
                exit(2);
        }

       
        // read library name
        r=fscanf(infile, "%s\n", &field);
        while (r != EOF) {
                if (field[0] == '*') { // load the library
                        for (int i = 0; i <= strlen(field); i++) {
                                field[i]=field[i+1];
                        }
                        mbstowcs(dllname, field, 64);
                        strcpy(dllnm, field);
                        dll = LoadLibrary(dllname);
                        if (! dll) {
                                DWORD e = GetLastError();
                                fprintf(outfile, "LoadLibrary(%s) : cannot load DLL -> error %d\n", dllnm, e);
                                bLibraryOpen=false;
                        }
                        else {
                                fprintf(outfile, "Testapi2 reading library (%s)\n", field);
                                bLibraryOpen=true;;
                        }
                } // load library
                else { // not a library

                        if (bLibraryOpen) {
                                if (count++ > 2000) {
                                        printf("Terminating\n");
                                        fprintf(outfile, "Terminating\n");
                                        fclose(outfile);
                                        exit(1);
                                }
                                mbstowcs(wapi, field, 64);
                                *(FARPROC *)&fun = GetProcAddress(dll, wapi);
                                if (fun) {
                                        fprintf(outfile, "\t%s implements %s (0x%08X)\n", dllnm, field, fun);
                                } else {
                                        DWORD e = GetLastError();
                                        fprintf(outfile, "%s doesn't know about %s\n", dllnm, field);
                                }
                       
                        }
                        else { // library not open so
                                        fprintf(outfile, "%s could not be opened to query about %s\n", dllnm, field);
                        }
                }
                r=fscanf(infile, "%s\n", &field);
        } // end while
       
        fclose(outfile);
        fclose(infile);
        exit(0);
}

Testapi2 reading library (AYGSHELL)
        AYGSHELL implements SHFullScreen (0x01BC2EB0)
        AYGSHELL implements SHSetAppKeyWndAssoc (0x01BC355C)
Testapi2 reading library (COREDLL.dll)
        COREDLL.dll implements _strdup (0x01FCC8E8)
        COREDLL.dll implements _strupr (0x01FCD288)
Testapi2 reading library (COMMCTRL)
        COMMCTRL implements InitCommonControls (0x01AA2444)
Testapi2 reading library (COREDLL)
        COREDLL implements BeginPaint (0x01FAE5D0)
        COREDLL implements BitBlt (0x01FAC784)
        COREDLL implements BringWindowToTop (0x01FAF134)
        COREDLL implements CallWindowProcW (0x01FAF930)
        COREDLL implements CharUpperW (0x01FB6838)
        COREDLL implements ClearCommError (0x01FB94D8)
        COREDLL implements CloseHandle (0x01FA8F6C)
        COREDLL implements CompareFileTime (0x01FBA1B0)
        COREDLL implements CopyRect (0x01FBE2EC)
        COREDLL implements CreateAcceleratorTableW (0x01FBE6F0)
        COREDLL implements CreateCompatibleBitmap (0x01FAC80C)
        COREDLL implements CreateCompatibleDC (0x01FAC824)
        COREDLL implements CreateDIBSection (0x01FBE7B4)
        COREDLL implements CreateDialogIndirectParamW (0x01FAF9B8)
        COREDLL implements CreateDirectoryW (0x01FA87FC)
        COREDLL implements CreateEventW (0x01FA8FDC)
        COREDLL implements CreateFileW (0x01FA88EC)
        COREDLL implements CreateFontIndirectW (0x01FAC854)
        COREDLL implements CreateMutexW (0x01FAA3FC)
        COREDLL implements CreatePatternBrush (0x01FAD34C)
        COREDLL implements CreatePen (0x01FAD294)
        COREDLL implements CreateProcessW (0x01FAC3CC)
        COREDLL implements CreateSolidBrush (0x01FAC89C)
        COREDLL implements CreateThread (0x01FAC45C)
        COREDLL implements CreateWindowExW (0x01FAD554)
        COREDLL implements DefWindowProcW (0x01FAE980)
        COREDLL implements DeleteCriticalSection (0x01FB09B4)
        COREDLL implements DeleteDC (0x01FAC8FC)
        COREDLL implements DeleteFileW (0x01FA885C)
        COREDLL implements DeleteObject (0x01FAC914)
        COREDLL implements DestroyAcceleratorTable (0x01FBE79C)
        COREDLL implements DestroyWindow (0x01FAEC24)
        COREDLL implements DispatchMessageW (0x01FADC2C)
        COREDLL implements DrawEdge (0x01FAC974)
        COREDLL implements DrawFrameControl (0x01FB05C4)
        COREDLL implements DrawTextW (0x01FAC9A4)
        COREDLL implements Ellipse (0x01FACA14)
        COREDLL implements EnableWindow (0x01FAFB80)
        COREDLL implements EndDialog (0x01FAF558)
        COREDLL implements EndPaint (0x01FAE630)
        COREDLL implements EnterCriticalSection (0x01FB09D8)
        COREDLL implements EqualRect (0x01FBE584)
        COREDLL implements EscapeCommFunction (0x01FB9554)
        COREDLL implements EventModify (0x01FA8EFC)
        COREDLL implements ExtEscape (0x01FAD44C)
        COREDLL implements ExtTextOutW (0x01FACA94)
        COREDLL implements FileTimeToSystemTime (0x01FBA72C)
        COREDLL implements FillRect (0x01FACB1C)
        COREDLL implements FindClose (0x01FA8B4C)
        COREDLL implements FindFirstFileW (0x01FA88A4)
        COREDLL implements FindNextFileW (0x01FA8B64)
        COREDLL implements FindResourceW (0x01FA9A48)
        COREDLL implements FindWindowW (0x01FAFAE0)
        COREDLL implements FlushFileBuffers (0x01FA8A64)
        COREDLL implements FreeLibrary (0x01FA9890)
        COREDLL implements GetClassInfoW (0x01FAF970)
        COREDLL implements GetClientRect (0x01FAE044)
        COREDLL implements GetCommModemStatus (0x01FB9688)
        COREDLL implements GetCommState (0x01FB9708)
        COREDLL implements GetCommTimeouts (0x01FB9748)
        COREDLL implements GetDC (0x01FAE690)
        COREDLL implements GetDeviceCaps (0x01FACBF4)
        COREDLL implements GetDiskFreeSpaceExW (0x01FA8874)
        COREDLL implements GetDlgItem (0x01FAF570)
        COREDLL implements GetFileAttributesW (0x01FA888C)
        COREDLL implements GetFileInformationByHandle (0x01FA8A4C)
        COREDLL implements GetFocus (0x01FAED2C)
        COREDLL implements GetLastError (0x01FA93C4)
        COREDLL implements GetLocalTime (0x01FBAAA0)
        COREDLL implements GetMessageW (0x01FAD8F8)
        COREDLL implements GetModuleHandleW (0x01FA9C58)
        COREDLL implements GetObjectType (0x01FACC3C)
        COREDLL implements GetObjectW (0x01FACC24)
        COREDLL implements GetPixel (0x01FACC54)
        COREDLL implements GetProcAddressW (0x01FA9998)
        COREDLL implements GetStockObject (0x01FACCFC)
        COREDLL implements GetSystemMetrics (0x01FAE134)
        COREDLL implements GetSystemPowerStatusEx2 (0x01FB012C)
        COREDLL implements GetSystemTime (0x01FBA9D0)
        COREDLL implements GetTextExtentExPointW (0x01FACD74)
        COREDLL implements GetTextMetricsW (0x01FACE0C)
        COREDLL implements GetTickCount (0x01FA9B50)
        COREDLL implements GetTimeZoneInformation (0x01FBADA8)
        COREDLL implements GetWindowLongW (0x01FAE5A0)
        COREDLL implements GetWindowRect (0x01FADEE0)
        COREDLL implements GetWindowTextW (0x01FAE36C)
        COREDLL implements GlobalMemoryStatus (0x01FB1298)
        COREDLL implements InflateRect (0x01FBE3A8)
        COREDLL implements InitializeCriticalSection (0x01FB098C)
        COREDLL implements InvalidateRect (0x01FAE074)
        COREDLL implements IsChild (0x01FAF164)
        COREDLL implements KernelIoControl (0x01FAA31C)
        COREDLL implements KillTimer (0x01FAFB10)
        COREDLL implements LeaveCriticalSection (0x01FB0B1C)
        COREDLL implements LoadAcceleratorsW (0x01FBE6C4)
        COREDLL implements LoadBitmapW (0x01FAF1F4)
        COREDLL implements LoadCursorW (0x01FB0684)
        COREDLL implements LoadIconW (0x01FAF2AC)
        COREDLL implements LoadLibraryW (0x01FA97E0)
        COREDLL implements LoadResource (0x01FA9AA0)
        COREDLL implements LoadStringW (0x01FAF454)
        COREDLL implements LocalAlloc (0x01FB9A24)
        COREDLL implements LocalFree (0x01FB9AFC)
        COREDLL implements MessageBeep (0x01FB0054)
        COREDLL implements MessageBoxW (0x01FAECE4)
        COREDLL implements MoveFileW (0x01FA882C)
        COREDLL implements MultiByteToWideChar (0x01FB5CD8)
        COREDLL implements OffsetRect (0x01FBE370)
        COREDLL implements OutputDebugStringW (0x01FA9E68)
        COREDLL implements Polygon (0x01FACEC4)
        COREDLL implements Polyline (0x01FACEDC)
        COREDLL implements PostMessageW (0x01FAD5B4)
        COREDLL implements PostQuitMessage (0x01FAD614)
        COREDLL implements PtInRect (0x01FBE334)
        COREDLL implements PurgeComm (0x01FB9788)
        COREDLL implements ReadFile (0x01FA8984)
        COREDLL implements Rectangle (0x01FACF0C)
        COREDLL implements RegCloseKey (0x01FC763C)
        COREDLL implements RegCreateKeyExW (0x01FC76B4)
        COREDLL implements RegDeleteKeyW (0x01FC7744)
        COREDLL implements RegEnumValueW (0x01FC7774)
        COREDLL implements RegOpenKeyExW (0x01FC77F4)
        COREDLL implements RegQueryValueExW (0x01FC78C4)
        COREDLL implements RegSetValueExW (0x01FC793C)
        COREDLL implements RegisterClassW (0x01FC799C)
        COREDLL implements ReleaseCapture (0x01FADD24)
        COREDLL implements ReleaseDC (0x01FAE708)
        COREDLL implements ReleaseMutex (0x01FAA38C)
        COREDLL implements RoundRect (0x01FACF7C)
        COREDLL implements SHGetSpecialFolderPath (0x01FC7A94)
        COREDLL implements SelectObject (0x01FACFE4)
        COREDLL implements SendMessageW (0x01FAD890)
        COREDLL implements SetBkColor (0x01FAD044)
        COREDLL implements SetBkMode (0x01FAD0A4)
        COREDLL implements SetCapture (0x01FADD0C)
        COREDLL implements SetCommMask (0x01FB9808)
        COREDLL implements SetCommState (0x01FB984C)
        COREDLL implements SetCommTimeouts (0x01FB9888)
        COREDLL implements SetCursor (0x01FB01BC)
        COREDLL implements SetFilePointer (0x01FA8A34)
        COREDLL implements SetFocus (0x01FAED14)
        COREDLL implements SetForegroundWindow (0x01FAF840)
        COREDLL implements SetLastError (0x01FA9374)
        COREDLL implements SetROP2 (0x01FAD2F4)
        COREDLL implements SetRect (0x01FBE2AC)
        COREDLL implements SetTextColor (0x01FAD134)
        COREDLL implements SetThreadPriority (0x01FA91DC)
        COREDLL implements SetTimer (0x01FAFAF8)
        COREDLL implements SetWindowLongW (0x01FAE384)
        COREDLL implements SetWindowPos (0x01FADD3C)
        COREDLL implements SetWindowTextW (0x01FAE354)
        COREDLL implements SetupComm (0x01FB98C4)
        COREDLL implements ShowWindow (0x01FAEC3C)
        COREDLL implements SizeofResource (0x01FA9AF8)
        COREDLL implements Sleep (0x01FA9034)
        COREDLL implements StretchBlt (0x01FAD194)
        COREDLL implements SystemIdleTimerReset (0x01FB024C)
        COREDLL implements SystemTimeToFileTime (0x01FBA60C)
        COREDLL implements TerminateProcess (0x01FAC4CC)
        COREDLL implements TranslateAcceleratorW (0x01FAFDF8)
        COREDLL implements TranslateMessage (0x01FAD958)
        COREDLL implements TransparentImage (0x01FAD394)
        COREDLL implements UpdateWindow (0x01FAEC54)
        COREDLL implements VirtualProtect (0x01FA9680)
        COREDLL implements VirtualQuery (0x01FA96D8)
        COREDLL implements WaitCommEvent (0x01FB994C)
        COREDLL implements WaitForMultipleObjects (0x01FA9084)
        COREDLL implements WaitForSingleObject (0x01FA90DC)
        COREDLL implements WideCharToMultiByte (0x01FB5EC8)
        COREDLL implements WriteFile (0x01FA89F4)
        COREDLL implements _fcloseall (0x01FCE3B8)
        COREDLL implements _fpreset (0x01FCDDF8)
        COREDLL implements _getstdfilex (0x01FC8A58)
        COREDLL implements _hypot (0x01FCD2C4)
        COREDLL implements _isctype (0x01FB589C)
        COREDLL implements _snwprintf (0x01FD0DDC)
        COREDLL implements _strdup (0x01FCC8E8)
        COREDLL implements _stricmp (0x01FCC938)
        COREDLL implements _vsnwprintf (0x01FD0D04)
        COREDLL implements _wcsdup (0x01FCC8A8)
        COREDLL implements _wcsicmp (0x01FB9448)
        COREDLL implements _wcsnicmp (0x01FB93DC)
        COREDLL implements _wcsupr (0x01FB6838)
        COREDLL implements _wfopen (0x01FCE858)
        COREDLL implements acos (0x01FD0E7C)
        COREDLL implements asin (0x01FD0E74)
        COREDLL implements atan (0x01FD1468)
        COREDLL implements atan2 (0x01FD159C)
        COREDLL implements atof (0x01FD1F60)
        COREDLL implements atoi (0x01FD2080)
        COREDLL implements calloc (0x01FD2090)
        COREDLL implements ceil (0x01FD209C)
        COREDLL implements cos (0x01FD252C)
        COREDLL implements exp (0x01FD3278)
        COREDLL implements fclose (0x01FCE4B8)
        COREDLL implements fflush (0x01FCE16C)
        COREDLL implements fgets (0x01FCF568)
        COREDLL implements fgetws (0x01FCF548)
        COREDLL implements floor (0x01FD3B58)
        COREDLL implements fmod (0x01FD3C98)
        COREDLL implements fopen (0x01FCE864)
        COREDLL implements fprintf (0x01FD41D4)
        COREDLL implements fputc (0x01FD41F0)
        COREDLL implements fputs (0x01FD0B60)
        COREDLL implements fread (0x01FD4558)
        COREDLL implements free (0x01FD4738)
        COREDLL implements fseek (0x01FD48C8)
        COREDLL implements ftell (0x01FD4A38)
        COREDLL implements fwprintf (0x01FD4CC4)
        COREDLL implements fwrite (0x01FD4D34)
        COREDLL implements iswctype (0x01FB5878)
        COREDLL implements log (0x01FD65A8)
        COREDLL implements log10 (0x01FD65A0)
        COREDLL implements malloc (0x01FD2084)
        COREDLL implements mbstowcs (0x01FA2D58)
        COREDLL implements memcmp (0x01FD6A24)
        COREDLL implements memcpy (0x01FD6EC4)
        COREDLL implements memmove (0x01FD6AF0)
        COREDLL implements memset (0x01FD723C)
        COREDLL implements pow (0x01FD7464)
        COREDLL implements printf (0x01FD4180)
        COREDLL implements puts (0x01FD0BD8)
        COREDLL implements qsort (0x01FD82CC)
        COREDLL implements realloc (0x01FD856C)
        COREDLL implements sin (0x01FD22A4)
        COREDLL implements sndPlaySoundW (0x01FB192C)
        COREDLL implements sprintf (0x01FD0CE0)
        COREDLL implements sqrt (0x01FCEEE4)
        COREDLL implements sscanf (0x01FD862C)
        COREDLL implements strcat (0x01FD8674)
        COREDLL implements strcmp (0x01FD86C0)
        COREDLL implements strcpy (0x01FD87AC)
        COREDLL implements strlen (0x01FD88CC)
        COREDLL implements strncmp (0x01FD896C)
        COREDLL implements strncpy (0x01FD899C)
        COREDLL implements strrchr (0x01FCCC94)
        COREDLL implements strstr (0x01FD8A40)
        COREDLL implements strtok (0x01FD8CB8)
        COREDLL implements swprintf (0x01FD0DF8)
        COREDLL implements swscanf (0x01FD90DC)
        COREDLL implements tan (0x01FD9120)
        COREDLL implements tolower (0x01FD99C8)
        COREDLL implements toupper (0x01FD99DC)
        COREDLL implements towupper (0x01FB6790)
        COREDLL implements vsprintf (0x01FD0CB4)
        COREDLL implements vswprintf (0x01FD0DC8)
        COREDLL implements wcscat (0x01FCC768)
        COREDLL implements wcschr (0x01FCC7C0)
        COREDLL implements wcscmp (0x01FCC800)
        COREDLL implements wcscpy (0x01FCC7A0)
        COREDLL implements wcslen (0x01FCCA10)
        COREDLL implements wcsncat (0x01FCCA34)
        COREDLL implements wcsncmp (0x01FCCA8C)
        COREDLL implements wcsncpy (0x01FCCAD8)
        COREDLL implements wcsstr (0x01FCCE74)
        COREDLL implements wcstod (0x01FD8ABC)
        COREDLL implements wcstok (0x01FCCEE4)
        COREDLL implements wcstol (0x01FD8DA8)
        COREDLL implements wsprintfW (0x01FD0DF8)
Testapi2 reading library (IMGDECMP)
        IMGDECMP implements DecompressImageIndirect (0x01124300)
LoadLibrary(libstdc++-6.dll) : cannot load DLL -> error 126
libstdc++-6.dll could not be opened to query about _ZSt17__throw_bad_allocv
libstdc++-6.dll could not be opened to query about _ZSt18_Rb_tree_decrementPKSt18_Rb_tree_node_base
libstdc++-6.dll could not be opened to query about _ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base
libstdc++-6.dll could not be opened to query about _ZSt18_Rb_tree_incrementPKSt18_Rb_tree_node_base
libstdc++-6.dll could not be opened to query about _ZSt29_Rb_tree_insert_and_rebalancebPSt18_Rb_tree_node_baseS0_RS
libstdc++-6.dll could not be opened to query about _ZTVN10__cxxabiv117__class_type_infoE
libstdc++-6.dll could not be opened to query about _ZTVN10__cxxabiv120__si_class_type_infoE
libstdc++-6.dll could not be opened to query about _ZTVN10__cxxabiv121__vmi_class_type_infoE
libstdc++-6.dll could not be opened to query about _ZdaPv
libstdc++-6.dll could not be opened to query about _ZdlPv
libstdc++-6.dll could not be opened to query about _Znaj
libstdc++-6.dll could not be opened to query about _Znwj
libstdc++-6.dll could not be opened to query about __cxa_guard_acquire
libstdc++-6.dll could not be opened to query about __cxa_guard_release
libstdc++-6.dll could not be opened to query about __cxa_pure_virtual

*AYGSHELL
SHFullScreen
SHSetAppKeyWndAssoc
*COREDLL.dll
_strdup
_strupr
*COMMCTRL
InitCommonControls
*COREDLL
BeginPaint
BitBlt
BringWindowToTop
CallWindowProcW
CharUpperW
ClearCommError
CloseHandle
CompareFileTime
CopyRect
CreateAcceleratorTableW
CreateCompatibleBitmap
CreateCompatibleDC
CreateDIBSection
CreateDialogIndirectParamW
CreateDirectoryW
CreateEventW
CreateFileW
CreateFontIndirectW
CreateMutexW
CreatePatternBrush
CreatePen
CreateProcessW
CreateSolidBrush
CreateThread
CreateWindowExW
DefWindowProcW
DeleteCriticalSection
DeleteDC
DeleteFileW
DeleteObject
DestroyAcceleratorTable
DestroyWindow
DispatchMessageW
DrawEdge
DrawFrameControl
DrawTextW
Ellipse
EnableWindow
EndDialog
EndPaint
EnterCriticalSection
EqualRect
EscapeCommFunction
EventModify
ExtEscape
ExtTextOutW
FileTimeToSystemTime
FillRect
FindClose
FindFirstFileW
FindNextFileW
FindResourceW
FindWindowW
FlushFileBuffers
FreeLibrary
GetClassInfoW
GetClientRect
GetCommModemStatus
GetCommState
GetCommTimeouts
GetDC
GetDeviceCaps
GetDiskFreeSpaceExW
GetDlgItem
GetFileAttributesW
GetFileInformationByHandle
GetFocus
GetLastError
GetLocalTime
GetMessageW
GetModuleHandleW
GetObjectType
GetObjectW
GetPixel
GetProcAddressW
GetStockObject
GetSystemMetrics
GetSystemPowerStatusEx2
GetSystemTime
GetTextExtentExPointW
GetTextMetricsW
GetTickCount
GetTimeZoneInformation
GetWindowLongW
GetWindowRect
GetWindowTextW
GlobalMemoryStatus
InflateRect
InitializeCriticalSection
InvalidateRect
IsChild
KernelIoControl
KillTimer
LeaveCriticalSection
LoadAcceleratorsW
LoadBitmapW
LoadCursorW
LoadIconW
LoadLibraryW
LoadResource
LoadStringW
LocalAlloc
LocalFree
MessageBeep
MessageBoxW
MoveFileW
MultiByteToWideChar
OffsetRect
OutputDebugStringW
Polygon
Polyline
PostMessageW
PostQuitMessage
PtInRect
PurgeComm
ReadFile
Rectangle
RegCloseKey
RegCreateKeyExW
RegDeleteKeyW
RegEnumValueW
RegOpenKeyExW
RegQueryValueExW
RegSetValueExW
RegisterClassW
ReleaseCapture
ReleaseDC
ReleaseMutex
RoundRect
SHGetSpecialFolderPath
SelectObject
SendMessageW
SetBkColor
SetBkMode
SetCapture
SetCommMask
SetCommState
SetCommTimeouts
SetCursor
SetFilePointer
SetFocus
SetForegroundWindow
SetLastError
SetROP2
SetRect
SetTextColor
SetThreadPriority
SetTimer
SetWindowLongW
SetWindowPos
SetWindowTextW
SetupComm
ShowWindow
SizeofResource
Sleep
StretchBlt
SystemIdleTimerReset
SystemTimeToFileTime
TerminateProcess
TranslateAcceleratorW
TranslateMessage
TransparentImage
UpdateWindow
VirtualProtect
VirtualQuery
WaitCommEvent
WaitForMultipleObjects
WaitForSingleObject
WideCharToMultiByte
WriteFile
_fcloseall
_fpreset
_getstdfilex
_hypot
_isctype
_snwprintf
_strdup
_stricmp
_vsnwprintf
_wcsdup
_wcsicmp
_wcsnicmp
_wcsupr
_wfopen
acos
asin
atan
atan2
atof
atoi
calloc
ceil
cos
exp
fclose
fflush
fgets
fgetws
floor
fmod
fopen
fprintf
fputc
fputs
fread
free
fseek
ftell
fwprintf
fwrite
iswctype
log
log10
malloc
mbstowcs
memcmp
memcpy
memmove
memset
pow
printf
puts
qsort
realloc
sin
sndPlaySoundW
sprintf
sqrt
sscanf
strcat
strcmp
strcpy
strlen
strncmp
strncpy
strrchr
strstr
strtok
swprintf
swscanf
tan
tolower
toupper
towupper
vsprintf
vswprintf
wcscat
wcschr
wcscmp
wcscpy
wcslen
wcsncat
wcsncmp
wcsncpy
wcsstr
wcstod
wcstok
wcstol
wsprintfW
*IMGDECMP
DecompressImageIndirect
*libstdc++-6.dll
_ZSt17__throw_bad_allocv
_ZSt18_Rb_tree_decrementPKSt18_Rb_tree_node_base
_ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base
_ZSt18_Rb_tree_incrementPKSt18_Rb_tree_node_base
_ZSt29_Rb_tree_insert_and_rebalancebPSt18_Rb_tree_node_baseS0_RS_
_ZTVN10__cxxabiv117__class_type_infoE
_ZTVN10__cxxabiv120__si_class_type_infoE
_ZTVN10__cxxabiv121__vmi_class_type_infoE
_ZdaPv
_ZdlPv
_Znaj
_Znwj
__cxa_guard_acquire
__cxa_guard_release
__cxa_pure_virtual

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel

Re: [Cegcc-devel] Compiling for PocketPC 2000

by Danny Backx :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The changes you applied to my source look very useful.

There's a big difference between the testapi.in.txt that I sent and the
one you used. Of the 1660 lines in my file (1559 functions), you only
keep 259 in your input file.

Is that all that Windows CE 3 defines ? If not, could you send along the
output with my complete list used as input so I can scan my executable
for functions not supported in your device ?

        Danny

On Wed, 2009-09-23 at 18:18 -0400, Rob Dunning wrote:
> Danny,
>
> Here's the output and input from running testapi on the exe you just sent me
> that said "Could not find XCSoarSimulator or one of it's parts":  (note
> change to testapi3.c that reads multiple dlls in the input file).
>
> Rob
 
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel
< Prev | 1 - 2 | Next >