Re: "Not a valid pocket pc application" -- not just trying to install an exe on the pocket pc

From: Doug Forster (doug_ZAPTHIS_AT_ZAPTHIS_TONIQ_DOT_CO_DOT_NZ)
Date: 11/18/04

  • Next message: Doug Forster: "Re: Cannot find the definition (implementation) of this function?" 
    Date: Fri, 19 Nov 2004 08:31:02 +1300

    Hi Alex,

    A pxa255 is *not* an x86 processor, it is an ARM - all PPC2003 devices are
    ARM intel or otherwise. I think you have gotten your project settings messed
    up by switching platforms all over the place. The easiest way of getting
    out of such a mess is to recreate the project from scratch using the correct
    platform (one of the Pocket PC 2003 wizards depending on whether you use MFC
    or not) . Get a 'Hello World' app working then manually add back any code
    you have already written. The resulting project will only have 2 processor
    options: WCE emulator and ARMV4 with a Release and Debug for each.

    Cheers

    Doug Forster

    "Alex" <acreepycow@yahoo.com> wrote in message
    news:46bd4bc5.0411180737.15fa87b6@posting.google.com...
    > I'm sorry, I realize i didn't include nearly enough details in the
    > description of my problem. It is a ppc2003, i made the mistake of
    > using evc3.0 with ppc2002 sdk and it wouldn't even sync to transfer
    > the executable over, but that problem was fixed by updating to evc4.0.
    > I do think the problem has to do with the processor. In the pull down
    > menu on the main window of evc4.0 there are the options to compile for
    > Win32(WCE ARMV4) release and debug and Win32(WCE emulator) release and
    > debug. When I compile using the ARVV4 option i get the following
    > error:
    >
    > corelibc.lib(pegwmain.obj) : error LNK2019: unresolved external symbol
    > WinMain referenced in function WinMainCRTStartup
    > ARMV4Rel/PDABot1.exe : fatal error LNK1120: 1 unresolved externals
    >
    > When I build using the WCE emulator option it compiles and links fine
    > but i get that "not a valid pocket pc application" error when i try to
    > run it from the pocket pc. The pocket pc's processor is an Intel
    > pxa255. I read that that means i should use x86 selection because
    > that is the general option for all intel processors. Although x86
    > isn't explicit in the evc4.0 options (where it was in evc3.0), the WCE
    > option does link where the ARM selection fails.
    >
    > Thanks again in advance.
    >
    > Alex Steingart
    > Trinity '06
    > Duke University
    > Department of Mechanical Engineering

  • Next message: Doug Forster: "Re: Cannot find the definition (implementation) of this function?"

    Relevant Pages

    • Re: problematic array assignment in double precision (ifort, windows)
      ... unit sphere. ... It works fine when I compile it with a switch /real-size:32. ... I'm sorry to hear that you're having problems with the Intel Premier ... Developer Products Division ...
      (comp.lang.fortran)
    • Re: code portability
      ... I see massive gcc and imake requirements. ... Again this isn't a question on how to compile GCC, ... GCC is hardly your average OSS project (and Intel C is hardly standard ...
      (comp.lang.c)
    • Has anybody tried use the Intel MKL compiler/library along with Matlab?
      ... Does "mex" compile Intel's stuff? ... I learned that we can do debugging of MEX file by make the MSVC ... But for Intel C++ compiler stuff, has anybody been able to do debugging? ...
      (comp.soft-sys.matlab)
    • Re: Why are so many people using 4.x?
      ... FreeBSD is useably, configurably, and stably moreso than ... what was before* on each and every of the "intel ... drm doesn't compile, tintin++-devel doesn't compile, ... myriads of myriads (with only 14k plus some odd it takes ...
      (freebsd-questions)