Can someone with a good heart and mind HELP PLEASE? (Installing packages) lazarus / 10-Designer ---------------------------------------------------------------------- epergola · 2009-06-07 01:21 When I first tried Lazarus I was astonished! I loved it. Then I tried to do something useful and I got stuck with never ending searching wiki and dozens, actually hundreds of web pages to no avail. I hope someone  can *really* help: clear, concice, to the point. I never got a satisfactory answer to why a Lazarus app that  calls a Delphi dll runs ok when the target is win32, but on the Windows Mobile Emulator 6.1 I get the dreaded error ".. not a valid Pocket Pc application". Ok so I moved away from it. I wrote a simple Lazarus app, that uses lnet to connect to a server that runs on the desktop. AGAIN, the app targeted to win32 works just fine, but when I recompile for Wince/arm, it never connects to the server! Now: a) the setting are : LCL widget wince (beta)     target OS winCE     target CPU arm     targetprocessor (Default)    and that seems to be right (infact another Lazarus app with no lnet/sockets, nor dll import, runs fine on WM 6.1) b) the equivalent sample app in Delphi Prism with the socket connection to the server on the desktop runs    just perfect. So I conclude the emulator is set just right, conected to the desktop with MS loopback just    right or the Prism app would not run on the same emulator. Finally, I thought it would be better to install the lnet visual package, maybe works better. I tried to install lnetvisual.lpk and I get    "The sistem.ppu was not found in the FPC directory. Make sure fpc is installed correctly     and the fpc.cfg points to  the right directory" I have spent hours searching the web: the answer I found were all basically 'the ppu file is not in the poath'?????  Of course that is what the message says! Could someone answer these question please? 1. which .ppu is not found? I run Lazaruson Win32, but I want to make (also) apps for arm-winCE.    sdo in the hierarchy (lazarus\fpc\......) where is this ppu?    So no matter how i staredted the IDE: I am here now, what do I do, what/how do I set the things    I need to install the package? Even if i have to exit the ID what are the concrete steps one by one to get the    lnetvisual package in the palette give the conditions I have stated? 2 .Once I find what this blessed 'right directory' is, how do I make the 'fpc.cfg' point to it? Do we have a tool?     Can anyone make a simple valid concrete example (hopefully not remanding to wicki and stuff from which    I got nothing)?  Sorry if I sound harsh, but after days of frustration it'snot easy to stay seraphic.... ---------------------------------------------------------------------- Martin_fr · 2009-06-07 01:45 I don't have an answer to your specific issue, but I can give you a few pointers, (those pointers should be valid cross all platforms) Quote1. which .ppu is not found? I run Lazaruson Win32, but I want to make (also) apps for arm-winCE.    sdo in the hierarchy (lazarus\fpc\......) where is this ppu? I assume you recompiled lazarus for wince (that is at least the LCL and all packackes used.) Did you do the same for FreePascal? Otherwise the System ppu for wince does not exist. Or maybe you compiled the Systme.ppu with a diff version of fpc, which may also lead to this error (the file does exist, but is unusable) (This includes a micup between the windows and wince ppu) Anyway, if it is not that, and you have a system ppu, you need to get more verbose feedback from fpc Use the option -va (see http://www.freepascal.org/docs-html/user /usersu13.html#x36-430005.1.2 ). It will create a massive amount of output, every single attempt of finding a file, and all location searched etc. Copy the output to an editor an search for "system.". This should give you some more hints (under lazarus, the context menu on the message window has an entry "copy all and hidden) Be aware compiling with -va can take a while. 2 .Once I find what this blessed 'right directory' is, how do I make the 'fpc.cfg' point to it? If it really is a missing config, then you need to edit the fpc config by hand (or enter the options in Lazarus compiler settings (path tab)) It is -Fu you are looking for ( http://www.freepascal.org/docs- html/user/usersu14.html#x37-440005.1.3 ) Good luck Edited by Vincent: added quote tags. ---------------------------------------------------------------------- epergola · 2009-06-07 02:53 Thanks Martin. If you want to help me a bit more I would appreciate it. Could you answer these questions, if you have an answer? I will unistall and start with a clean install. Ok I restate: I want to do ALL development on win32 but also target some apps to winCE.  Is THAT simple, nothing more! No want to  hear recompiling compilers, trunks,vn etc. 1. I have these files:    lazarus-qt-0.9.26.2-fpc-2.2.2-win32.exe    lazarus-0.9.26.2-fpc-2.2.2-win32.exe    lazarus-0.9.26.2-fpc-2.2.2-cross-arm-wince-win32.exe     what I did before I installed      lazarus-0.9.26.2-fpc-2.2.2-win32.exe    and then      lazarus-0.9.26.2-fpc-2.2.2-cross-arm-wince-win32.exe    I did not install any fpc by itself, it looks like the lazarus    installation also installs fpc. (I read an entire    'How to Install Lazarus' and I get nothing out of it).    Is this correct? Do I  need to install also      lazarus-qt-0.9.26.2-fpc-2.2.2-win32.exe *what is it?) 2. Once I have started with this clean installation, and I  try to     install the lnetvisual.lpk, would it install automatically or do I     need  to  take   another univeristy course to learn how to in stall     a package   in   Lazarus? -:) 3. Supposing all works fine, I have the lnetvisual.lpk installed.     My Lazarus was installed as win32 (optionally targeting winCE).     Well, I write an app (repeat i will NEVER develop in WinCE, always     in win32), I test it in win32 and it works.     Then I want to make a winCE version. Is it enough or not,     SIMPLY to change these  settings:        LCL widget wince (beta)        target OS winCE        target CPU arm        targetprocessor (Default)     and recompile and my neat simple beautiful app baby will work     like a charm in the WM 6.1 emulator? Without having to start     trembling to any mention of recompiling.... the compiler,     liine command nightmares, trunks, nvc, and all the goodies the     devil himself created for us programmer that do not     write/program/love/understand_much the visceral details of    compilers working? heheheh sorry... just joking. I thank you for the previous answer, I hope I could thank you again even nore for the... next. P.S. isthere someform of pay support? ---------------------------------------------------------------------- wes12 · 2009-06-08 19:56 Quote from: epergola on June 07, 2009, 03:21:50 amI never got a satisfactory answer to why a Lazarus app that  calls a Delphi dll runs ok when the target is win32, but on the Windows Mobile Emulator 6.1 I get the dreaded error ".. not a valid Pocket Pc application". You have not understood some basic principles. A Delphi DLL is compiled to run only on a Win32 system using an Intel CPU. WinCE is different to Win32, and an ARM CPU is different to an Intel CPU. The Windows Mobile Emulator emulates a WinCE system with an ARM CPU, so your Delphi DLL can never run, and you get the message ".. not a valid Pocket PC application". Quote from: epergola on June 07, 2009, 03:21:50 amOk so I moved away from it. I wrote a simple Lazarus app, that uses lnet to connect to a server that runs on the desktop. AGAIN, the app targeted to win32 works just fine, but when I recompile for Wince/arm, it never connects to the server! The Windows Mobile Emulator emulates ONLY a WinCE system. But the server is on your Win32 system. Why do you think that these two systems will be able to communicate with each other? They are two completely separate and isolated systems. Quote from: epergola on June 07, 2009, 03:21:50 amWell, I write an app (repeat i will NEVER develop in WinCE, always in win32), I test it in win32 and it works. But WinCE is very different to Win32. Everything in WinCE is smaller and some things work differently. You cannot develop in Win32 and then expect an app to immediately work in WinCE in the same way. You will easily solve many of your problems if you develop a new version of your application for WinCE from the start, rather than trying to re- use all the Win32 code.