Re: C++ exception before WinMain
- From: Valter Minute <v_a_l_t_e_r.m_i_n_u_t_e@xxxxxxxxxxxxx>
- Date: Mon, 12 Mar 2007 07:46:00 -0700
"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> wrote in
news:upAWCHLZHHA.3968@xxxxxxxxxxxxxxxxxxxx:
Grazzie mille for your answers, Valter.
De rien, Remi.
You may have some link warning related to debugging symbols with
EVC++ and wince 5.0 system files because some parts of the OS are
built with the VS2005 compiler IIRC.
Do you think it is the case here?
Usually you have warning when building with EVC++ and a 5.0 SDK.
I do most of my development in Platform Builder and VS2005 so I don't
remember the exact warning code. The first time I saw them I did a
quick search on google groups and find that explanation.
The omni_thread warning are a bit more cryptic. It seems that
your module both imports (from an external lib) an exports those
simbols. Did you link some external libs? If the symbol is seen
also as export it may be that you should #define something to
change the way it's declared in . file.
You are probably right. I shall investigate on this point.
Good luck :)
[...]
You were right: I had missed a "static omni_thread::init_t
omni_thread_init;" class instanciation not showing in the
ClassView tab globals. Reading you helped me to focus on this
point :-) Actually, the exception was raised because of
DuplicateHandle call for a thread handle, which is not allowed
under CE.
I'm happy to hear that you found your problem.
Looking from the filename it seems a sort of VNC viewer. If it's
public domain and you can provide a link to the source code, I
can try it on my own device (but I'm not a C++ or WinCE guru at
all, so don't expect too much from me!).
Yes Sherlock ;-), it is a VNC Viewer, based on TightVNC
(http://prdownloads.sourceforge.net/vnc-tight/tightvnc-1.3.8_winsrc
.tar.bz2?download). Unfortunately, the porting to CE is not that
easy and quite a lot of the original code had to be changed for
the whole thing to compile - and link in this clumsy way. I can't
imagine yet what I am going to discover when tracing the code...
One of my customers ported an implementation of VNC server on CE.
It has to work out some issues on compilation and find a way to send
updates only when needed but it seems to work fine.
He told me about a "libVNC" that was released after he did his porting
and should be a simpler way to re-implement VNC on devices.
It should handle the protocol and let you re-implement the UI.
I never checked it... but it may be worth a look
(http://libvncserver.sourceforge.net/).
--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)
.
- Follow-Ups:
- Re: C++ exception before WinMain
- From: Remi de Gravelaine
- Re: C++ exception before WinMain
- References:
- C++ exception before WinMain
- From: Remi de Gravelaine
- Re: C++ exception before WinMain
- From: Valter Minute
- Re: C++ exception before WinMain
- From: Remi de Gravelaine
- C++ exception before WinMain
- Prev by Date: Re: Network projector in CE 6.0
- Next by Date: VirtualCopy error
- Previous by thread: Re: C++ exception before WinMain
- Next by thread: Re: C++ exception before WinMain
- Index(es):
Relevant Pages
|
