Hi!
On Sun, Jul 08, 2007 at 08:20:49PM +0100, Pedro Alves wrote:
> Hi all,
>
> Here goes the v2 of the seh giga macros. Wear sunglasses.
>
> * __finally blocks don't eat the exception anymore.
>
> * The filter in __except (filter), is now really an
> expression, thanks to gcc's preprocessor
(adding the cegcc-devel back)
[EMAIL PROTECTED] wrote:
>>
> Since it is supported by coredll should I update my cegcc copy of winbase.h
> to include:
> HANDLE RegisterDevice (LPCWSTR lpszName, DWORD index,
> LPCWSTR lpszLib, DWORD dwInfo);
> BOOL DeregisterDevice (HANDLE hDevice);
>
> Or wa
Alexander Zubko wrote:
> So, now I'm very happy and satisfied user of your tool. Thanks.
> I've thought to write some manual about that I've done. But now it seems
> so simple, so I do not know write it or not. What do you think about it?
> Worth it writing and adding to some examples of using m
Hi Danny,
Somehow I missed this mail entirely. Sorry for that.
In case it still helps and for the record, I'll reply below. Probably
you've found this stuff out by yourself by now.
Danny Backx wrote:
> On Sun, 2007-06-03 at 19:01 +0100, Pedro Alves wrote:
>> The exception c++ model that both mi
Hi Leonardo,
sorry for the delay,
Leonardo Weiss Chaves wrote:
> Hi,
>
> I am trying to build jamvm (http://jamvm.sourceforge.net/) with
> cegcc/mingw32ce, since jamvm can also be build with cygwin
> (http://developer.classpath.org/mediation/ClasspathOnCygwin).
>
Cool stuff. I wish I knew a
Nuno Lucas wrote:
>
> Doesn't the "You got a segfault" message comes from the current active
> system debugger on Windows?
> I thought this was what DrWatson (the default system debugger) did for
> Windows. But when you install the Microsoft IDE it usually installs a
> new system debugger, which a
On Mon, 2007-07-09 at 21:49 +0100, Pedro Alves wrote:
> >> _cegcc_main_data:
> >> .word 0 /* _cegcc_main_handler */
> >> .word 0 /* _cegcc_main_size */
> ^^^
> This is not supposed to be the size, but a pointer
> to data to the passed to the handler. The size g
Hi,
Today I've also tried to build wxWinCE using cegcc.
I've seen that the developers of wxWinCE have used Visual C++
Embedded 4.0 to maintain this port, which means that it should
be possible to compile wxWinCE using mingw32ce (no unix portability
layer is required).
The configure script curren
On 7/10/07, Erik van Pienbroek wrote:
>
> The configure script currently doesn't support building the wxWinCE
> port. If you tell configure to use the wxMSW port, the compilation
> fails due to a missing errno.h (which indicates that the wxMSW port
> is really used instead of the wxWinCE port). It
Pedro,
Thanks for your reply. And I agree with you that interfaces (from OS kernel)
is the point that a driver develop should take care of. Now it's clearer for me
to understand the capability of cegcc. Cegcc is already a great tool that
helps me to port Linux applications!
BTW, the reas
On 7/10/07, Qian, Ling (Ling) wrote:
>
> 1. ACX100 driver is linked against the Linux kernel, what is the module to
> be linked in cegcc? is it libcoredll.a? ( I am downloading the src of cegcc,
> it needs some time :)
>
> 2. What is the relationship between the WinCE NDIS and libcoredll.a, w
11 matches
Mail list logo
