Re: [Lazarus] Lazarus Release Candidate 1 of 1.4. Message cannot be stopped
On 04/03/15 19:30, Martin Frb wrote: On 04/03/2015 16:56, Jürgen Hestermann wrote: I use Lazarus V1.4RC1 on Win7 and today I had a strange situation: I started to build and run an application with F9. But my machine was quite slow so nothing (visible) happened for many seconds. It could be that I then hit F9 again. After a while I got an error message saying: Stop current debugging and rebuild project? But this message could not be stopped. Clicking on Yes or No had no effect. The message stayed (or reappeared quickly). I had to exit from Lazarus and restart it to be able to continue. Maybe someone can fix this easily. Tricky, we will need to try and reproduce it. If you can reproduce, try getting a logfile http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session In any case if it happens, you should be able to solve it by choosing reset debugger from run menu. It used to happen very frequently before Martin (IIRC) fixed some closely related issue. It happens now once in a blue moon. Difficult to reproduce :( Stephano -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4. Message cannot be stopped
On 04/03/2015 16:56, Jürgen Hestermann wrote: I use Lazarus V1.4RC1 on Win7 and today I had a strange situation: I started to build and run an application with F9. But my machine was quite slow so nothing (visible) happened for many seconds. It could be that I then hit F9 again. After a while I got an error message saying: Stop current debugging and rebuild project? But this message could not be stopped. Clicking on Yes or No had no effect. The message stayed (or reappeared quickly). I had to exit from Lazarus and restart it to be able to continue. Maybe someone can fix this easily. Tricky, we will need to try and reproduce it. If you can reproduce, try getting a logfile http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session In any case if it happens, you should be able to solve it by choosing reset debugger from run menu. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4. Message cannot be stopped
I use Lazarus V1.4RC1 on Win7 and today I had a strange situation: I started to build and run an application with F9. But my machine was quite slow so nothing (visible) happened for many seconds. It could be that I then hit F9 again. After a while I got an error message saying: Stop current debugging and rebuild project? But this message could not be stopped. Clicking on Yes or No had no effect. The message stayed (or reappeared quickly). I had to exit from Lazarus and restart it to be able to continue. Maybe someone can fix this easily. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Wed, 25 Feb 2015 15:27:58 +0100 Schindler Karl-Michael karl-michael.schind...@web.de wrote: Hi, I checked RC1 of 1.4 on Mac OS X and there is one thing, which i found. The patch of revision 47654, which fixes a 32/64bit issue in lcl/lclintf.pas and lcl/include/sysenvapis_mac.inc for all Mac OS X variants, has not been included. I tried it and it appears to be fine. Can someone please merge this revision into 1.4? Done. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 20/02/2015 19:18, Mattias Gaertner ha scritto: On Fri, 20 Feb 2015 18:29:15 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 20/02/2015 17:30, Mattias Gaertner ha scritto: On Fri, 20 Feb 2015 17:04:22 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 20/02/2015 01:32, Mattias Gaertner ha scritto: [...] Do you mean line 3237? That was fixes_1_4. I rather mean line 3206. I guess this line is in 1.4RC1. Please refer to fixes_1_4. No it was in trunk. trunk: 3205: if APackage.AutoUpdate=pupManually then 3206:exit(mrNo); ? Sorry I was too hasty. The piece of code was: // check the current output directory Result:=CheckIfCurPkgOutDirNeedsCompile(APackage, true,SkipDesignTimePackages,GroupCompile, NeedBuildAllFlag,ConfigChanged,DependenciesChanged,Note); if Result=mrNo then begin // the current output is valid exit; end; Which appeared to me to check only the default directory. But I had not seen that the current output directory is properly set (either default or fallback) in GetOutputDirType. So forget about my observations. Giuliano -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, Feb 19, 2015 at 6:55 PM, m...@rpzdesign.com m...@rpzdesign.com wrote: Do these XML files also have the keystroke assignments? Where are the XML files located. Yes, key mappings are in editoroptions.xml, section KeyMapping. On *nix systems the default location for config files is ~/.lazarus. It can be overridden by --pcp=xxx parameter when strarting Lazarus. On Windows I can never remember the path by hart but you can see it in View - IDE internals - About IDE - Primary config directory. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 18:40:22 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 19/02/2015 14:10, Mattias Gaertner ha scritto: The Clean All is calling make clean. That only works in the Lazarus source directory. There is a clean up for the project and its packages, but not yet for the IDE and its packages. Missing feature. Is there a reason why a procedure CleanLazarusDestDir similar to CleanLazarusSrcDir could not be used to perform the cleanup when isRedirected is true? All that is required, in a user path, is to clean up compiler generated files, without all the other stuff which cleanide or cleanlaz do. Trunk now cleans up the fallback directories, when the user selects the clean option. Please test. If it works it can be merged to fixes_1_4. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 20/02/2015 01:32, Mattias Gaertner ha scritto: On Fri, 20 Feb 2015 00:23:57 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: [...] After some further analysis, I'm becoming convinced that clean all would be unnecessary, There are always cases when a clean all is needed. For example when an unit is moved to another package. The compiler options are exactly the same, but you have to delete the old ppu files. Let's say, would be less necessary. it clean auto didn't have a flaw in how package compilation is handled in TLazPackageGraph. In a situation where lazarus tree is not writeable, and a different user path must be used, what happens currently is: 1. TLazPackageGraph.CheckIfCurPkgOutDirNeedsCompile checks from lazarus tree if the compilation is required. 2. If yes, it verifies if normal output dir is writeable. The check fails, and it uses the FallBackOutputDir with SetDirectoryOverride. Compilation output goes in the user path, and overwrites possible old ppu's and resources. That's OK. 3. If no compilation is required, compilation is skipped, and anything leftover in the user path remains untouched. That's the flaw. What exactly is flawed? 4. When linking user path takes precedence over lazarus tree path (newly compiled must take precedence over old ones), and invalid leftovers abort the linking. The issue can be solved by brute force, always forcing the compile when normal output dir is not writeable, or with more elegance, by checking also the fall back output dir before deciding if a new compilation is required. Do you mean line 3237? I rather mean line 3206. If normal output directory (i.e. the not writeable one, in our case) doesn't need compile, no check is made on the fall back directory. If the fall back directory is empty (as it would be on a first time build) , a useless compilation is avoided, and this is Ok, but if it contains old ppu's (as it may happen after an update) the old ppu's are left in place, and will cause linking to abort. I'll make some tests on the transition from 1.2.6 to 1.4RC1 which shows the problem, to see if some smarter checks on PackageSytem can help, or if, after all, a clean all is the only viable solution. Are there cases where a package units directory contains units from more than one package? Giuliano -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Fri, 20 Feb 2015 18:29:15 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 20/02/2015 17:30, Mattias Gaertner ha scritto: On Fri, 20 Feb 2015 17:04:22 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 20/02/2015 01:32, Mattias Gaertner ha scritto: [...] Do you mean line 3237? That was fixes_1_4. I rather mean line 3206. I guess this line is in 1.4RC1. Please refer to fixes_1_4. No it was in trunk. trunk: 3205: if APackage.AutoUpdate=pupManually then 3206:exit(mrNo); ? Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 09:01:29 +0200 FreeMan freema...@delphiturkiye.com wrote: If see in osx qt, you can hard attack. set second shortcut via key grab, then key grab not find that shortcut :) Please create a bug report. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 02:33:31 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 19/02/2015 02:13, Mattias Gaertner ha scritto: On Thu, 19 Feb 2015 01:25:19 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 16/02/2015 23:38, Mattias Gaertner ha scritto: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. [...] I installed RC1.4 and I stumbled into a problem. Some missing buttons in the Configure Build Lazarus dialogue. I did something wrong, or there's been a regression? Here's a screenshot the dialogue of RC1.4 from svn from my last update (rev 47621): http://www.bononiadocta.it/Lazarus/rev47621.png Do you mean branches/fixes_1_4 or trunk? It's branches/fixes_1_4 of a few days ago. Also trunk as of yesterday is ok. I didn't test against latest branches/fixes. Please do. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 10:47:18 +0100 Andrea Mauri andrea.mauri...@gmail.com wrote: Dear all, I am testing Lazarus 1.4RC2 r FPC 2.6.4 i386-win32-win32/win64 [...] procedure TForm1.TreeView1Click(Sender: TObject); var i: integer; begin i:= TreeView1.Selected.Level; end; When I click on the checkbox of any treeview node I got a sigsegv error here: function TTreeNode.GetLevel: Integer; // root is on level 0 var ANode: TTreeNode; begin Result := 0; ANode := Parent; while Assigned(ANode) do begin Inc(Result); ANode := ANode.Parent; end; end; It probably means TreeView1.Selected is nil. If you think it should not be nil, then please create a bug report with a complete example. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
It is really a minor thing but actually when I copy the lazarus version info using the Information on lazarus window (Help menu) I got Lazarus 1.4RC2 r FPC 2.6.4 i386-win32-win32/win64 No svn information is available. I am using the svn 1.4 fixes. Andrea -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Created #27497 , #27498 , #27500 On 19.02.2015 10:09, Mattias Gaertner wrote: On Thu, 19 Feb 2015 09:01:29 +0200 FreeMan freema...@delphiturkiye.com wrote: If see in osx qt, you can hard attack. set second shortcut via key grab, then key grab not find that shortcut :) Please create a bug report. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, Feb 19, 2015 at 2:25 AM, Giuliano Colla giuliano.co...@fastwebnet.it wrote: I installed RC1.4 and I stumbled into a problem. Some missing buttons in the Configure Build Lazarus dialogue. I did something wrong, or there's been a regression? No, it is a well thought of feature, not a regression. It depends on your directory access rights only. You are on Linux and run Lazarus as normal user. If you were allowed to select Clean All, you would get error from OS. The assumption is that once you install Lazarus under /usr/... it will not change and you don't need Clean All. When installing packages and rebuilding Lazarus the changes will happen in your home directory and startlazarus starts the new executable from there. We used to get reports that people had to run Lazarus as root. The change was made to prevent such reports. There used to be real bugs in the building process but they are fixed. (?) If you find a _real_ situation where this does not work then please report. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Dear all, I am testing Lazarus 1.4RC2 r FPC 2.6.4 i386-win32-win32/win64 I got a problem with Ttreeview. I have a project in which I use a TTreeView with checkboxes. It worked with laz 1.2 fixes branch. I tested a simple project with 1 form, 1 imagelist and 1 ttreeview filled with few items whose state index is set to 0. The stateimages property is set to imagelist1 that is filled on form creation with the following routine found on lazarus forum: procedure TForm1.FormCreate(Sender: TObject); var aSize: TSize; aBMP: TBitmap; aDetails: TThemedElementDetails; aRect: TRect; begin aDetails:=ThemeServices.GetElementDetails(tbCheckBoxUncheckedNormal); aSize:=ThemeServices.GetDetailSize(aDetails); ImageList1.Width:=aSize.cx; ImageList1.Height:=aSize.cy; aBMP:=TBitmap.Create; with aBMP do begin SetSize(aSize.cx, aSize.cy); Transparent:=True; TransparentColor:=clForm; Brush.Color:=TransparentColor; Canvas.FillRect(0,0, Width,Height); end; aRect:=Rect(0, 0, aSize.cx, aSize.cy); ThemeServices.DrawElement(aBMP.Canvas.Handle, aDetails, aRect, nil); ImageList1.Add(aBMP, nil); aBMP.Canvas.FillRect(0,0, Width,Height);; aDetails:=ThemeServices.GetElementDetails(tbCheckBoxCheckedNormal); ThemeServices.DrawElement(aBMP.Canvas.Handle, aDetails, aRect, nil); ImageList1.Add(aBMP, nil); FreeAndNil(aBMP); end; Starting the project I got a ttreeview with unchecked boxes. Here the code for click on tree: procedure TForm1.TreeView1Click(Sender: TObject); var i: integer; begin i:= TreeView1.Selected.Level; end; When I click on the checkbox of any treeview node I got a sigsegv error here: function TTreeNode.GetLevel: Integer; // root is on level 0 var ANode: TTreeNode; begin Result := 0; ANode := Parent; while Assigned(ANode) do begin Inc(Result); ANode := ANode.Parent; end; end; Thanks, Andrea Il 16/02/2015 23:38, Mattias Gaertner ha scritto: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. Please read below why everybody really should join the testing now. News in this Version http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes On Windows the installer now allows 2 independent installations. http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus About the release process: http://wiki.lazarus.freepascal.org/Lazarus_1.4_fixes_branch#Roadmap_to_1.4 The 1.4RC1 is built with fpc 2.6.4. The release candidate is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the Lazarus 1.4RC1 directory. Minimum requirements: Windows: 98, 2k, XP, Vista, 7, 32 or 64bit. On 64bit it is recommended to use the 32bit IDE. Win98 IDE needs building with flag -dWIN9XPLATFORM. FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit. Mac OS X: 10.5 to 10.10, 10.9+ without IDE debugger (gdb works), LCL only 32bit, non LCL apps can be 64bit. == Why should everybody (including you) test the release candidate? == In the past weeks the Lazarus team has stabilized the 1.4 fixes branch. The resulting 1.4RC1 is now stable enough to be used by any one for test purposes. However many of the fixes and new features that where committed since the release of 1.2 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million. Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it. Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.4.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features. == How to test == Download and install the 1.4RC1. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path In either case you should make backups. (including your primary config) Open your project in the current Lazarus (1.2.6), and use Publish Project from the project menu. This creates a clean copy of your project. You can then open that copy in the RC1. Please test: - If you can edit forms in the designer - rename components / change properties in Object inspector / Add new events - Add components to form / Move components on form - Frames, if you use them - If you can navigate the source code (e.g. jump to
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 19/02/2015 11:01, Mattias Gaertner ha scritto: It probably means TreeView1.Selected is nil. If you think it should not be nil, then please create a bug report with a complete example. Both FRClickNode and FSelectedNode are nil. Now I got the sigsegv error but it worked on laz 1.2 so yes, I think it is a bug. I already reported in the bugtracker. Andrea -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, Feb 19, 2015 at 1:10 PM, Giuliano Colla giuliano.co...@fastwebnet.it wrote: Whatever it was, it's got fixed in the meantime. You installed it as root to a place where your normal user has no write access. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 13:44:03 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 19/02/2015 12:32, Juha Manninen ha scritto: On Thu, Feb 19, 2015 at 1:10 PM, Giuliano Colla giuliano.co...@fastwebnet.it wrote: Whatever it was, it's got fixed in the meantime. You installed it as root to a place where your normal user has no write access. Then there's a bug, because the full scenario is: The lazarus tree installed from rpm is in /usr/lib (or /usr/lib64) where normal user has no write access. A custom executable is on ~/.lazarus_1.4 (--pcp= etc) where normal user has write access. A Build Lazarus should therefore build a new custom executable in ~/.lazarus_1.4 where the normal user has write access, and actually it does. Given this scenario, the only place where a clean all needs to work is on the writeable local tree: if sources are located on a non writeable path is not relevant. Without a clean all, a number of stale ppu's where left in place in my writeable path. I could build only by removing by hand ppu's in my writeable path. The appropriate check should be if the *target* path is writeable. If it's not, then it's impossible to build. If it is, then it's possible to clean it in any way: automatically, clean common, clean all. The Clean All is calling make clean. That only works in the Lazarus source directory. There is a clean up for the project and its packages, but not yet for the IDE and its packages. Missing feature. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Mr Freeman: I appreciate your attempt at a response, but your communication is completely incoherent. I am talking about saving assigned key stroke shortcuts to an external file and being able to import them from an external file. Hell, I could use the entire settings for the compiler as well set to an external file for re-import later or on another computer. If you have something you want to say, please add clarify nouns and verbs. md On 2/19/2015 1:01 AM, FreeMan wrote: If see in osx qt, you can hard attack. set second shortcut via key grab, then key grab not find that shortcut :) On 19.02.2015 03:29, m...@rpzdesign.com wrote: Can you export the assigned key stroke shortcuts to an external file? And then import them later? The current shortcut key assignment interface of lazarus is a disaster. md -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thursday, February 19, 2015, m...@rpzdesign.com m...@rpzdesign.com wrote: Hell, I could use the entire settings for the compiler as well set to an external file for re-import later or on another computer. In fact all settings in Lazarus are stored in external XML files. You can copy them to another computer. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Do these XML files also have the keystroke assignments? Where are the XML files located. THanks. On 2/19/2015 9:12 AM, Juha Manninen wrote: On Thursday, February 19, 2015, m...@rpzdesign.com mailto:m...@rpzdesign.com m...@rpzdesign.com mailto:m...@rpzdesign.com wrote: Hell, I could use the entire settings for the compiler as well set to an external file for re-import later or on another computer. In fact all settings in Lazarus are stored in external XML files. You can copy them to another computer. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 19/02/2015 14:10, Mattias Gaertner ha scritto: The Clean All is calling make clean. That only works in the Lazarus source directory. There is a clean up for the project and its packages, but not yet for the IDE and its packages. Missing feature. Is there a reason why a procedure CleanLazarusDestDir similar to CleanLazarusSrcDir could not be used to perform the cleanup when isRedirected is true? All that is required, in a user path, is to clean up compiler generated files, without all the other stuff which cleanide or cleanlaz do. Giuliano -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 19/02/2015 14:10, Mattias Gaertner ha scritto: On Thu, 19 Feb 2015 13:44:03 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 19/02/2015 12:32, Juha Manninen ha scritto: On Thu, Feb 19, 2015 at 1:10 PM, Giuliano Colla giuliano.co...@fastwebnet.it wrote: Whatever it was, it's got fixed in the meantime. You installed it as root to a place where your normal user has no write access. Then there's a bug, because the full scenario is: The lazarus tree installed from rpm is in /usr/lib (or /usr/lib64) where normal user has no write access. A custom executable is on ~/.lazarus_1.4 (--pcp= etc) where normal user has write access. A Build Lazarus should therefore build a new custom executable in ~/.lazarus_1.4 where the normal user has write access, and actually it does. Given this scenario, the only place where a clean all needs to work is on the writeable local tree: if sources are located on a non writeable path is not relevant. Without a clean all, a number of stale ppu's where left in place in my writeable path. I could build only by removing by hand ppu's in my writeable path. The appropriate check should be if the *target* path is writeable. If it's not, then it's impossible to build. If it is, then it's possible to clean it in any way: automatically, clean common, clean all. The Clean All is calling make clean. That only works in the Lazarus source directory. There is a clean up for the project and its packages, but not yet for the IDE and its packages. Missing feature. After some further analysis, I'm becoming convinced that clean all would be unnecessary, it clean auto didn't have a flaw in how package compilation is handled in TLazPackageGraph. In a situation where lazarus tree is not writeable, and a different user path must be used, what happens currently is: 1. TLazPackageGraph.CheckIfCurPkgOutDirNeedsCompile checks from lazarus tree if the compilation is required. 2. If yes, it verifies if normal output dir is writeable. The check fails, and it uses the FallBackOutputDir with SetDirectoryOverride. Compilation output goes in the user path, and overwrites possible old ppu's and resources. That's OK. 3. If no compilation is required, compilation is skipped, and anything leftover in the user path remains untouched. That's the flaw. 4. When linking user path takes precedence over lazarus tree path (newly compiled must take precedence over old ones), and invalid leftovers abort the linking. The issue can be solved by brute force, always forcing the compile when normal output dir is not writeable, or with more elegance, by checking also the fall back output dir before deciding if a new compilation is required. The second solution would avoid unnecessary recompilations, e.g. when the custom version uses a different WS. In the current situation almost all packages appear to require compilation at every build, because compiler options in the lazarus tree are different from current options, while most of them actually do not. If nobody detects a basic flaw in my considerations, I'd add an entry in the bugtracker, with target 1.6. Now it's a bit late to start playing with TLazPackageGraph for 1.4, I believe. Giuliano -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 20/02/2015 00:23, Giuliano Colla ha scritto: Il 19/02/2015 14:10, Mattias Gaertner ha scritto: On Thu, 19 Feb 2015 13:44:03 +0100 Giuliano Collagiuliano.co...@fastwebnet.it wrote: Il 19/02/2015 12:32, Juha Manninen ha scritto: On Thu, Feb 19, 2015 at 1:10 PM, Giuliano Colla giuliano.co...@fastwebnet.it wrote: Whatever it was, it's got fixed in the meantime. You installed it as root to a place where your normal user has no write access. Then there's a bug, because the full scenario is: The lazarus tree installed from rpm is in /usr/lib (or /usr/lib64) where normal user has no write access. A custom executable is on ~/.lazarus_1.4 (--pcp= etc) where normal user has write access. A Build Lazarus should therefore build a new custom executable in ~/.lazarus_1.4 where the normal user has write access, and actually it does. Given this scenario, the only place where a clean all needs to work is on the writeable local tree: if sources are located on a non writeable path is not relevant. Without a clean all, a number of stale ppu's where left in place in my writeable path. I could build only by removing by hand ppu's in my writeable path. The appropriate check should be if the *target* path is writeable. If it's not, then it's impossible to build. If it is, then it's possible to clean it in any way: automatically, clean common, clean all. The Clean All is calling make clean. That only works in the Lazarus source directory. There is a clean up for the project and its packages, but not yet for the IDE and its packages. Missing feature. After some further analysis, I'm becoming convinced that clean all would be unnecessary, it clean auto didn't have a flaw in how package compilation is handled in TLazPackageGraph. please read if clean auto didn't have a flaw!! In a situation where lazarus tree is not writeable, and a different user path must be used, what happens currently is: 1. TLazPackageGraph.CheckIfCurPkgOutDirNeedsCompile checks from lazarus tree if the compilation is required. 2. If yes, it verifies if normal output dir is writeable. The check fails, and it uses the FallBackOutputDir with SetDirectoryOverride. Compilation output goes in the user path, and overwrites possible old ppu's and resources. That's OK. 3. If no compilation is required, compilation is skipped, and anything leftover in the user path remains untouched. That's the flaw. 4. When linking user path takes precedence over lazarus tree path (newly compiled must take precedence over old ones), and invalid leftovers abort the linking. The issue can be solved by brute force, always forcing the compile when normal output dir is not writeable, or with more elegance, by checking also the fall back output dir before deciding if a new compilation is required. The second solution would avoid unnecessary recompilations, e.g. when the custom version uses a different WS. In the current situation almost all packages appear to require compilation at every build, because compiler options in the lazarus tree are different from current options, while most of them actually do not. If nobody detects a basic flaw in my considerations, I'd add an entry in the bugtracker, with target 1.6. Now it's a bit late to start playing with TLazPackageGraph for 1.4, I believe. Giuliano -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Fri, 20 Feb 2015 00:23:57 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: [...] After some further analysis, I'm becoming convinced that clean all would be unnecessary, There are always cases when a clean all is needed. For example when an unit is moved to another package. The compiler options are exactly the same, but you have to delete the old ppu files. it clean auto didn't have a flaw in how package compilation is handled in TLazPackageGraph. In a situation where lazarus tree is not writeable, and a different user path must be used, what happens currently is: 1. TLazPackageGraph.CheckIfCurPkgOutDirNeedsCompile checks from lazarus tree if the compilation is required. 2. If yes, it verifies if normal output dir is writeable. The check fails, and it uses the FallBackOutputDir with SetDirectoryOverride. Compilation output goes in the user path, and overwrites possible old ppu's and resources. That's OK. 3. If no compilation is required, compilation is skipped, and anything leftover in the user path remains untouched. That's the flaw. What exactly is flawed? 4. When linking user path takes precedence over lazarus tree path (newly compiled must take precedence over old ones), and invalid leftovers abort the linking. The issue can be solved by brute force, always forcing the compile when normal output dir is not writeable, or with more elegance, by checking also the fall back output dir before deciding if a new compilation is required. Do you mean line 3237? The second solution would avoid unnecessary recompilations, e.g. when the custom version uses a different WS. Most packages have $(LCLWidgetType) in their output directory. In the current situation almost all packages appear to require compilation at every build, because compiler options in the lazarus tree are different from current options, while most of them actually do not. 1.4RC1 on Linux had a bug about comparing the -Cg option in Makefile.compiled. That had been fixed. Hopefully in 1.6 we have replaced Makefiles with fpmake. Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
If see in osx qt, you can hard attack. set second shortcut via key grab, then key grab not find that shortcut :) On 19.02.2015 03:29, m...@rpzdesign.com wrote: Can you export the assigned key stroke shortcuts to an external file? And then import them later? The current shortcut key assignment interface of lazarus is a disaster. md -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On 02/19/2015 01:25 AM, Giuliano Colla wrote: Il 16/02/2015 23:38, Mattias Gaertner ha scritto: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. [...] I installed RC1.4 and I stumbled into a problem. Some missing buttons in the Configure Build Lazarus dialogue. I did something wrong, or there's been a regression? Here's a screenshot the dialogue of RC1.4 from svn from my last update (rev 47621): http://www.bononiadocta.it/Lazarus/rev47621.png And here's a screenshot of the same dialogue from the RC1.4 downloaded from sourceforge (rev 47789) http://www.bononiadocta.it/Lazarus/rev47789.png It looks like that here when cpu is different than default (eg. x86_64 on 32 bit system). But as I can see your cpu is default - so bug. z. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
En Tue, 17 Feb 2015 05:00:50 -0600, Luca Olivetti l...@wetron.es escribió: Oh, and I have a one line patch to dbgrids.pas, but Jesus didn't acknowledge it yet: http://bugs.freepascal.org/view.php?id=27232 Bye I'm sorry, I will take a look shortly. Jesus Reyes A. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Il 19/02/2015 02:13, Mattias Gaertner ha scritto: On Thu, 19 Feb 2015 01:25:19 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 16/02/2015 23:38, Mattias Gaertner ha scritto: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. [...] I installed RC1.4 and I stumbled into a problem. Some missing buttons in the Configure Build Lazarus dialogue. I did something wrong, or there's been a regression? Here's a screenshot the dialogue of RC1.4 from svn from my last update (rev 47621): http://www.bononiadocta.it/Lazarus/rev47621.png Do you mean branches/fixes_1_4 or trunk? It's branches/fixes_1_4 of a few days ago. Also trunk as of yesterday is ok. I didn't test against latest branches/fixes. Giuliano -- Giuliano Colla Project planning question: when it's 90% done, are we halfway or not yet? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Thu, 19 Feb 2015 01:25:19 +0100 Giuliano Colla giuliano.co...@fastwebnet.it wrote: Il 16/02/2015 23:38, Mattias Gaertner ha scritto: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. [...] I installed RC1.4 and I stumbled into a problem. Some missing buttons in the Configure Build Lazarus dialogue. I did something wrong, or there's been a regression? Here's a screenshot the dialogue of RC1.4 from svn from my last update (rev 47621): http://www.bononiadocta.it/Lazarus/rev47621.png Do you mean branches/fixes_1_4 or trunk? And here's a screenshot of the same dialogue from the RC1.4 downloaded from sourceforge (rev 47789) http://www.bononiadocta.it/Lazarus/rev47789.png Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Thanks. Оригинално писмо От: Juha Manninen Относно: Re: [Lazarus] Lazarus Release Candidate 1 of 1.4 До: Lazarus mailing list Изпратено на: Вторник, 2015, Февруари 17 16:06:02 EET On Tue, Feb 17, 2015 at 4:03 PM, Kamen Ketev kamenl...@abv.bg wrote: When I load project says: Component Class: TDateEdit Error reading deData.DialogTitle: Unknown property: Dialog Title... Why you remove this property? How can fix the problem? http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes#TDateEdit.DialogTitle_property_was_removed -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Tue, Feb 17, 2015 at 4:03 PM, Kamen Ketev kamenl...@abv.bg wrote: When I load project says: Component Class: TDateEdit Error reading deData.DialogTitle: Unknown property: Dialog Title... Why you remove this property? How can fix the problem? http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes#TDateEdit.DialogTitle_property_was_removed -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Tue, 17 Feb 2015 12:12:55 +0100 Luca Olivetti l...@wetron.es wrote: [...] ERROR: Broken dependency: camviewpkg 0.0camviewpkg 0.0 make: *** [useride] Error 3 It means it can't find camviewpkg.lpk. Maybe the error message can be improved for lazbuild. [...] Sorry, that was a PEBKAC (just yesterday I removed one of the packages to use the upstream one instead of what I cooked myself). Now the make bigide is stuck (i.e. it doesn't proceed) C:\lazextra\rx\tooledit.pas(109,15) Error: (3058) There is no method in an ances tor class to be overridden: TCustomRxDateEdit.Change; Have you seen this: http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes#TEditButton_was_rewritten ? C:\lazextra\rx\tooledit.pas(112,15) Error: (3058) There is no method in an ances tor class to be overridden: TCustomRxDateEdit.DoButtonClick(TObject); C:\lazextra\rx\tooledit.pas(219,1) Fatal: (10026) There were 2 errors compiling module, stopping Fatal: (1018) Compilation aborted Error: C:\FPC\2.6.4\bin\i386-Win32\ppc386.exe returned an error exitcode (normal if you did not specify a source file to be compiled) Compiling package rxnew 2.4.2.120: stopped with exit code 1 (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetWordList.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetAlign.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetReplace.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetUses.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetPreProcessor.pas TLazPackageGraph.CompileRequiredPackages ERROR=Exit code 1 ERROR: BuildLazarusIDE: Compile AutoInstall Packages failed. I had to interrupt it with CTRL+C It didn't stop automatically? Can you reproduce it? Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
El 17/02/15 a les 12:25, Mattias Gaertner ha escrit: C:\lazextra\rx\tooledit.pas(109,15) Error: (3058) There is no method in an ances tor class to be overridden: TCustomRxDateEdit.Change; Have you seen this: http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes#TEditButton_was_rewritten ? No, but I just got the svn version of rxnew, and the author read it ;-) TLazPackageGraph.CompileRequiredPackages ERROR=Exit code 1 ERROR: BuildLazarusIDE: Compile AutoInstall Packages failed. I had to interrupt it with CTRL+C It didn't stop automatically? Can you reproduce it? I did it twice, I waited for a couple of minutes with no disk activity then hit CTRL+C. I suppose that if I reinstall the broken version of rx I can trigger it again...let me trymmh, it seems I cannot find a way to install the broken package, make useride just uses the good version now. Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es Tel. +34 935883004 Fax +34 935883007 -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On 17/02/2015 07:32, Dejan Boras wrote: Compiled a few of my projects, works on Fedora 21 x64. But trying to rebuild the IDE gives: File /usr/lib64/lazarus/ide/cmdlinedebugger.pp not found. It never was in this location. But yes it has moved. So if you have an old lazbuild, or previous IDE it will not build (a package must be added by hand). I only tested 1.4RC on windows, and had no issues recompiling. Which method do you use to build? IDE, Lazbuild, ...? And does (temporarily) cleaning the old config dir help? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
El 17/02/15 a les 12:00, Luca Olivetti ha escrit: El 16/02/15 a les 23:38, Mattias Gaertner ha escrit: == How to test == Download and install the 1.4RC1. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path I used the svn copy and made a different test (note that I modified the useride target in the makefile to add the pcp): C:\laz_1_4make useride ./lazbuild.exe --pcp=config --lazarusdir=. --build-ide= SetPrimaryConfigPath NewValue=config - C:\laz_1_4\config primary config path: C:\laz_1_4\config\ NOTE: Building Lazarus IDE with profile Build IDE with Packages TBuildManager.SetBuildTargetIDE OS=win32 CPU=i386 WS=win32 ERROR: Broken dependency: camviewpkg 0.0camviewpkg 0.0 make: *** [useride] Error 3 I'll build a standard ide to see what happens, but the above procedure worked until now. Sorry, that was a PEBKAC (just yesterday I removed one of the packages to use the upstream one instead of what I cooked myself). Now the make bigide is stuck (i.e. it doesn't proceed) C:\lazextra\rx\tooledit.pas(109,15) Error: (3058) There is no method in an ances tor class to be overridden: TCustomRxDateEdit.Change; C:\lazextra\rx\tooledit.pas(112,15) Error: (3058) There is no method in an ances tor class to be overridden: TCustomRxDateEdit.DoButtonClick(TObject); C:\lazextra\rx\tooledit.pas(219,1) Fatal: (10026) There were 2 errors compiling module, stopping Fatal: (1018) Compilation aborted Error: C:\FPC\2.6.4\bin\i386-Win32\ppc386.exe returned an error exitcode (normal if you did not specify a source file to be compiled) Compiling package rxnew 2.4.2.120: stopped with exit code 1 (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetWordList.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetAlign.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetReplace.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetUses.pas (3104) Compiling C:\laz_1_4\components\jcf2\Settings\SetPreProcessor.pas TLazPackageGraph.CompileRequiredPackages ERROR=Exit code 1 ERROR: BuildLazarusIDE: Compile AutoInstall Packages failed. I had to interrupt it with CTRL+C Oh, and I have a one line patch to dbgrids.pas, but Jesus didn't acknowledge it yet: http://bugs.freepascal.org/view.php?id=27232 Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es Tel. +34 935883004 Fax +34 935883007 -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Rebuilding works after cleaning out the compiled units/ lib/ and bin/ out of the profile directory. On Tue, Feb 17, 2015 at 12:37 PM, Martin Frb laza...@mfriebe.de wrote: On 17/02/2015 07:32, Dejan Boras wrote: Compiled a few of my projects, works on Fedora 21 x64. But trying to rebuild the IDE gives: File /usr/lib64/lazarus/ide/cmdlinedebugger.pp not found. It never was in this location. But yes it has moved. So if you have an old lazbuild, or previous IDE it will not build (a package must be added by hand). I only tested 1.4RC on windows, and had no issues recompiling. Which method do you use to build? IDE, Lazbuild, ...? And does (temporarily) cleaning the old config dir help? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Hi, Totally interested in helping test RC1...but...I'm scared. I have Lazarus 1.2.6 installed now and I would like to install RC1 to a separate directory structure. I've downloaded the 3 fpc/laz RC1 DEB files and am ready to go except: I'm working in Kubuntu 14.04. I'm new-ish with Linux, and with DEB packages before this I've simply right clicked and allowed the system to install them. I assume this will overwrite my existing Laz install. So how do I use the deb file such that I consistently get the packages into a new directory structure that will work separately from 1.2.6? using a dpkg switch? If I get to this desired structure, I assume I will need to do the makes manually, yes? (first time...shiver). Also you said if you install to a new location you need to use: --primary-config-path I've done some searching and can find no reference to this switch, I don't even know which program (lazarus? FPC? DPKG?) would expect this switch. Any help, links or whatever, would be appreciated. Once I've convinced myself that I can get the RC onto my system and it will play nicely, I will install and test. Thanks in advance, Julius On 02/16/2015 11:38 PM, Mattias Gaertner wrote: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. Please read below why everybody really should join the testing now. News in this Version http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes On Windows the installer now allows 2 independent installations. http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus About the release process: http://wiki.lazarus.freepascal.org/Lazarus_1.4_fixes_branch#Roadmap_to_1.4 The 1.4RC1 is built with fpc 2.6.4. The release candidate is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the Lazarus 1.4RC1 directory. Minimum requirements: Windows: 98, 2k, XP, Vista, 7, 32 or 64bit. On 64bit it is recommended to use the 32bit IDE. Win98 IDE needs building with flag -dWIN9XPLATFORM. FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit. Mac OS X: 10.5 to 10.10, 10.9+ without IDE debugger (gdb works), LCL only 32bit, non LCL apps can be 64bit. == Why should everybody (including you) test the release candidate? == In the past weeks the Lazarus team has stabilized the 1.4 fixes branch. The resulting 1.4RC1 is now stable enough to be used by any one for test purposes. However many of the fixes and new features that where committed since the release of 1.2 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million. Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it. Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.4.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features. == How to test == Download and install the 1.4RC1. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path In either case you should make backups. (including your primary config) Open your project in the current Lazarus (1.2.6), and use Publish Project from the project menu. This creates a clean copy of your project. You can then open that copy in the RC1. Please test: - If you can edit forms in the designer - rename components / change properties in Object inspector / Add new events - Add components to form / Move components on form - Frames, if you use them - If you can navigate the source code (e.g. jump to implementation) - Auto completion in source code - Compile, debug and run - Anything else you use in your daily work Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On Tue, 17 Feb 2015 13:42:42 +0100 JuuS j...@mykolab.ch wrote: [...] I have Lazarus 1.2.6 installed now and I would like to install RC1 to a separate directory structure. I've downloaded the 3 fpc/laz RC1 DEB files and am ready to go except: Lazarus 1.2.6 and 1.4 use the same compiler. If you installed 1.2.6 from our sourceforge site, then you only need to update the lazarus deb. It doesn't hurt to install the fpc debs though. deb is clever enough to figure it out. Note: In a few months FPC 3.0 will be released. The following Lazarus 1.4.x release will use that. I'm working in Kubuntu 14.04. I'm new-ish with Linux, and with DEB packages before this I've simply right clicked and allowed the system to install them. I assume this will overwrite my existing Laz install. So how do I use the deb file such that I consistently get the packages into a new directory structure that will work separately from 1.2.6? using a dpkg switch? These deb files are not made for parallel installation. As always: Before installing a new Lazarus version make a backup of your ~/.lazarus directory. Installing the 1.4 deb will replace the old 1.2.6. You can downgrade by installing the 1.2.6 deb. When starting the IDE it will give you an upgrade or downgrade message. Note that downgrade from 1.4 to 1.2.x may loose some settings. You can install a second Lazarus version in parallel. Do you want that? Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Lazarus Release Candidate 1 of 1.4
The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. We would like to invite all users to test this release candidate. Please read below why everybody really should join the testing now. News in this Version http://wiki.lazarus.freepascal.org/Lazarus_1.4.0_release_notes On Windows the installer now allows 2 independent installations. http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus About the release process: http://wiki.lazarus.freepascal.org/Lazarus_1.4_fixes_branch#Roadmap_to_1.4 The 1.4RC1 is built with fpc 2.6.4. The release candidate is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/ Choose your CPU, OS, distro and then the Lazarus 1.4RC1 directory. Minimum requirements: Windows: 98, 2k, XP, Vista, 7, 32 or 64bit. On 64bit it is recommended to use the 32bit IDE. Win98 IDE needs building with flag -dWIN9XPLATFORM. FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit. Mac OS X: 10.5 to 10.10, 10.9+ without IDE debugger (gdb works), LCL only 32bit, non LCL apps can be 64bit. == Why should everybody (including you) test the release candidate? == In the past weeks the Lazarus team has stabilized the 1.4 fixes branch. The resulting 1.4RC1 is now stable enough to be used by any one for test purposes. However many of the fixes and new features that where committed since the release of 1.2 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million. Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it. Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.4.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features. == How to test == Download and install the 1.4RC1. - On Windows you can install as a 2ndary install, that will not affect your current install: http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus - On other platforms, if you install to a new location you need to use --primary-config-path In either case you should make backups. (including your primary config) Open your project in the current Lazarus (1.2.6), and use Publish Project from the project menu. This creates a clean copy of your project. You can then open that copy in the RC1. Please test: - If you can edit forms in the designer - rename components / change properties in Object inspector / Add new events - Add components to form / Move components on form - Frames, if you use them - If you can navigate the source code (e.g. jump to implementation) - Auto completion in source code - Compile, debug and run - Anything else you use in your daily work Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
Compiled a few of my projects, works on Fedora 21 x64. But trying to rebuild the IDE gives: File /usr/lib64/lazarus/ide/cmdlinedebugger.pp not found. On Tue, Feb 17, 2015 at 12:52 AM, Howard Page-Clark h...@talktalk.net wrote: On 16/02/2015 22:38, Mattias Gaertner wrote: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. ... Huge thanks to the team who have laboured to produce this latest marvel. It installed flawlessly (on my Windows 7 machine) in about 40 seconds, and was ready to roll! I've never seen such a snappy install for a full-featured development environment before. Recompiled the last three projects I worked on (chewing its way through scores of files) without any problems. No bugs to report yet. Thanks again. Howard --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Lazarus Release Candidate 1 of 1.4
On 16/02/2015 22:38, Mattias Gaertner wrote: The Lazarus team would like to announce the first release candidate for the upcoming Version 1.4. ... Huge thanks to the team who have laboured to produce this latest marvel. It installed flawlessly (on my Windows 7 machine) in about 40 seconds, and was ready to roll! I've never seen such a snappy install for a full-featured development environment before. Recompiled the last three projects I worked on (chewing its way through scores of files) without any problems. No bugs to report yet. Thanks again. Howard --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
