Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2008-12

WinCE 2.2.3 Snapshot Problem

11 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Henry Vermaak
to Unknown author

2008/12/9 :
---->8----

Show quoted text 17 lines
I get the following error message and compilation fails when I try to build a new project: "The system.ppu was not found in the FPC directories. Make sure fpc is installed correctly and the fpc.cfg points to the right directory." There is a wince-arm system.ppu on my setup at: C:\Lazarus\fpc\2.2.3\units\arm-wince\rtl\system.ppu And the only fpc.cfg is the vanilla one installed from the snapshot at: C:\Lazarus\fpc\2.2.3\bin\i386-win32\fpc.cfg I don't know how to proceed from here? Is WinCE 2.2.3 known to be broken at the moment? I did try with the 2.3.1 snapshots last week and I couldn't get those to work either.

have you had a look at the paths inside the fpc.cfg? do they point at the right units? for example, my fpc.cfg contains this:

# searchpath for units and other system dependent things -FuC:\FPC\2.2.3/units/$FPCTARGET/
-FuC:\FPC\2.2.3/units/$FPCTARGET/*
-FuC:\FPC\2.2.3/units/$FPCTARGET/rtl

you should have something similar.

henry

Reply by email

Vincent Snijders
to Unknown author: An embedded and charset-unspecified text was scrubbed... Name: not available Url:…

2008/12/9 :

Show quoted text 5 lines
Hello, I don't know how to proceed from here? Is WinCE 2.2.3 known to be broken at the moment? I did try with the 2.3.1 snapshots last week and I couldn't get those to work either.

I can confirm fpc 2.3.1 for arm-wince is broken, see http://www.hu.freepascal.org/fpcircbot/cgipastebin?msgid=4740

Feel free to create a fpc bug report about it.

Vincent

Reply by email

Vincent Snijders
to Unknown author: An embedded and charset-unspecified text was scrubbed... Name: not available Url:…

2008/12/9 :

Show quoted text 24 lines
Hello, I was hoping to see how the LCL WinCE was progressing as I have not been able to look at it for six months or so. I use Lazarus for Windows from SVN routinely but I have always found building the WinCE cross-compiler and library much harder. So that I don't disturb my normal working environment I decided to install a test setup in a VirtualBox from snapshots so I downloaded and installed today's Lazarus snapshots for FPC 2.2.3: Lazarus-0.9.27-17734-fpc-2.2.3-20081209-win32.exe Lazarus-0.9.27-17734-fpc-2.2.3-20081209-cross-arm-wince-win32.exe A new Win32/i386 application compiles and runs without issue. However when I change the compiler settings to: LCL Widget Type - wince (beta) Target OS - WinCE Target CPU family - arm I get the following error message and compilation fails when I try to build a new project: "The system.ppu was not found in the FPC directories. Make sure fpc is installed correctly and the fpc.cfg points to the right directory."

AFAIK, this is not a compiler message, but a message from the IDE.

What is the compiler path setting in the environment options?

Vincent

Reply by email

Felipe Monteiro de Carvalho
to Unknown author

Go to the environment options dialog and check if the compiler is the right one.

I think that Lazarus comes preconfigured to use ppcx86.exe but it should actually use fpc.exe which will choose the correct compiler.

Don't change anything in your fpc.cfg file.

Felipe Monteiro de Carvalho

Reply by email

Henry Vermaak
to Unknown author: An embedded and charset-unspecified text was scrubbed... Name: not available Url:…

2008/12/9 :

Show quoted text 11 lines
Thanks Henry, My search paths match yours: # searchpath for units and other system dependent things -Fuc:\Lazarus\fpc\2.2.3/units/$FPCTARGET/ -Fuc:\Lazarus\fpc\2.2.3/units/$FPCTARGET/* -Fuc:\Lazarus\fpc\2.2.3/units/$FPCTARGET/rtl The fpc.cfg is the default one installed by the snapshot. I have also searched the system for any other fpc.cfg files that might have got in the way.

o.k. have you changed the compiler path to be used (in environment options)? you have to choose the ppcrossarm.exe.

henry

Reply by email