Recent

Author Topic: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)  (Read 100244 times)

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #105 on: November 22, 2017, 08:22:34 pm »
When simply adding a subfolder to PATHS
and NOT adding even one of the PAS files there
the compiler runs through all files.
What means "all files"?
I am also not sure what PATHS means here. A path in "Other unit files (-Fu)" is only passed to the compiler with -Fu.

Quote
A file named CHARACTER.PAS exists in both FPC folder and UTF8tools ZIP.
So there something interfers with UTF8tools and Laz 1.8 RC5
CHARACTER.PAS may be in both places but it is not related to Lazarus 1.8 RC5 anyhow.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #106 on: November 22, 2017, 08:28:33 pm »
Does anyone know when the final release is expected to be published?   :-\
Very soon after FPC 3.0.4 is released!
Lazarus 1.8 is held back waiting for it. The Windows version of RC5 already uses a self built FPC 3.0.4.
This is annoying because FPC 3.0.4 was already tagged a long time ago, meaning it is ready. Somebody only must build it.
Please ask FPC developers when will they release.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

BeniBela

  • Hero Member
  • *****
  • Posts: 905
    • homepage
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #107 on: November 23, 2017, 12:24:32 am »
The modern way would be to have a build server in the cloud that builds everything on every commit

Thaddy

  • Hero Member
  • *****
  • Posts: 14159
  • Probably until I exterminate Putin.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #108 on: November 23, 2017, 10:20:25 am »
The modern way would be to have a build server in the cloud that builds everything on every commit
The modern surest way would be to have a build server in the cloud that builds everything on every commit to make a failed build.
I am running a build farm. Commits are not always complete. A noob will run into trouble he/she can't explain. Bad advice. You and I can do that, but that is not for everyone.

(I actually think you agree with me on this.... :o )
« Last Edit: November 23, 2017, 10:22:26 am by Thaddy »
Specialize a type, not a var.

PeterX

  • Sr. Member
  • ****
  • Posts: 404
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #109 on: November 23, 2017, 03:34:29 pm »
What means "all files"?
I am also not sure what PATHS means here. A path in "Other unit files (-Fu)" is only passed to the compiler with -Fu.
PATHS means adding a path to the project settings, here:  folder "UTF8tools"

I have set up a test project.


Quote
CHARACTER.PAS may be in both places but it is not related to Lazarus 1.8 RC5 anyhow.
C:\lazarus\fpc\3.0.4\source\rtl\objpas\character.pas

It took some time to find out that character.pas in UTF8tools interrupts the compiling in my project.
« Last Edit: November 23, 2017, 04:25:21 pm by PeterX »
usually using latest Lazarus release version with Windows 10

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #110 on: November 23, 2017, 04:55:39 pm »
PATHS means adding a path to the project settings, here:  folder "UTF8tools"
There are many project settings. Do you mean "Other unit files (-Fu)"? You should never use it for library code! Lazarus packages are meant for that purpose and UTF8tools provides a package. Use it please. It may solve the acute problem but the fundamental problem is having 2 units with identical names.

Quote
C:\lazarus\fpc\3.0.4\source\rtl\objpas\character.pas
Yes, as I wrote the problem is not related to Lazarus or its release candidate anyhow.
It is caused by an external package (UTF8tools) having a unit name conflicting with FPC's libraries.
UTF8tools should respect the choice of unit names in FPC libs and name its units differently. Now also dotted names can be used.
Please contact its author about the problem.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

PeterX

  • Sr. Member
  • ****
  • Posts: 404
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #111 on: November 23, 2017, 05:05:55 pm »
.. UTF8tools provides a package. Use it please.
I do not need the UTF8tools in any other program. Or on design time.
So why not using the units there in the folder manually ?
usually using latest Lazarus release version with Windows 10

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #112 on: November 24, 2017, 10:15:49 pm »
I do not need the UTF8tools in any other program. Or on design time.
So why not using the units there in the folder manually ?
I guess it works well if you use it for one project only.
Once you set the same "Other unit files (-Fu)" path for many projects, you may get strange compilation issues. It is just wrong because the feature is not designed for shared code.
Packages are for shared code! You should make it a habit to use them always.

Note, this is different from Delphi. There either a project's unit path or a global unit path is used for all library code. The global unit path is especially stupid because it pollutes the name space for all projects even if they don't need a certain library/package.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

PeterX

  • Sr. Member
  • ****
  • Posts: 404
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #113 on: November 24, 2017, 10:52:35 pm »
Note, this is different from Delphi. There either a project's unit path or a global unit path is used for all library code. The global unit path is especially stupid because it pollutes the name space for all projects even if they don't need a certain library/package.
Thank You for this detailed explanation !

At the end the reason for the unexpected error message was two "character.pas" files in the unit paths ...
I was a little bit in trouble because the error message didn't say anything about the cause.
usually using latest Lazarus release version with Windows 10

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #114 on: November 24, 2017, 11:42:17 pm »
At the end the reason for the unexpected error message was two "character.pas" files in the unit paths ...
Yes, a poorly named unit.
BTW, why do you need UTF8tools? If LazUTF8 and other units in LazUtils don't have some function, we can add it.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

BeniBela

  • Hero Member
  • *****
  • Posts: 905
    • homepage
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #115 on: November 25, 2017, 07:05:37 pm »
I put all my paths in fpc.cfg

Then I can use uses theunit, in any program without additional configuration and even compile it with nothing more than fpc project.lpr on the command line

When a unit has a stupid name,  I rename it

PeterX

  • Sr. Member
  • ****
  • Posts: 404
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #116 on: November 25, 2017, 10:39:33 pm »
BTW, why do you need UTF8tools? If LazUTF8 and other units in LazUtils don't have some function, we can add it.
I wrote a Windows Explorer like program that displays some type of files decoded.

In case of text files I needed code that automatically converts the text in the file
to the native Lazarus UTF8 format to be displayed in a TMemo.

UTF8tools does the job.
usually using latest Lazarus release version with Windows 10

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #117 on: November 25, 2017, 11:55:32 pm »
In case of text files I needed code that automatically converts the text in the file to the native Lazarus UTF8 format to be displayed in a TMemo.
UTF8tools does the job.
Unit LConvEncoding in LazUtils also has many conversion functions. I am interested what is missing. I have nothing against using UTF8tools but I want to improve code in LazUtils.
UTF8tools appears to be very comprehensive. It has lots of detailed Unicode information. I believe it is very good for advanced uses although I have not needed such features myself.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

piola

  • Full Member
  • ***
  • Posts: 118
  • Lazarus 2.2, 64bit on Windows 8.1 x64
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #118 on: November 28, 2017, 06:09:14 pm »
FPC 3.0.4 has finally been released  :)

So I hope we can look forward to the wishfully awaited Lazarus 1.8 soon  :) :)

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4458
  • I like bugs.
Re: Lazarus Release Candidate 5 of 1.8 (includes RC1 fpc 3.0.4)
« Reply #119 on: November 28, 2017, 08:47:07 pm »
FPC 3.0.4 has finally been released  :)
Where did you see the announcement?
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

 

TinyPortal © 2005-2018