@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet
Page: 1 2 3



Comments:

<0> anybody using gcc under cygwin ?
<1> ##workingset
<1> Hey.
<1> Is are there any IRC channels dedicated to the WinCE ports of GCC?
<1> Such as CEgcc http://cegcc.berlios.de/
<0> TFGBD : Interesting ..never saw that before ... is it working ?
<1> It seems to be.
<1> There are many programs ported with it.
<1> But I have one major issue with it and various other CE GCC ports.
<0> being ?
<1> They all seem to only support ARM!
<0> Yes, well AFAIK most recent WCE versions only support ARM too
<1> Folks need to realize that CE supports ARM, MIPS, SH3, SH4, SH5, and x86.
<1> You are talking consumer devices.
<0> yes
<1> I am speaking about plain embedded Windows CE.



<1> To call Pocket PC Windows CE is misleading.
<1> Since it is just one IMPLEMENTATION or distro of Windows CE.
<0> Yes I know but isn't it so that for WinCE the vendorneeds to provide a profile ?
<1> It is a MS customized stadard platform (like a linux distro, I guess
<0> In VCEmb there are only four profiles Smartphone, pocket and emulation versions of both
<1> Yeah, Windows CE is componentized and can be heavily customized.
<1> That is because you only have the Pocket PC 200x SDK installed.
<1> It all depends on the SDK.
<0> Also IIRC, WinCE porting is basically a hardware provider issue. He needs to package and provide an SDK
<1> If you install the CE 4.2 or 5.0 standard SDK, you will have various ARM, MIPS, SHx, and x86 targets available.
<1> Agreed.
<0> so perhaps you just need the mips / sh3 gcc compiler ?
<1> Though, its easy enough to make your own or just use the STANDARDSDK.
<0> are there WinCE specific IRC ?
<1> Channels?
<0> yes
<1> Not that I know of.
<0> sad
<1> Just a handful of very small channels that I already idle in and ...
<1> the warez ones... :/
<1> #winprog on efnet seems to have some experts...
<1> but they are general win32 and not really wince specific.
<0> yes both API do differ alot
<1> I did not expect to meet someone that knows a bit about CE here.. :P
<0> well I have already struggled a bit with it
<0> using wxwindows
<1> Trying to port it?
<0> no it already runs just fine
<1> Ok...yeah I remember.
<0> delivers 100% portability betwee w32 wce and linux
<0> with a bit of patches of course ...
<1> Wow, Nice.
<1> But I bet its ARM only, eh! :P
<0> it is compiled with VC so I presume with the right profile porting is possible
<1> Ok, nice.
<1> What have you ported with it?
<0> this : http://www.adaptiveplanet.com/mobile/mainframe.html
<0> then click on 'applicatievoorbeelden'and then FORM application
<1> I see.
<1> Neat.
<0> yes I was very pleased with it.
<0> beats MFC on WCE ...
<1> :P
<1> Can you make your x86 build pubicly available?
<1> I ***ume you used one for testing at some point...
<0> ?
<1> x86 emulator.
<0> euh, i really do not follow ...
<1> In addition to the ARM build, did you make an x86 build to test it in the emulator?
<0> yes with debugging even
<1> Ah, cool.
<0> want the libs ?
<1> Is there a download on your site>
<0> no, got it only on my dev. system
<0> hold on ...
<1> Why are there screenshots and no download, then? :P
<0> because It is not really available yet ... currently just used internally and for showcase purposes
<1> I see.
<0> we have other soft we need to port first ...
<1> Ah.
<1> This is for a product your company will sell?



<0> no I do not think so
<0> as said probably just for internal use
<1> I see.
<1> What is it your company does?
<0> Long and complicated story ... have some time ?
<0> it started of to design a new development paradigm
<1> Does this support using a CE commandbar control for menus/toolbars or only the AYGshell based CE menubar for Pocket PC?
<0> (using components and C)
<0> I 'think' the first ... you use the WxW api for it which hides all details
<1> The CE commandbar is the more cl***ic CE control that is often at the top, supports rebars, etc.
<1> The CE menubar is the Pocket PC menubar at the bottom.
<0> sorry do not know ... as said wxw takes care of it but it does appear at the bottom
<0> but you can have extended buttons at the bottom
<1> http://www.vbce.com/code/vbce6/commandbar/CommandBar.gif
<0> I think it is the AYGShell then.
<1> http://www.pocketnow.com/html/portal/reviews/0000000186/review/soft/CEZoom4.gif
<1> Aygshell CE Menubar.
<1> Ok.
<1> I figured :/
<0> the component toolkit we have built it now being ported to WCE
<1> Plain custom CE?
<0> yes
<1> Cool.
<1> So I guess you will opt for the commandbar there..
<0> our toolkit does not depend on a GUI
<1> Does this toolkit support CE 3.0? (Handheld PC 2000, Pocket PC 2000, Pocket PC 2002)
<0> so which commandbar depends on the GUI lib that is used with our toolkit
<1> Or just CE 4.2+
<0> Depends on the API available on 3.0
<1> Are you using EVC4?
<0> yes
<1> I see.
<0> but that is not really important
<1> I guess it may take some modification to revert to evc3
<0> our toolkit supports many compilers
<1> Oh
<1> Ok.
<0> Well we need threading and CreateEvents to signal applications running on CE
<0> so we do not need a lot from the OS but some things
<1> I see.
<0> and since we are currently porting we do not know yet what our
<0> minimal requirement is
<1> I see.
<0> but I would guess that 3.0 is possible
<1> Hopefully you can target at least CE 3.0 also.
<0> it is weird that 'industrial' versions still use 3.0
<0> why hasn;t it been upgraded ?
<0> it are all just build levels no ?
<1> What do you mean?
<1> Most newer industrial devices I have seen use 4.x or 5.0.
<0> well 5.0 4.2 3.0 are just build levels of the same OS
<0> but then windows mobile 4 and 5
<0> with the complete GUI
<1> I wouldn't call "Windows Mobile" the "complete" GUI.
<1> it is just one implementation of CE.
<1> CE does not even need a GUI>
<1> It can run headless as in a router, etc.
<0> no but with 'today' and such I mean
<1> The Pocket PC shell.
<1> Yeah.
<1> To Microsoft, the Windows Mobile team is like another "customer" of the embedded OS..
<1> The same as Wyse for their thin clients.
<1> Thats how I understand it.
<0> well with special previleges probably ;-)
<1> Oh of course :P
<1> I'm sure they get more source than Wyse ;P
<0> and have more impact on it
<1> And sometimes they seem to give things to the embedded OS team..
<0> I have worked with a customer who found a bug in CE
<1> Like the newer Pocket IE that was introduced in CE 4.2
<1> Hehe.
<1> Where? :P
<0> and MS told him he could not patch the OS nor could they tell
<1> Oh? :P


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #gcc
or
Go to some related logs:

#centos
yum madwifi linva
quotes on voting-positive
bash without eval
python-curses suse 10 rpm
changin localhost gentoo
ubuntu dapper disable animation
xarragon
namesserver gentoo
bacula netgear error



Home  |  disclaimer  |  contact  |  submit quotes