Windows CE Interface/pt

From Free Pascal wiki
Revision as of 17:11, 20 July 2015 by FTurtle (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
WinCE Logo.png

This article applies to Windows CE only.

See also: Multiplatform Programming Guide

English (en) français (fr) 한국어 (ko) português (pt) 中文(台灣)‎ (zh_TW)

Configurando a interface do Windows CE

Para configurar a interface Windows CE você vai precisar usar ou o instalador add-on ou configurar a interface manualmente. As duas opções são detalhadas a seguir. Usar o instalador add-on é evidentemente muito mais fácil.

Usando o instalador add-on

Guia passo-a-passo:

  • Instale o Lazarus no Windows normalmente.
  • Baixe e instalee o instalador add-on para o Lazarus no Windows de Lazarus Testing no sourceforge.
  • Você pode compilar aplicações Win32 Arm-WinCE de dentro do Lazarus modificando nas opções do compilador :
    • Widget set
    • SO Alvo
    • CPU Alvo

Nota: certifique-se de que ambos os instaladores têm a mesma versão do FPC.

Configurando a interface Windows CE manualmente

O compilador e a biblioteca Run-Time para Windows CE estão disponíveis somente na divisão de desenvolvimento do FreePascal, a versão 2.1.x. Os snapshots do Lazarus vêm com esta versão do FreePascal.

Passo 1 - Para começar você vai precisar recompilar o compilador no Windows para criar um cross-compilador Windows CE - ARM. Há instruções aqui: WinCE_port.

Passo 2 - Você também precisa compilar a FCL (Free Component Library) com o compilador recém-criado. Instruções aqui.

Passo 3 - Ponha o arquivo batch abaixo na raiz do seu diretório de subversão do Lazarus e execute-o.

make lcl LCL_PLATFORM=wince PP=ppcrossarm.exe CPU_TARGET=arm OS_TARGET=wince

Isto deve compilar a LCL para Windows CE.

Passo 4 - Cross-compile o LazarusPackageIntf de modo que possa usar componentes visuais de terceiros. Vá a lazarus\packager\registration e faça:

make PP=ppcrossarm.exe CPU_TARGET=arm OS_TARGET=wince

NOTA: you need to specify $(LazarusDir)\packager\units\$(TargetCPU)-$(TargetOS)\ into your project's unit path (adding FCL as requirement should do that).

Step 5 - Now you can use Lazarus IDE to design,compile and debug your applications.

  • You can also use scripts similar to this for compiling your applications:
ppcrossarm.exe -Twince -FuC:\Programas\fpc\rtl\units\arm-wince -FDC:\Programas\arm -XParm-wince- test.pas
ppcrossarm.exe -Twince -FuC:\programas\lazarus\lcl\units\arm-wince -FuC:\programas\lazarus\lcl\units\arm-wince\wince -FuC:\Programas\fpc\rtl\units\arm-wince -FDC:\Programas\arm -XParm-wince- windowtest.pas

Compiling Windows CE project files with Lazarus IDE

NOTE: recently a "wincemenures.or" file is reported missing on linking. You just need to copy this file from "lazarus/lcl/interfaces/wince" to "lazarus/lcl/units/arm-wince" and everything will be fine.

Everything is just as you do with other interfaces and OSes. Make sure you have selected wince as widgetset in in Compiler Options->Paths and in Code tab page select WinCE as target os and arm as Target CPU. You also need to change compiler path in Environment options to point to your ppcrossarm.exe compiler.

Now IDE is ready to compiler your files.

Debugging Windows CE software on the Lazarus IDE

You can also debug applications created within Lazarus IDE.

Step 1 - In Lazarus IDE go to the menu Environment->Debugger Options. Change the debugger path to the directory with gdb for can get it from here

Step 2 - If you are using Microsoft Device Emulator Preview, launch(or restore)it.Make sure you've started emulator with 128mg of ram.Select a path for shared folders in emulator, add copy command to your .bat file used for building your application to copy the compiled exe file to your shared path.(as you can see in my .bat file).Here is a .bat file you can use to launch emulator with 128 of ram.

start deviceemulator.exe ".\ppc_2003_se\PPC_2003_SE_WWE_ARMv4.bin" /memsize 128 /skin 

After that just do 'save and exit' whenever you want to quit emulator,and launch it again from shortcuts created in your start menu.(the shortcuts with '(restore)').

Step 3 - Run Device Emulator Manager and in available emulators right click on the name of emulator and do cradle.Now Microsoft ActiveSync will be launched.If not in Micrososft ActiveSync Go to the menu File->Get connected.If still ActiveSync doesn't recognize the emulator.Uncradle and Cradle the emulator again.

Step 4 - Copy that file with File Explorer program in your emulator to \gdb directory.If it is your first time running emulator you have to create a gdb directory in 'My Pocket PC' folder which is your root(\) folder.(To make things even faster for your each build,with file explorer go to your shared folder,press ctrl+c in your exe file,go to \gdb folder and each time before you try to debug your application just press ctrl+v)

Step 5 - Now you can safely debug your application.gdb for wince will be will copy arm-wince-pe-stub.exe to \gdb folder and check if your application.exe file is there and will launch the program. If you encountered an error make sure the \gdb folder is created,arm-wince-pe-stub.exe and you exe file is there.Also most of the times because of big size of exe file you can not copy that into your \gdb file.So you have to call Microsoft Device Emulator Preview with 128mg of ram instead of default 64mg ram.

Some Hints

1. Programs remain in memory still after exiting from them. So you can't overwrite the .exe file. You have to use tools like Process Viewer from Microsoft which remotely shows all processes and allow you to kill them. Or use process killers inside the emulator. Process Explorer is another good option. One can get it from

2. Each time you are done with debugging your program don't exit from program.Do program Reset and then Debugger reset. Note that sometimes still program remain in memory,so you also have to kill the process too.

Installing and Using the Pocked PC Emulator

1 - You can download a Pocket PC Emulator from Microsoft here. First, download and install the file

2 - Next, be careful that there is a wrong information on the website. It will say that you need to install the Virtual Machine Network Driver, but the link provided on the website is broken. Instead, download Virtual PC 2007 here. This will install the necessary driver too.

3 - Now, go back to the first website and download and install the efp.msi file

Now you should have a fully functional PocketPC Emulator which can be utilized together with Lazarus to develop applications.

To run a Lazarus application on the emulator you can either use GDB via ActiveSync, or you can also just execute it directly.

Running an application on the emulator

1 - Go the the Windows Programs Menu --> "Windows Mobile Emulator Images" --> "PocketPC"

2 - If you never configured your shared folder for the emulator, do so now, by clicking on the menu File --> Configure once the emulator opens. Set it to a folder where you can access your Windows CE executable created with Lazarus.

3 - On the emulator click: Start --> Programs. Now select "File Explorer". Now select "Storage Card". Navigate until you find your executable and double click it to execute it.


An example of Lazarus+WinCE and the Free Pascal software used to test the cross compiler:

Capture 2.jpg Wince.PNG

How to add a new control

For example TButton.

TButton is defined in lcl/buttons.pp. This is the platform independent part of the LCL, which is used by the normal LCL programmer.

Its widgetset class is in lcl/widgetset/wsbuttons.pp. This is the platform independent base for all widgetsets (qt, carbon, gtk, win32, ...).

It's wince interface class is in lcl/interfaces/wince/wincewsbuttons.pp:

 TWinCEWSButton = class(TWSButton)
   class function  CreateHandle(const AWinControl: TWinControl; const AParams: TCreateParams): TLCLIntfHandle; override;

Every WS class, that actually implements something must be registered. See the initialization section at the end of the wincewsXXX.pp unit:

 RegisterWSComponent(TButton, TWinCEWSButton);

Also notice that DestroyHandle should be implemented to clean up memory utilized by the control.

See Also