svn checkout http://svn.freepascal.org/svn/lazarus/tags/lazarus_2_0_0_RC2
cd lazarus_2_0_0_RC2
make CPU_TARGET=i386
open startlazarus.app --args "--pcp=~/.lazarus_2_0_0_RC2"
Tests on MAC OSLooking into it...
How to test the RC2 version when "lazarus-2.0.0RC2-i686-macosx.dmg" does not exist in the Sourceforge ?
We have to build it from source files ? Is there a procedure to do this ?
I tried to compile my projects and everything looks good beside the message unit lazutf8sysutils not found.Yes, good point. I had renamed the unit because it had nothing to do with UTF8. Actually I thought it was not used outside Lazarus sources.
I need the function NowUTC which is now located in unit LazSysUtils.
Ok, search and replace fixed the error.
I'm just wondering that I couldn't get any information about that unit movement.
Or have I missed something?
BTW, I recommend the HEAD of fixes branch for everybody who builds from sources:
https://svn.freepascal.org/svn/lazarus/branches/fixes_2_0/
It is always better than a tagged version because it contains the latest bug fixes merged. This is true also after versions 2.0, 2.0.2 etc. are released.
Yes, good point. I had renamed the unit because it had nothing to do with UTF8. Actually I thought it was not used outside Lazarus sources.
Now in r59436 I added lazutf8sysutils back there with "deprecated" warnings. It will be in 2.0 final and in RC3 if that is built.
Now waiting to be merged to fixes branch. See:
http://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch
1) RC2 is not available for macOS as a download from http://sourceforge.net/projects/lazarus/files
but I notice that the 64-bit Windows installer is still shipping with the ancient, buggy GDB 7.3?
Can you report any way, that you know how to crash the old gdb?
I have an automatic testcase, that runs a lot of commands against that gdb. I run this under win10 1709 64bit, with no crash or hang.
Using Dwarf3 causes gdb to crash, but that is true for all gdb versions including 8.2.
Using dwarf3 with fpc trunk causes less crashes (but still some) that dwarf3 with 3.0.4 on the same version of gdb.
As far as the Dwarf versions, well, yeah, but that's definitely an FPC issue, not a GDB issueYes and no. Fpc may well write something incorrect into the dwarf3 info. But gdb should give an error, not crash.
As far as the Dwarf versions, well, yeah, but that's definitely an FPC issue, not a GDB issueYes and no. Fpc may well write something incorrect into the dwarf3 info. But gdb should give an error, not crash.
In my expeience newer GDBs don't crash with that kind of thing, they just stop (which was sort of my whole point).
That just immediately shows the debugger checkmark icon (as it does with no debug info at all) for me if I build it with Dwarf3. With Dwarf2 it works properly and displays the string value."debugger checkmark icon" You mean "breakpoint with green checkmark"?
Are you already aware of this bug ?Don't know, is it in the bug tracker?
- Have Sparta designer setup.
- clock to go to designer
- click to get back to code editor
At this point the caret is no visible anymore and you have to minimize maximize so that a show event get generated which has for effect to restore the caret.
Once X is assigned, evaluate it (hover with the mouse).No crash here. GDB is 7.12 fpc = 3.3.1, Lazarus is 2.1.0 59416 OS Raspbian platform armhf
On my system gdb will just exit => crash
Are you already aware of this bug ?
- Have Sparta designer setup.
- clock to go to designer
- click to get back to code editor
At this point the caret is no visible anymore and you have to minimize maximize so that a show event get generated which has for effect to restore the caret.
Don't know, is it in the bug tracker?
Tests on MAC OSFixed
How to test the RC2 version when "lazarus-2.0.0RC2-i686-macosx.dmg" does not exist in the Sourceforge ?
That just immediately shows the debugger checkmark icon (as it does with no debug info at all) for me if I build it with Dwarf3. With Dwarf2 it works properly and displays the string value."debugger checkmark icon" You mean "breakpoint with green checkmark"?
You mean it does not stop at the breakpoint? Then add some statement, where it can stop.
I did, in the first place. It doesn't crash GDB. It just exits the program immediately.When gdb exits (without being instructed to do so) then what is that, but a crash?
Download and install the 2.0 RC2.
- 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
Download and install the 2.0 RC2.
- 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
#1 -- I did this successfully with RC2, but when I went to install the cross-compiler for x64, it did it over my primary installation without question. I just went to one of my other boxes and updated that box to RC2 outright.
#2 -- The Build Mode options indicate that they can be stored in the "environmentoptions.xml" as well as the .lpi files, but after the upgrade on box #2, I did not see the ones from the IDE at all. I had to recreate them. And they weren't in the actual environmentoptions.xml file either, even on the installation on box #1 (where they show up properly in the GUI).
1) The cross compile installers, now (from RC3 onwards) will allow choosing the directory to install to.
2) A 2ndary install will not see the modes from the primary install, and vice versa. But if you had them on the 2nd box (where I believe you updated the primary install), then they should work. Search for BuildMatrix in the file / make sure they exist before the upgrade)
Well I have found them in that file.
Make sure you look in the right place. In the IDE go to the menu "View" > "Ide Internals" > "About IDE"
Search for the "primary config path". In that folder look at the environmentoptions.xml
PLease Martin consider taking this patch https://bugs.freepascal.org/view.php?id=34527, for 2.0 or next RC if any.Applied a different fix, but the patch pointed to the origin of the issue. (see commit msg)
About the speed of the designer painting, have you tried in the options to set "reduced designer painting"?Wow, that helped a lot. Thanks.
The problems I reported before:Make sure it does not find your old config, if in doubt create a 2ndary install with a new conf dir.
- I have fpcupdeluxe on path for some reason, maybe for some android related setup I had configured previously.
So the setup uses the fpc in path instead of the shipped one, maybe as well that causes the debugger problems..
Lazarus fixes 2.0 compilation is broken. Rev 595071) 59507 that revision is trunk, not fixes.
FreePascal-3.0.5/lazarus-2.0.fixes/lazarus/ide/lazarus.pp(78,5) Fatal: (10022) Can't find unit LazDebuggerFpLldb used by Lazarus
Fatal: (1018) Compilation aborted
Both have DefaultDrawing and DoubleBuffered enabled.
without RDP the redrawing is still there but is much faster. (but still unnecessary)
Lazarus fixes 2.0 compilation is broken. Rev 595071) 59507 that revision is trunk, not fixes.
FreePascal-3.0.5/lazarus-2.0.fixes/lazarus/ide/lazarus.pp(78,5) Fatal: (10022) Can't find unit LazDebuggerFpLldb used by Lazarus
Fatal: (1018) Compilation aborted
2) What OS? And how did you start the build? Which command to execute?
It builds fine for me on windows and linux.
The problems I reported before:Make sure it does not find your old config, if in doubt create a 2ndary install with a new conf dir.
- I have fpcupdeluxe on path for some reason, maybe for some android related setup I had configured previously.
So the setup uses the fpc in path instead of the shipped one, maybe as well that causes the debugger problems..
Make sure you have no pre-installed fpc in your path.
--
I did a fresh install of the rc2 64bit win installer. The supplied lazarus.exe is 64bit (according to the windows task manager)
Lazarus fixes 2.0 compilation is broken. Rev 595071) 59507 that revision is trunk, not fixes.
FreePascal-3.0.5/lazarus-2.0.fixes/lazarus/ide/lazarus.pp(78,5) Fatal: (10022) Can't find unit LazDebuggerFpLldb used by Lazarus
Fatal: (1018) Compilation aborted
2) What OS? And how did you start the build? Which command to execute?
It builds fine for me on windows and linux.
59507 is what svn info reports.
Probably your last change broke it:
Autor del último cambio: mattias
Revisión del último cambio: 59505
Revision: 59505
Log: macos dmg: default debugger TFpLldbDebugger
Modified:
_U branches/fixes_2_0/
U branches/fixes_2_0/tools/install/macosx/environmentoptions.xml
It's linux 64 bits (Debian) using lazarus svn: URL: https://svn.freepascal.org/svn/lazarus/branches/fixes_2_0
I use my own scripts to automate building fpc and lazarus (the desired version). It fails simply executing: make clean bigide
As I said, it was working fine before latest commits.
First of all, sorry I tested with trunk.
I had a look at fixes_2.0.
It indeed has the problem, because some merges are yet missing. The problem is in 59503.
It will work again, when the pending merges from http://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch#Submitted_by_developer_.2F_committer.2C_tested.2C_waiting_to_be_merged have been applied.
LCLTMSFNCWPReg.pas(44,0) Error: Can't open resource file "/Developer/TMS FNC Dashboard Pack/TMSFNCDashBoardResources.dcr"
Build IDE: Exit code 512, Errors: 1
Fatal: Cannot find LCLTMSFNCBloxShapesFlowChart used by LCLTMSFNCBloxControl, incompatible ppu=/Developer/TMS FNC Blox/lib/i386-darwin/LCLTMSFNCBloxShapesFlowchart.ppu, package LCLTMSFNCBloxPkg
I have filed bug https://bugs.freepascal.org/view.php?id=34582
Honestly, this bug has "always" existed, but now would be a good time to fix it, with minimal effort.
Please note the bug I filed on the bug tracker for macOS (https://bugs.freepascal.org/view.php?id=34588). It is simply a uppercase/lowercase issue with the framework S(s)ecurity in the file components/fpdebug/fpdbgdarwinclasses.pas.Fixed by Matthias. Thanks.
Sorry for this ignorant question...
fixes_2_0 as of 3rd December, Cocoa not building.
cocoaprinters.inc(106,36) Error: identifier idents no member "lclCGContext"
106 of cocoaprinters.inc appears in this function -
procedure TCocoaPrinterView.drawRect(dirtyRect: NSRect); var Context: NSGraphicsContext; begin Context := NSGraphicsContext.currentContext; CGContextDrawPDFDocument(context.lclCGContext, CGRect(dirtyRect), doc, pageNum); end;
I don't really blame it, I cannot find any mention of lclCGContext under components either ! Is anyone else aware of this issue or can confirm its an issue ?
Davo
....Indeed it is.
This should have been fixed in revision 59723
There is a bug introduced in r59700 (svn). Rev 59699 is ok.r59700 merges r59492 from trunk. The commit is by Jesus with message :
There is a bug introduced in r59700 (svn). Rev 59699 is ok.r59700 merges r59492 from trunk. The commit is by Jesus with message :
"Printers: Support for Cocoa printing, updated examples."
Please report a regression bug in the bug tracker. It should be fixed before release.
I emailed Jesús about it before posting here. I guess he knows it but still no response.Thanks. A bug report is the way to go.
Filled a bug report: https://bugs.freepascal.org/view.php?id=34680
These events show up in the ide (Cocoa trunk) as TForm events, but not, as I can see, for other controls, for example TPaintBox. As TPaintBox is a TControl, shouldn't they?I don't know the details of this issue but I guess it will not be changed before 2.0 release.
I will prepare the patch to make MouseWheelHorz event for most of LCL ctrls.
The RC2 packages for AMD64 Debian are still not available:
https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%202.0RC2/
The package listed here is still the RC1. Beside that, it depends on fpc instead of fpc-laz, so it can't be installed.
Can please someone have a look why the RC1 package is listed here?
Sorry about that. Not sure what happened there.Okay, thanks Martin, good to know! So I will be patient!
Anyway we are planning on RC3 in the next week. So probably not going to rebuild RC2.
https://bugs.freepascal.org/view.php?id=34683I applied the patch. Thanks.
@JuhaAs wp noted, a square cross looks strange inside the rectangle. IMO things would get worse by the change.
Pls consider to apply first [safe one] patch from https://bugs.freepascal.org/view.php?id=34632
Okay, thanks Martin, good to know! So I will be patient!No need to be patient. You can easily get the sources of fixes 2.0 branch through SVN.
Just got feedback from the person in charge. RC2 is in place now.Sorry about that. Not sure what happened there.Okay, thanks Martin, good to know! So I will be patient!
Anyway we are planning on RC3 in the next week. So probably not going to rebuild RC2.
>As wp noted, a square cross looks strange inside the rectangle. IMO things would get worse by the change.Juha,
Just got feedback from the person in charge. RC2 is in place now.Oh wow, this was fast! Thanks Martin! :-)