Re: Compile problem

Huh? What do you mean you can't do anything about it? You can't change the
project settings? If you can't do that, you're out of luck.

In the Solution Explorer, right-click on the project name and choose
Properties. In the Configuration Properties portion of the tree, choose
Linker and, under that, Advanced. Note that Entry Point is the first item
in the list. If that's been set wrong by the conversion, you should be able
to change it. You might also check the subsystem setting, etc. It *is*
going to be possible to make this work, but you may have to fool with it, as
I said.

Paul T.

"cdang_2000" <cdang2000@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5E81867-6925-4F75-A633-A54611D09D1C@xxxxxxxxxxxxxxxx
Hello Paul,

Thanks for answering my question. However, it does not solve it, from my
point of view. I think the whole issue is the SW architecture differences
between the two compilers: eMebedded and Visual Studio 2005. And changing
the "Entry Point" as you said, is really beyond my reach. In other words,
I
cannot do anything about that.

I really hope that you and others can point me a right way to solve this
error.

Thanks again, Paul



"Paul G. Tobey [eMVP]" wrote:

The project is assuming a certain entry point, so you'll need to change
the
Link setting for the entry point to correspond to what entry point you
actually have (not sure why the conversion didn't work right). I'm not
sure
exactly what the right entry is, but that's where you need to make the
change (Entry Point), so maybe you can figure it out from that pointer...

Paul T.

"cdang_2000" <cdang2000@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:86FC5734-2E35-4395-A0D2-F6B0EC583C11@xxxxxxxxxxxxxxxx
Hello all,

I really need your helps here.

I had a dialog-based app compiled using eMbedded 4.2 PPC 2003 SDK. It
runs
great on Pocket PC device. Now, I want to compile it using Microsoft
Visual
Studio 2005 with either Mobile 5.0 Pocket PC SDK or Mobile 5.0
SmartPhone
SDK.

The project conversion is OK, compile process is OK. However, it gives
a
linking problem, like below:

Error 1 error LNK2019: unresolved external symbol wWinMain referenced
in
function wWinMainCRTStartup in file corelibc.lib.

Does anyone know anything how to fix this? I would be very thankful to
have
answers for this.

Thanks in advance.








.

Relevant Pages

  • Re: float to pointer coercion (cost 13)
    ... Do you compile two versions of the ... but it is given two entry ... but to the immediate-args entry point. ... ((DOUBLE-FLOAT DOUBLE-FLOAT) ...
    (comp.lang.lisp)
  • Re: HLA suggestions
    ... >> This is only true if you compile a PROGRAM. ... >> For more details on controlling the code that HLA generates. ... lex level:) as the "_HLAMain" entry point...and the linker response ...
    (alt.lang.asm)
  • Re: float to pointer coercion (cost 13)
    ... Do you compile two versions of the ... but to the immediate-args entry point. ... I didn't realize that Maclisp used that technique. ... > Or maybe it came from some contemporary hack in the "Franz Lisp", ...
    (comp.lang.lisp)
  • Re: Linux kernel 2.4 programming problem
    ... I create a new entry in arch/i386/kernel/entry.S ... compile i receive a problem like this ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Linux kernel 2.4 programming problem
    ... I read guide/articles like this ... All the articles say the same things, but the implementation of my new ... I create a new entry in arch/i386/kernel/entry.S ... compile i receive a problem like this ...
    (Linux-Kernel)