Hello
I'm new to cegcc.
I've installed the current cygwin-version and unpacked
cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2 in /opt of my cygwin-installation.
I put /opt/mingw32ce/bin at the beginning of my PATH
Wenn I call arm-mingw32ce-g++ it say's nothing. I can't compile anything and
there is no
Hi,
I'm not saying my version is perfect, but did you try this?
http://www.unsads.com/~squalyl/cegcc/mingw32ce-4.1.zip
I'ts cross compiled from linux for mingw. it does not rely on cygwin for
running, but there should no problem to run on cygwin too. Maybe you'll have
a better luck?
Keep me info
Could you open a bugzilla and attach your coredll.dll ?
Thanks
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
__
Vincent R. wrote:
>
> Could you open a bugzilla and attach your coredll.dll ?
> Thanks
>
Danny privately analyzed the file and objdump is correct it seems, so there
is no bug. Thanks.
-
Regards,
İsmail DÖNMEZ
--
View this message in context:
http://n2.nabble.com/Can-t-see-the-exports-
In the examples at http://danny.backx.info/download/cegcc/demo.tar.gz
you can see source and compiled version for two DLLs, and objdump for
both.
The lib1.dll works, lib2.dll doesn't, as shown in testapi2 output :
Started processing DLL(lib1.dll)
lib1.dll doesn't know about open
li
On Wed, 09 Dec 2009 12:01:45 +0100, Danny Backx
wrote:
> In the examples at http://danny.backx.info/download/cegcc/demo.tar.gz
> you can see source and compiled version for two DLLs, and objdump for
> both.
>
> The lib1.dll works, lib2.dll doesn't, as shown in testapi2 output :
> Started processi
> It reminds me what was reported the first time someone talked about
issue
> between cegcc and Windows Mobile 6.1.
> In this initial report there was something about the size and under some
> value, it was working fine.
>
Here is extract of the original post :
"I tried to modify binutils/bfd/pe
İsmail cartman Dönmez wrote:
> Vincent R. wrote:
>> Could you open a bugzilla and attach your coredll.dll ?
>> Thanks
>>
>
> Danny privately analyzed the file and objdump is correct it seems, so there
> is no bug. Thanks.
Well there's clearly at least a bug in objdump, since it is displaying
gi
On Wed, Dec 9, 2009 at 4:45 PM, Dave Korn-2 [via cegcc-devel]
wrote:
> İsmail cartman Dönmez wrote:
>> Vincent R. wrote:
>>> Could you open a bugzilla and attach your coredll.dll ?
>>> Thanks
>>>
>>
>> Danny privately analyzed the file and objdump is correct it seems, so
>> there
>> is no bug. Th
On Wed, 2009-12-09 at 15:01 +, Dave Korn wrote:
> Also, what's going on there with the VMA/LMA for .data? It can't possibly
> really be supposed to be 32 meg below the base address that the DLL gets
> loaded at!
Considering that these are "system DLLs", I am not sure whether what
we're seei
On Wed, 9 Dec 2009 06:58:12 -0800 (PST), İsmail "cartman" Dönmez
wrote:
> On Wed, Dec 9, 2009 at 4:45 PM, Dave Korn-2 [via cegcc-devel]
> wrote:
>> İsmail cartman Dönmez wrote:
>>> Vincent R. wrote:
Could you open a bugzilla and attach your coredll.dll ?
Thanks
>>>
>>> Danny privat
Vincent R. wrote:
>
> On Wed, 9 Dec 2009 06:58:12 -0800 (PST), İsmail "cartman" Dönmez
> wrote:
>> On Wed, Dec 9, 2009 at 4:45 PM, Dave Korn-2 [via cegcc-devel]
>> wrote:
>>> İsmail cartman Dönmez wrote:
Vincent R. wrote:
> Could you open a bugzilla and attach your coredll.dll ?
>
OK I had a look with PE Explorer tool and it doesn't detect any exports
either.
Let me make some assumptions, are you extracting those files from ROM with
the kind of tool
you can find on XDA website ?
IT might explain your corrupted binaries.
-
On Wed, 9 Dec 2009 19:40:37 +0200, İsmail Dönmez
wrote:
> On Wed, Dec 9, 2009 at 6:37 PM, Vincent R.
wrote:
>>
>> OK I had a look with PE Explorer tool and it doesn't detect any exports
>> either.
>> Let me make some assumptions, are you extracting those files from ROM
>> with
>> the kind of tool
On Wed, Dec 9, 2009 at 6:37 PM, Vincent R. wrote:
>
> OK I had a look with PE Explorer tool and it doesn't detect any exports
> either.
> Let me make some assumptions, are you extracting those files from ROM with
> the kind of tool
> you can find on XDA website ?
> IT might explain your corrupted
I got qt core and gui compile, but the resulting binaries are huge (9MB O_o)
and they don't run on my htc wizard.
Dig on the qt-ce mailing list to see the status of qt-cegcc.
starting from here:
http://lists.trolltech.com/pipermail/qt-wince-interest/2009-November/000750.html
regards
sebastien
On Wed, Dec 9, 2009 at 7:58 PM, Vincent R. wrote:
> On Wed, 9 Dec 2009 19:40:37 +0200, İsmail Dönmez
> wrote:
>> On Wed, Dec 9, 2009 at 6:37 PM, Vincent R.
> wrote:
>>>
>>> OK I had a look with PE Explorer tool and it doesn't detect any exports
>>> either.
>>> Let me make some assumptions, are y
Thorsten wrote:
>
> Hello
>
> I'm new to cegcc.
> I've installed the current cygwin-version and unpacked
> cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2 in /opt of my cygwin-installation.
> I put /opt/mingw32ce/bin at the beginning of my PATH
>
> Wenn I call arm-mingw32ce-g++ it say's nothing. I ca
On Wed, 9 Dec 2009 13:40:48 -0800 (PST), İsmail "cartman" Dönmez
wrote:
> Thorsten wrote:
>>
>> Hello
>>
>> I'm new to cegcc.
>> I've installed the current cygwin-version and unpacked
>> cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2 in /opt of my
>> cygwin-installation.
>> I put /opt/mingw32ce/bin at
On Wed, 09 Dec 2009 12:01:45 +0100, Danny Backx
wrote:
> In the examples at http://danny.backx.info/download/cegcc/demo.tar.gz
> you can see source and compiled version for two DLLs, and objdump for
> both.
>
> The lib1.dll works, lib2.dll doesn't, as shown in testapi2 output :
> Started processi
Danny Backx wrote:
> On Wed, 2009-12-09 at 15:01 +, Dave Korn wrote:
>> Also, what's going on there with the VMA/LMA for .data? It can't possibly
>> really be supposed to be 32 meg below the base address that the DLL gets
>> loaded at!
>
> Considering that these are "system DLLs", I am not
21 matches
Mail list logo