Unknown Property LCLVersion lazarus / 10-Designer ---------------------------------------------------------------------- hy · 2008-03-08 16:31 Since a couple of days Lazarus inserts 'LCLVersion'#6#6'0.9.25'as last property into the*.lrs-files On runtime it crashes after loading the form with an error: unknown property LCL-Version ... how do i fix this? Itried to remove it b editing the *.lrs manually but keeps beeing reinserted which is a drag ---------------------------------------------------------------------- Bart · 2008-03-09 13:34 Hi, I run SVN 14480 (Win9x). Sure it has the new property for TForm, but the compiled program runs just fine. However if I open/compile with a previous version of Lazarus (like the stable 0.9.24) you get the errors. I personally do not like the introduction of this new property, but that's just me... If you open/compile the program in a Lazarus version that does not support this property yet, right-click in the unit that belongs to the form, choose "open .lfm", then remove the line that has the property LCLVersion  in it. Save the file. Close it. Recompile, run, should be OK. If you experience this problem in your SVN version update it to the lates one. If it persists even then, report back. Hope this helps a little. Bart ---------------------------------------------------------------------- hy · 2008-03-09 17:05 Hi Bart, thanks for your reply. the problem is I am running the current svn version. But have additionally installed a pre-release version of lazarus in the system in /usr/lib/lazarus I would like to force it using the svn units but in my project options I don't have any references to lazarus or fpc, so I don't know where to start altering search paths. Any hints? ---------------------------------------------------------------------- Bart · 2008-03-10 15:05 I'm not sure that can be done? I think in effect to use a TForm with new properties in Lazarus, you will have to recompile the LCL at least? But then you don't have a stable version anymore... I have the same problem as you. I run SVN version and stable 0.9.24 in WinMe and 0.9.24 on Linux. Switching for and back between versions can be a PITA if new properties have been defined for components you use. It would be nice if the IDE, upon loading the form, would give the opportunity to remove the properties that it cannot handle (Delphi does this AFAIK). As long as you do not use them in code, then it should be OK. I could not find such a feature in the IDE. We could ask for it though (but I think it will not get a high priority). Bart ---------------------------------------------------------------------- hy · 2008-03-10 19:15 thanks I actually stopped working on my s7uff forthe moment. because I additionaly try to keep it (write once compile everywhere) on a Win- Machine at my working place. due to some restrictions in our company net i can not tun svn versions (and can't download a complete daily snapshot) of lazarus 4 Win. Anyway i am going on holidays on Sunday and hope the matter will be easier to solve in April when I am back. thanks for your help. ---------------------------------------------------------------------- sw2090 · 2008-03-12 12:04 I experienced the same using a selfcompiled svn with carbon on osx tiger while a stable version of laz was installed previously to the compiling of the svn. Projects created with the svn compile but do not run with that lcl-version: unknon property error. In fact I found that the svn lazarus from somewhere grabbed a lazarus path which was the path to the "older" stable version of lazarus and put it into its environnment settings. Due to that it compiled or/and linked the projects with that lcl version there which doesn't have this property. After I changed the lazarus path in lazarus' environment settings dialog to the path where the svn lazarus is it compiled my project and made me an app package that runs fine Thus I still got linker issus with the current svn on osx 10.5 "leopard" But maybe this helps solving your issue hy cheers Sebastian ---------------------------------------------------------------------- hy · 2008-03-14 18:37 Thanks, I found out that (on Linux) it seems to be sufficient to create a fpc.cfg in the svn repository with the respective paths or to change the path in  the /etc/fpc.cfg.