Lazarus Release Candidate 2 of 3.0

[hamacker]

I don´t know why, but RC2 when I choose events onclick, onbefore[it],... sometimes (not all time) in uses interfaces section add units like DB, Grids, Forms... again! Not a probleam, just remove duplicates and will be OK for some time.
I think that is a parse problem, because I like to my 'use' like that (one per line):
uses
  Classes,
  SysUtils,
  Forms,
  Controls,
  Graphics,
  Dialogs,
  ExtCtrls,
  Buttons,
  ComCtrls,
  StdCtrls,
  DBGrids,
  DBCtrls,
  DBExtCtrls,
  ActnList,
  Variants,
  DB,
  ZDataset,
  ZAbstractRODataset,
  ZAbstractConnection,
  Grids,
  classe.nfe;

I build my lazarus from git.

It´s happens only with me, anyone?

[ASerge]

It´s happens only with me, anyone?

Very rarely, and not only in RC2.
And also a situation when you can't focus a form, but only components on it. And soon an error occurs and the IDE crashes. In RC2 too. Very rarely, also.

[dbannon]

RE: datetimepicker.pas(85,12) Error: Can't find unit DateTimePicker used by DateTimeCtrls

....
If you do an upgrade, and the lazarus dir is the same (or the config incorrectly keeps the old), then old files may remain. That is, files may have moved to new locations, since the previous release.

No Martin, I can demonstrate this problem on a perfectly clean (VM) install. A fresh build. Interesting things -

• The compiler mentions line 85, char 12 of datetimepicker.pas. That line is only five char long ....
• Even when the build fails, it appears to make viable datetimepicker.ppu and .o files in the expected place.

I think the problem is being misreported. Might be a strace job, see what really is being opened when the excrement hits the Air Movement Device. Maybe this evening when I have some time.

Davo

[Martin_fr]

call the complier with -va  (I think) and it will report each file it tries to open.

[TRon]

call the complier with -va  (I think) and it will report each file it tries to open.

-vt will do as well (I suggested that earlier) but doing a -va is perhaps the better option as it will display all and everything it is just a bit more work to find what you are looking for in the end-result. Piping is a must so that you can use a proper editor to view the results unless you can copy all the lines out of Lazarus.

[dbannon]

RE: datetimepicker.pas(85,12) Error: Can't find unit DateTimePicker used by DateTimeCtrls

Hmm, neither -va nor -vt seem to add any worthwhile information. I am watching the output from the console I launched startlazarus from because there does not seem, to me, any way to redirect Lazarus's rebuild of the IDE (is there ?).

I also tried my favourite, strace and it tells me that the build process successfully opened (eg) datetimepicker.ppu down in my .lazarus config location. But then tried to open datetimepicker.pas in the same place (see image). Obviously, it was not there and, I suspect, that triggered but was not responsible for the problem. I guess it checks for it in case the user has edited that .pas file. This is not about datetimepicker, its about the moving build files into user space.

So, as an experiment, I copied datetimepicker.pas from the readonly location to my .lazarus location and, sure enough, the problem moved to the next line of the compile list DateTimeCtrls. 

I have tried to build the IDE as a project (so I can use the debugger etc) but, of course, its in read only space and thats not possible. If I move it into user space, the problem does not show up. Its all about this moving the user's new build file into user space. Someone who understands that process needs to look at it.

Personally, I always build my Lazarus from source. And, right now, I am glad I do !

Sigh.

Any suggestions welcome.

Davo

[flowCRANE]

I have a question about the current state of the Lazarus. It has long been possible to set a separate style for case of labels and it works very nicely, but it only works when the case of block is in the body of the routine. Highlighter does not color labels in variant records — see attachment.

Can anyone let me know if label coloring in this block has been added yet?

[Martin_fr]

Highlighter does not color labels in variant records — see attachment.

Can anyone let me know if label coloring in this block has been added yet?

Nope it hasn't. Simply because the idea hadn't been brought up yet.

Ideally report a bug (feature request) about it, then it wont be forgotten.

[flowCRANE]

Ok, I will report this, thanks for feedback. Edit: issue created (#40586).

But please, next time consider all cases when implementing new highlighting feature, not only main one.

[Martin_fr]

You could say it was an oversight. But it simply hadn't occurred to me. Considering all cases requires awareness that there is something that one doesn't think about => but awareness would require one to think about it. 

[Bart]

You could say it was an oversight. But it simply hadn't occurred to me. Considering all cases requires awareness that there is something that one doesn't think about => but awareness would require one to think about it.

You do not see what you do not see...
(AKA a blindspot)

Bart

[Martin_fr]

But please, next time consider all cases when implementing new highlighting feature, not only main one.

"cases"... pun intended?

[ermeneuta]

I tried to install Lazarus 3.0RC2 under Armbian on my Rock 5A board, by compiling the source, given that a DEB package does not exist for my configuration.
I issued make clean, then make bigide. Compilation was successful, but at link time I received these error messages :

Code: Pascal  [Select][+][-]

1. Linking ./lazres
2. /usr/bin/ld.bfd: /usr/lib/fpc/3.2.2/units/aarch64-linux/rtl/cprt0.o: in function `_start':
3. (.text+0x54): undefined reference to `__libc_csu_init'
4. /usr/bin/ld.bfd: (.text+0x58): undefined reference to `__libc_csu_init'
5. /usr/bin/ld.bfd: (.text+0x5c): undefined reference to `__libc_csu_fini'
6. /usr/bin/ld.bfd: (.text+0x60): undefined reference to `__libc_csu_fini'
7. lazres.pp(395) Error: Error while linking

Is there a fix for this ? Thanks

-Fred

[vangli]

An observation regarding RC2 errors when rebuilding IDE, which is necessary when installing packages.

- Installed from 64 bit deb package. Splash screen states RC1.
- Compiling from source files. Splash screen states RC2.
- As user, start source compiled version with startlazarus, asks for updating user config files. (After first running deb version)
- Then, if start deb version with compiled startlazarus, it ask for downgrading user config files.

Could it be that the 64bit deb somehow is incomplete or have other errors? E.g. some changes from RC1 to RC2 hasn't been included?

Edited: And RC2 deb file is 10 MByte lesser than RC1.

[ikel]

Congrats for the Lazarus Release Candidate 2!