Re: [Cegcc-devel] Developing PocketIE ActiveX controls usin g CeGCC?

2009-01-07 Thread mosfet
y I had no need to write anything native for the device. > > However, the reading you pointed out seems like a very nice > start-by-example, for which I thank you. > > I am getting the distinct feeling, that I will need to stick to > eVC++ 4.0 for the task at hand. > &

Re: [Cegcc-devel] Developing PocketIE ActiveX controls usin g CeGCC?

2009-01-07 Thread mosfet
Hi, What you want to do is a bit crazy, it's not that easy with Visual and I don't know if it 's a good idea to add some issues with cegcc. In addition PocketIE is really a bad browser and except for very simple HTML page, you never have a good rendering... see here for more info : http://msdn.mi

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-21 Thread mosfet
Hum actually it seems normal tha IAT is null ... On Sun, 21 Dec 2008 14:33:05 +0100, mosfet wrote: > While checking differences between cegcc and visual I have also noticed > that : > > 1) Visual doesn't put a checksum in PE header but I don't think it's &

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-21 Thread mosfet
While checking differences between cegcc and visual I have also noticed that : 1) Visual doesn't put a checksum in PE header but I don't think it's important 2) IAT is NULL cegcc: -- Dump of file TESTDLL.DLL Data Directory EXPORT rva: 00014000 size: 004A IMPORT rva: 00

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-19 Thread mosfet
res created > by binutils and/or gcc is responsible for filling up this field. > > Or am I completely on the wrong track ? > > Danny > No I think you are right, this is the way to go. > On Fri, 2008-12-19 at 10:35 +0100, mosfet wrote: >> On Thu, 18 Dec 2008 2

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-19 Thread mosfet
rote UPX is doing the right thing, I don't know exactly how but maybe when compressing and uncompressing it fixes the issue with o32_ptr. > On Thu, 2008-12-18 at 10:38 +0100, mosfet wrote: >> Hi, >> >> Thanks to a great Windows Mobile Hacker/tweaker mamaich, he has

Re: [Cegcc-devel] Smartphone Example

2008-12-19 Thread mosfet
DS_OK, 0, NOMENU, END Now this is valid and comma will be silently eaten ... > On Thu, 2008-12-18 at 13:36 +0100, mosfet wrote: >> Ok one windres fix it and he will commit it into binutils: >> >> Index: src/binutils/rcparse.y >> ===

Re: [Cegcc-devel] Smartphone Example

2008-12-18 Thread mosfet
have the time for it right now. > > Danny > > On Tue, 2008-12-16 at 21:37 +0100, mosfet wrote: >> Hum actually it works but couldnt' be possible to fix windres to accept >> this syntax with comma ? >> >> >> >> >> On Tue, 16 Dec 2008

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-18 Thread mosfet
Hi, Thanks to a great Windows Mobile Hacker/tweaker mamaich, he has found why cegcc binaries are not loaded on WM6.1 platforms. Please find below his analysis : KITL output: 167564 PID:97eeb752 TID:b5980c3a CertVerify: \testDllexe.exe trust = 2 167635 PID:97eeb752 TID:b5980c3a CertVerify: test

Re: [Cegcc-devel] Smartphone Example

2008-12-16 Thread mosfet
Hum actually it works but couldnt' be possible to fix windres to accept this syntax with comma ? On Tue, 16 Dec 2008 17:23:54 +0100, Danny Backx wrote: > You need to make sure that you have the right macros defined. Here's a > Makefile that works for me : > TARGET=arm-mingw32ce > CC= ${TAR

Re: [Cegcc-devel] Smartphone Example

2008-12-16 Thread mosfet
Could you post your archive because when I try I still get some errors but since I am not using an official cegcc version but a "home made" I may have forgotten to report some modifications. Thanks On Tue, 16 Dec 2008 17:23:54 +0100, Danny Backx wrote: > You need to make sure that you have the

Re: [Cegcc-devel] Smartphone Example

2008-12-15 Thread mosfet
Hi, I don't want to copy/paste from MSDN, so could you send me your project ? And what command line are you using ? On Mon, 15 Dec 2008 13:46:05 -0600, "Jared Waltzer" wrote: > I am trying to compile the example here with the mingw32ce compiler: > http://msdn.microsoft.com/en-us/library/ms931

Re: [Cegcc-devel] mingw32ce, :: operator and w32api macros

2008-12-13 Thread mosfet
); //WINBASEAPI HANDLE WINAPI GetCurrentThread(void); //WINBASEAPI DWORD WINAPI GetCurrentThreadId(void); //WINBASEAPI BOOL WINAPI PulseEvent(HANDLE); //extern BOOL ResetEvent(HANDLE); On Sat, 13 Dec 2008 17:32:50 +0100, mosfet wrote: > Hum first I mean you need to declare it with inline but with

Re: [Cegcc-devel] mingw32ce, :: operator and w32api macros

2008-12-13 Thread mosfet
Hum first I mean you need to declare it with inline but without the _ like this. Could you test and tell us if it solves your issue ? winbase.h: -- #ifdef _WIN32_WCE inline LPVOID LockResource(HGLOBAL hResData) { return ((LPVOID)hResData); } #else WINBASEAPI PVOID WINAPI LockResourc

Re: [Cegcc-devel] mingw32ce, :: operator and w32api macros

2008-12-13 Thread mosfet
Hi, Thanks for your report! I think this function should be defined like visual ones as inline : _inline DWORD WINAPI TlsAlloc(void) { return TlsCall(TLS_FUNCALLOC, 0); } _inline BOOL WINAPI TlsFree(DWORD dwTlsIndex) { return TlsCall(TLS_FUNCFREE, dwTlsIndex); } _inline LPVOID

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-06 Thread mosfet
On Sat, 06 Dec 2008 14:08:29 +0100, mosfet <[EMAIL PROTECTED]> wrote: > About the WM6.1 issue, in the case newer gcc\binutils doesn't solve the > issue I am following another > track. > Actually the problem with WM6.1 comes from a modification done in the > kernel(nk.ex

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-06 Thread mosfet
About the WM6.1 issue, in the case newer gcc\binutils doesn't solve the issue I am following another track. Actually the problem with WM6.1 comes from a modification done in the kernel(nk.exe) and especially in the loader. What you need to know is the fact Microsoft give access to Windows CE source

Re: [Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-06 Thread mosfet
On Sat, 06 Dec 2008 07:55:25 +0100, Danny Backx <[EMAIL PROTECTED]> wrote: > Actually I think it's time to move to new versions of the tools. That > includes gcc itself. Vincent has done excellent work on getting a cegcc > to work based on gcc-4.3.2, we should pick that up. > > Opinions ? > >

[Cegcc-devel] Windows Mobile 6.1 compatibility

2008-12-05 Thread mosfet
Pedro, I forgot to ask you if you have time, would it be possible to incorporate into cegcc a recent version of binutils >= 2.18.50. I was looking into mingw mailing list and I found this : - "FWIW recent 2.18.50 snapsho

Re: [Cegcc-devel] Enlightenment Libraries Fundations port

2008-11-23 Thread mosfet
Hi, I tried it and I find it amazing ... I have developped a small application in C++/WTL but I would like to rewrite it using this new framework. I have some questions, what is the license ? Can I develop some commercial software with it ? I see that your are using zlib, libjpeg, libpng but you c

Re: [Cegcc-devel] LLVM vs gcc

2008-11-15 Thread mosfet
On Sat, 15 Nov 2008 11:08:46 +0100, janrinze <[EMAIL PROTECTED]> wrote: > On Fri, 2008-11-14 at 11:10 +0100, mosfet wrote: >> Hi, >> >> I wanted to know if some people have already tried the llvm compiler that >> may be the next open source compiler. >> Do

[Cegcc-devel] LLVM vs gcc

2008-11-14 Thread mosfet
Hi, I wanted to know if some people have already tried the llvm compiler that may be the next open source compiler. Do you know if we can compile arm platform ? I am asking because from what I read, tllvm would have a clean architecture and would be easier to work on it.

[Cegcc-devel] Fwd: Re: question about what to do for the libpng port

2008-11-06 Thread mosfet
Original Message Subject: Re: [Cegcc-devel] question about what to do for the libpng port Date: Thu, 06 Nov 2008 14:02:00 +0100 From: mosfet <[EMAIL PROTECTED]> To: Vincent Torri <[EMAIL PROTECTED]> On Thu, 6 Nov 2008 12:12:07 +0100 (CET), Vincent Torri <[

Re: [Cegcc-devel] question about what to do for the libpng port

2008-11-06 Thread mosfet
> the best way would be libpng to add 2 functions to open and close a file, > so that we can manage all the platform in a portable manner :) I agree with this last solution... But I don't understand the issue here because I thought cegcc implements all posix functions so why do you need to use Cr

Re: [Cegcc-devel] Script does't compile on ubuntu : posix enhancement

2008-06-23 Thread Mosfet
the script > #!/bin/sh into #!/bin/bash ? > > Just a thought.. > > Jan Rinze. > > On Mon, 2008-06-23 at 10:14 +0200, Mosfet wrote: >> I will check but actually it seems more complicated and finally I have >> >> changed the link sh->dash into sh->b

Re: [Cegcc-devel] Script does't compile on ubuntu : posix enhancement

2008-06-23 Thread Mosfet
//www.lucas-nussbaum.net/blog/?p=274 On Sun, 22 Jun 2008 20:03:08 +0200, Danny Backx <[EMAIL PROTECTED]> wrote: > Thanks for the info. I've just committed a change. Can you verify it ? > > Danny > > On Sat, 2008-06-21 at 16:36 +0200, Mosfet wrote: >

[Cegcc-devel] Script does't compile on ubuntu : posix enhancement

2008-06-22 Thread Mosfet
Hi, I am trying to compile cegcc on a ubuntu 8.04 and build-cegcc.sh doesn't compile. After some research I've learnt that this distro now uses a new shell called dash that is more rescrictive and respect only POSIX. This was a change thas was made for two reasons : 1) dash is smaller an

Re: [Cegcc-devel] mingw32ce and implementations of missing posix functions

2008-06-19 Thread Mosfet
e same but it may be a bad idea. On Thu, 19 Jun 2008 16:05:50 +0200, Danny Backx <[EMAIL PROTECTED]> wrote: > On Thu, 2008-06-19 at 13:56 +0200, Mosfet wrote: >> I would like to discuss about mingw32ce and the way it's implemented. > [..] >> I kn

[Cegcc-devel] mingw32ce and implementations of missing posix functions

2008-06-19 Thread Mosfet
Hi, I would like to discuss about mingw32ce and the way it's implemented. >From what I understand you comment missing include files on the windows CE platform like this : /* Define to 1 if you have the header file. */ #undef HAVE_ERRNO_H or like that #if _GLIBCXX_HAVE_ERRNO_H #in

Re: [Cegcc-devel] Some explanations

2008-06-18 Thread Mosfet
Wed, 18 Jun 2008 20:04:38 +0200, Danny Backx <[EMAIL PROTECTED]> wrote: > The gcc-4.3.0 directory is not stable, and I'm not supporting it right > now. Is this what you're referring to ? > > Danny > > On Wed, 2008-06-18 at 18:13 +0200, Mo

[Cegcc-devel] Some explanations

2008-06-18 Thread Mosfet
I saw that amongst modifications you are modifying src\gcc\gcc\config\arm\ieee754-df.S src\gcc\gcc\config\arm\ieee754-sf.S src\gcc\gcc\config\arm\lib1funcs.asm and your are replacing everybeq LSYM(Lad_s) by beq LSYM(ad_s) What does it mean ? --

[Cegcc-devel] GDB : compilation error

2008-06-18 Thread Mosfet
Hi, When trying to compile src from SVN trunk I get the following error with GDB *** BFD does not support target arm-unknown-mingw32ce. *** Look in bfd/config.bfd for supported targets. make[1]: *** [configure-bfd] Erreur 1 make[1]: quittant le répertoire « /mnt/compil/repos_vincent/src

Re: [Cegcc-devel] Feedback on compiling CEGCC 4.3.x

2008-06-17 Thread Mosfet
I am still stuck with this compilation error, it seems cegcc 4.3 don't take the config/mingw32ce ... mkdir -p ./arm-mingw32ce/bits/stdc++.h.gch /home/Vincent/cegcc/src/build-mingw32ce/gcc/./gcc/xgcc -shared-libgcc -B/home/Vincent/cegcc/src/build-mingw32ce/gcc/./gcc -nostdinc++ -L/home/Vince