Database Info

visual studio 2008/embeded visual c++ lib/dll

Hi there,
if anybody uses win32 for tornado programming and could help:
i'm facing a problem that can't load lib/dll/h files.
All i get is linking error or even visual studio stops with an error message.
After reinstalation of visual studio message is the same.
So if you have a simple smartphone app with using some dynamin dll/lib, please send it to me.
Thanks.
Saulius

Are you using VS 2005/2008 or embedded C++ 4.0?
In my past experience with C++ 4.0 dlls, you have to register the dll, like on a desktop...there is a regsrvce program that on the embedded Tools install.
With VS you have to first create a mobile conpatible DLL and add it to you application project. It should work assuming the .NET CF is the same (and installed). If you're using VS 2008, you'll need CF 3.5 installed. If your trying to use an embedded C++ 4.0 dll in a .NET application, I would assume you still need to add it to the project and VS will create an interop version for deployment.

Question about developing for WM

Hi, I'm trying out developing for my O2 Flame and was wondering if I could use the GNU GCC Compiler for compiling my programs, as I do not have the money for Visual C++ or something like that. If the GCC Compiler can't, can anybody recommend me a free compiler, Thanks in advanced.

You can use the free version of Embedded Visual C++ 4.0, although it was originally designed for development for WM 2003. If you limit the main menu to two items then WM 5.0 onwards will display the program correctly with the buttons either side of the SIP. Any more, and it switches back to the WM2003 style command bar.
For C++ you can develop in the Win32, ATL or MFC models.
http://www.microsoft.com/downloads/d...displaylang=en
Don't forget to apply SP4 to it after install. (Same page, use the link at the bottom)
It also uses an earlier WM2003 emulator that runs a half way x86/Arm code setup. It works, but the standalone emulator manager with the relevant WinMo SDK does a better job. You will only be able to fully debug the code created in by EVC 4, in its own WM2003 emulator or on a real device, not in the standalone emulator. The standalone emulator images will run your code so you can test it, but you cannot set breakpoints, examine variables. etc.
If you want to develop stuff for GPS, then you may have to add the relevent headers and lib files from later versions of the SDKs
The GNU compiler can be made to work, but I have never tried it.

Thanks for your help!

[Q] Problems using Haret

Hi there everybody!
I've been struggling to try porting android for a new phone but can't event pass the first step.
I've a so called TMN Bluebelt ( ZTE Xiang ), equipped with a Qualcomm MSM7225 processor running Windows Mobile 6.1.
I've been searching on this matter here and in other places and decided to start it.
Downloaded some haret versions and tried a couple of configurations but no luck.
I found that MSM7225 needs a special patch for haret to work successfully and found that same compiled version. Tried everything but all output i get from haret in my phone is :
HaRet boot
Shutting down hardware
Turning off MMU...
Click to expand...
Click to collapse
I found another post saying that this processor can have some problems turning mmu on/off so i decided to investigate further down. I downloaded CeGCC 0.59 and tried compiling haret from git repo.
Now the problem is, when i try to run my compiled version of haret i get
"haret.exe is not a Pocket PC valid application". I'm completely lost. I've experience dealing with linux/windows OS's but not Windows Mobile, so i don't know what to do next.
Any kind soul with good ideas regarding this?
Help would be appreciated.

Well it seems like nobody here knows how to deal with this.
It's a shame, because I don't either
I've been goggling on this matter yet and i found some clues on what can be the problem.
Newer versions of mingw32ce are using a library called libgcc_s_sjlj-1.dll and others to split the code and produce smaller binaries.
I stumbled on one thread (can't place the link) and checked this application, the Dependency Walker (can't place the link). It seems that my binary is using that dynamically linked libgcc version whereas the "officially" compiled versions don't. I guess the error i'm getting about my binary being an invalid "Pocket PC App" is connected with this. Maybe i'll need to compile it too. I tried to find this library's source code but no luck. Can't seem to find it in the cegcc project cvs.
Meanwhile I installed a vm with Virtual Studio and eVC++ 4 and tried to compile haret with the .vcp project that is in the source folder. One more time i got a problem converting the vcp to the newer VS format. It seems that bakefile, the utility used to produce the eVC related files generates incompatible configuration strings with VS converter.
(can't place the link)
The same way, I'm unable to open the project with eVC++ 4, and I can't trace the error.
Now I'm giving up on this for some time. I'll wait for someone to help me or, at least, until Handhelds come up with their page again (it seems they're in undergoing renovations of it for months. I hope this time, 1st week of March, will be definitive).

[Q] AOSP Build/Emulator - newbie questions

Hello,
I'm trying to test some fixes for android issue 74754 (it is on code.google.com, p, android, issues - sorry newbies cannot post links...)
(I have posted possible solutions on that thread; but since google does not fixes it, I'm taking matters in my own hands).
So I set up an environment in a clean kubuntu 14.10 64bits as per instructions on
source.android.com, source, building.
I'm first trying to build and run the "vanilla" AOSP and reproduce the bugs there, so I did no patching yet. I go through the steps from source.android.com to "lunch" and build for the emulator target, then run "emulator" without args (which works with default settings). All runs seamlessly from the host PC point of view.
Questions:
1 - If I build for full-eng or aosp_arm-user (so the target and emulator is for arm7), the emulator runs Ok (bearable performance, I'm using an old Core2Duo 2.93GHz, 8GB RAM, Quadro600 video card, nvidia drivers), but if I try full_x86_64-eng, or anything x86 (I'd like to try kvm), everything builds Ok, but the emulator just shows a black screen (while eating up 100% of one CPU core) - tried the emulator with and without kvm, with and without acceleration. I'm Ok with using only the arm emulation, but if anyone has an A-HA! tip to make the x86 emulation work, it will be most welcome (note: I've solved all error messages issues; there is no library missing messages, no core dumps, no nothing. The emulator just seems to be booting forever - as if running the arm emulation is much faster than the x86, which I assume to be the opposite)
2 - Although I was able to reproduce part of the bug in the emulator, the other part includes creating an event in the calendar app. Problem is, when doing that, the system says the event can only be created if I have defined a calendar to sync to (why can't one use a calendar app without being "in the cloud" is a "big brother" issue unrelated to the bug), but then I create an email account, and start getting repeated "Unfortunately, Email has stopped". The emulator has internet access (email account creation passes the smtp/imap tests, and web browser works).
Any hints?
Thanks!

problems with OP7 chinese version, AA int rom, android 10, intelligent hub

I have a brand new OP7 from China, with AA international android 10 rom installed.
problem I am having, my employer requires device management through vmware intelligent hub application for device enrollment, and cert installations.
during the setup and enrollment process, I get an error saying failed to create install url, support team has never seen this error before, and I can't find much reference to the issue online.
Any suggestions where to start with this?

Probably compatible issue with android 10.
Try to clean install of 10.0.1. For me at least it solved some apps that didn't worked even in first original android 10 release.

As usual, the solution here is downgrading to android 9, due to providers not being willing to believe there is an issue with their software. I used the rollback package provided for those running Q betas earlier in the year. This put it back to 9.5 and I was able to get the vmware product to work. I will hold off on updating to 10 when they get their head out of their butts.
Note to the vmware developers, your product has been broken on android 10 since the early betas in the spring, but still, you fail to address the problem. Your support is a joke.