No working code for WinCE with latest release !!! lazarus / 35-Windows CE ---------------------------------------------------------------------- HHJB · 2011-03-27 18:36 I've downloaded and installed (clean install) the latest Lazarus/FPC release: lazarus-0.9.30-fpc-2.4.2-win32.exe lazarus-0.9.30-fpc-2.4.2-cross-arm-wince-win32.exe All seemed to be fine. Application compiles with both targets 'i386-win32' and 'arm-wince'. The Win32 app also runs afterwards as expected. But the WinCE app doesnt. It seems to start but it does not show a window. Only in taskbar you can see the app. This behaviour can be reproduced with a form just containing an exit button. Under the last release 0.9.28 all runs fine. Also I am always using two different lpi-files for final build. One for win32 and one for wince (All same except LCLWidgetSet, TargetOS, TargetCPU). With the latest Lazarus release 0.9.30 the $(ProjOutDir) is not expanded correctly for wince anymore. All paths are expanded to $(TargetCPU)-$(TargetOS) correctly but $(ProjOutDir) remains to lib\i386-win32 instead of lib\arm-wince which overwrites its contents. If someone could have a look at this behaviour, I would appreciate. Thanks in advance. ---------------------------------------------------------------------- felipemdc · 2011-03-27 18:45 Have you tested in one of the emulators? Which one? Which WinCE device do you have? With which WinCE version? ---------------------------------------------------------------------- HHJB · 2011-03-27 19:32 I tested on real device (Motorola MC3100 - WinCE 6.0 Build 3122). ---------------------------------------------------------------------- felipemdc · 2011-03-28 09:49 Could you test in the emulators? (instructions in the wiki about how to download and use them) ---------------------------------------------------------------------- felipemdc · 2011-03-28 10:39 I just tested here in Windows XP with the WM 6.0 emulator and it worked fine. ---------------------------------------------------------------------- HHJB · 2011-03-28 15:02 So, I also tested with WM6.1 on real device (HTC) and it seems to work. But nevertheless WM6.1 is based on WinCE5 and not on WinCE6 which is broken with 0.9.30. Testing with emulators is a nice thing but the real world is not virtual (not based on emulators). ---------------------------------------------------------------------- felipemdc · 2011-03-28 15:33 Are you sure that your device has a ARM processor? I did some research and it says that Intel builds the processor. Intel usually (maybe always?) indicates x86. http://www.ruggedpcreview.com/3_handhelds_mc3100.html ---------------------------------------------------------------------- HHJB · 2011-03-28 15:46 Processor: Marvell, PXA32X-624MHz CPU Core: Intel Xscale Instruction Set: ARM And by the way, with 0.9.28-2.2.4 all worked fine! ---------------------------------------------------------------------- felipemdc · 2011-03-28 15:56 Does an application which doesn't use the LCL work? For example one using Windows.MessageBox() ---------------------------------------------------------------------- marcov · 2011-03-28 16:30 Note: http://bugs.freepascal.org/view.php?id=18951 ---------------------------------------------------------------------- HHJB · 2011-03-28 17:17 Tested and Running! So seems to have something to do with LCL. ---------------------------------------------------------------------- felipemdc · 2011-03-28 20:20 Could you find which revision broke it? The problem will be that the time between 0.9.28 and 0.9.30 was pretty huge, so not all revisions compile with all compiler versions ... anyway, insistently testing one should be able to find out which revision broke it. ---------------------------------------------------------------------- HHJB · 2011-03-30 14:52 So how to proceed? I have no resources to test all development sources between two (stable) releases. Whats about the second problem I described (maybe it has something to do with it). That was about when and how $(ProjOutDir) is expanded. Just create a .lpi with the $(TargetCPU) set to 'arm' and $(TargetOS) and $(LCLWidgetType) set to 'wince'. Then doubbleclick to open Lazarus and just say complile. If you have compiled a 'i386-win32' version before then all the generated .o, .ppu, etc. files will be created in 'lib/i386-win32' and not in 'lib/arm-wince' as expected. ---------------------------------------------------------------------- felipemdc · 2011-03-31 06:23 Searching for regressions is explained here: http://wiki.lazarus.freep ascal.org/How_To_Help_Developing_Lazarus#Dealing_with_regressions You don't have to test all possible versions, aproximately 10 tests should be enough. The scope should be testing revisions between 22000 and 30000 aproximately. You should start testing 26000. Download this revision from subversion and rebuild *only the LCL* and your app. Let's say that you install Lazarus 0.9.28.2 with FPC 2.2.4 in C:/Programas/lazarus282 And Lazarus 0.9.30 with FPC 2.4.2 in C:/Programas/lazarus30 Download Lazarus using Tortoise SVN for revision 26000 in C:/Programas/svnlazarus Because there were changes in the LCL build process, you might need to first build an old svn Lazarus to use as a base. I'm not sure if the current Lazarus will do it for this test. For building an older Lazarus, download lazarus rev 26000 and in it's dir put a batch script, build.bat: SET PATH=C:\Programas\lazarus30\fpc\2.4.2\bin\i386-win32 make pause And run it. If it doesn't build with FPC 2.4.2, try FPC 2.2.4 which comes with Lazarus 0.9.28.2 Then you open this IDE using a script: startlazarus --pcp=config Then set environment option for the correct compiler. Now rebuild the LCL for WinCE, rebuild your project and test. For further tests, you can simply update only the LCL directory of the Lazarus svn tree to the new revision, no need to update the entire tree. Then rebuild only the LCL for WinCE and test your app. This should be very fast. ---------------------------------------------------------------------- felipemdc · 2011-03-31 06:27 Quote from: HHJB on March 30, 2011, 04:52:50 pmWhats about the second problem I described (maybe it has something to do with it). That was about when and how $(ProjOutDir) is expanded. Just create a .lpi with the $(TargetCPU) set to 'arm' and $(TargetOS) and $(LCLWidgetType) set to 'wince'. Then doubbleclick to open Lazarus and just say complile. If you have compiled a 'i386-win32' version before then all the generated .o, .ppu, etc. files will be created in 'lib/i386-win32' and not in 'lib/arm-wince' as expected. In the new Lazarus you can use build modes, which is what you should use now. They can be set in the "Project Options" dialog. For this particular issue if you really want to use this variable expansion, maybe try asking in the subforum "Using the Lazarus IDE" ---------------------------------------------------------------------- marcov · 2011-04-04 09:56 Note that the above bugreport that I mentioned has been updated, and might provide a clue. Apparantly newer winmobile need some messages handled.