Lazarus Release 2.2.6

[DreamVB]

Thanks you for all your hard work.

[Martin_fr]

On Linux LMDE5 taking error on the start:

Directory: /usr/share/fpcsrc/3.2.2/
Warning: Found version 3.2.2, expected 3.3.1
You can download FPC and the FPC sources from http://sourceforge.net/projects/lazarus/?source=directory

Result in messages on compilation:

Compile Project, Target: /home/bs/tmp/project1: Exit code 1, Errors: 1
project1.lpr(12,3) Fatal: Can't find unit Interfaces used by Project1

Did you have another fpc version installed before? Maybe you need to uninstall that first.
On Linux it is tricky to have more than one fpc version at the same time.

[bobihot]

Did you have another fpc version installed before? Maybe you need to uninstall that first.
On Linux it is tricky to have more than one fpc version at the same time.

I have only FPC version 3.2.2 installed with lazarus 2.2.4
But he maybe wanted version 3.3.1?

[dbannon]

On Linux it is tricky to have more than one fpc version at the same time.

Not really Martin. It all depends on $PATH, I have this at the end of my .bashrc script -

Code: Bash  [Select][+][-]

1. FPCV='fpc-3.2.2'
2. export OLD_PATH="$PATH"
3. export PATH="$HOME/bin/FPC/$FPCV/bin":"$PATH"

If I want to go back to, eg, 3.2.0 I'd type -

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

1. export PATH="$HOME/bin/FPC/fpc-3.2.0/bin":"$OLD_PATH"

In both cases, FPC installed from a tarball in user space.

Davo

 

[TRon]

On Linux it is tricky to have more than one fpc version at the same time.

Not really Martin. It all depends on $PATH, I have this at the end of my .bashrc script -

If I want to go back to, eg, 3.2.0 I'd type -

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

1. export PATH="$HOME/bin/FPC/fpc-3.2.0/bin":"$OLD_PATH"

Code: [Select]

-V

As alternative you can also use an alias or a link as that also saves you from using/modifying the path environment variable.

Make sure to have properly configured paths in fpc.cfg.

What does make things very messy is when someone installs FPC using the package manager /and/ also builds/installs a standalone compiler. In such cases it is easier to just use a complete standalone setup and leave the systems package manager for what it is. Also a recipe for disaster seems to be installing a Lazarus which also contains FPC icw the system package manager and/or a stand-alone build. If you wish to have multiple FPC versions then it is better to DIY and adjust other software to use that stand-alone setup. The only tool that currently does not seem to play game with that is the FPC package manager (but that might be just me).

edit: link to FPC version switching

[PierceNg]

I run zsh. Idea's the same as what dbannon wrote. With these, I switch by doing like "path0; fpc331path". I also have jdk8path, jdk11path, node16path, node18path and so on.

Code: Text  [Select][+][-]

1. export PATH0CAR=standard stuff that should be found first
2. export PATH0CDR=standard stuff that can be overridden by stuff earlier in the path
3. export PATH=$PATH0CAR:$PATH0CDR
4.  
5. function path0() {
6.   export PS1="%n@%m:%~%# "
7.   export PATH=$PATH0CAR:$PATH0CDR
8.   hash -r
9. }
10.  
11. function fpc331ccpath() {
12.   export OLD_PS1=$PS1
13.   export PS1="[fpc331cc] $OLD_PS1"
14.   export FPCPATH=~/pkg/fpc331/bin:~/pkg/fpc331/lib/fpc/3.3.1
15.   export PATH=$PATH0CAR:$FPCPATH:$PATH0CDR
16.   hash -r
17. }
18.  
19. function fpc331path() {
20.   export OLD_PS1=$PS1
21.   export PS1="[fpc331 laz22] $OLD_PS1"
22.   export FPCPATH=~/pkg/fpc331/bin:~/pkg/fpc331/lib/fpc/3.3.1:~/pkg/lazarus22b
23.   export PATH=$PATH0CAR:$FPCPATH:$PATH0CDR
24.   hash -r
25. }
26.  
27. function fpcllvmpath() {
28.   export OLD_PS1=$PS1
29.   export PS1="[llvm14 fpcllvm] $OLD_PS1"
30.   export LLVMPATH=~/pkg/llvm14/bin
31.   export FPCPATH=~/pkg/fpcllvm/bin:~/pkg/fpcllvm/lib/fpc/3.3.1
32.   export PATH=$LLVMPATH:$PATH0CAR:$FPCPATH:$PATH0CDR
33.   hash -r
34. }

[Al-Eid]

Thanks to all
Good luck

[Martin_fr]

Did you have another fpc version installed before? Maybe you need to uninstall that first.
On Linux it is tricky to have more than one fpc version at the same time.

I have only FPC version 3.2.2 installed with lazarus 2.2.4
But he maybe wanted version 3.3.1?

3.2.2 is correct

What happens if you open a terminal and run
   fpc

What does it output?

[RadDeveloper]

Hi Lazarus Team! Since the two last releases, this issue hasn't been fixed :-(

Here is the bug in this version. Here the steps: Launch Lazarus IDE, Click Project -> View Project Source, then close project1.lpr page, then again Click Project -> View Project Source, then the source page appears to be blank (no project code inside), and cannot compile a project.

Thanks.

I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

But that only happens on new project, so the steps to produce the issue are:
1. Start Lazarus
2. File > New > Project > Application > OK
3. Project > View Project Source
4. Close the project1.lpr tab on the Source Editor
5. Project > View Project Source

[af0815]

Is the project1.lpr saved gefore or not ? I cannot see this on a saved project.
Open the Project inspector and if your lpr is still in project

[chenyuchih]

Great news! Thank you all the Lazarus team(and fpc staffs also)

[Ericktux]

muchas gracias a todo el equipo lazarus, saludos desde Perú 

[dbannon]

Hi Lazarus Team! Since the two last releases, this issue hasn't been fixed :-(

Here is the bug in this version. Here the steps: Launch Lazarus IDE, Click Project -> View Project Source, then close project1.lpr page, then again Click Project -> View Project Source, then the source page appears to be blank (no project code inside), and cannot compile a project.

Thanks.

I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

But that only happens on new project, so the steps to produce the issue are:
1. Start Lazarus
2. File > New > Project > Application > OK
3. Project > View Project Source
4. Close the project1.lpr tab on the Source Editor
5. Project > View Project Source

as af0815 says, at no stage in that process has the project been saved. If you close it without saving, you cannot really expect it to be there can you ?

Davo

[dsiders]

Hi Lazarus Team! Since the two last releases, this issue hasn't been fixed :-(

Here is the bug in this version. Here the steps: Launch Lazarus IDE, Click Project -> View Project Source, then close project1.lpr page, then again Click Project -> View Project Source, then the source page appears to be blank (no project code inside), and cannot compile a project.

Thanks.

I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.

But that only happens on new project, so the steps to produce the issue are:
1. Start Lazarus
2. File > New > Project > Application > OK
3. Project > View Project Source
4. Close the project1.lpr tab on the Source Editor
5. Project > View Project Source

as af0815 says, at no stage in that process has the project been saved. If you close it without saving, you cannot really expect it to be there can you ?

Davo

Better tell someone to go break version 2.3.0 then. Because it does not exhibit that behavior. So, error or not, it won't exist in version 2.4.

[dalfy]

Hello.
Where can I place a proposal for the FPDoc documentation module?
Suggestion: after renaming the variable (by F2), as well rename the variables in the xml file.