Will it be 2.5.2, 2.6.0 or 3.0.0 ? I'm curious.

Op 2011-02-28 14:49, Alexsander Rosa het geskryf:

Will it be 2.5.2, 2.6.0 or 3.0.0 ? I'm curious.

Michael van Canneyt told me this morning it will be FPC 2.4.4, and will be released really soon.

Regards,
- Graeme -

Graeme Geldenhuys wrote

Michael van Canneyt told me this morning it will be FPC 2.4.4, and will be released really soon.

Before or after 0.9.30 release of Lazarus?

Michael

But will it be able to compile Lazarus from SVN/trunk? In other words, will 2.5.1 be released as 2.4.4 ?

2011/2/28 Graeme Geldenhuys

Alexsander Rosa wrote

But will it be able to compile Lazarus from SVN/trunk? In other words, will 2.5.1 be released as 2.4.4 ?

No.

2.4.4 is a fixes release of 2.4.4.

2.5.1 is scheduled for release as 2.6.0. When this will be is unknown at this time.

Michael.

Ok, thanks. The bugtrack "roadmap" page has 3.0.0 only, probably I was looking in the wrong place.
Where do I find the roadmap for 2.6.0? Is there a way to filter the issues list to show what's missing?

2011/2/28

Alexsander Rosa wrote

Ok, thanks. The bugtrack "roadmap" page has 3.0.0 only, probably I was looking in the wrong place. Where do I find the roadmap for 2.6.0? Is there a way to filter the issues list to show what's missing?

Not to my knowledge, FPC does not maintain an official roadmap. We don't want to be pinned down ;-)

Michael.

Alexsander Rosa wrote

But will it be able to compile Lazarus from SVN/trunk? In other words, will 2.5.1 be released as 2.4.4 ?

It does it right now. I usually compile Lazarus with fpc 2.5.1 both from svn trunk.

Alexsander Rosa wrote

Ok, thanks. The bugtrack "roadmap" page has 3.0.0 only, probably I was looking in the wrong place.

See http://www.freepascal.org/faq.var#versions for a short summary about versioning.

Where do I find the roadmap for 2.6.0? Is there a way to filter the issues list to show what's missing?

FPC does not maintain roadmaps and the featureset of a major branch is more or less based on what is in SVN on the moment of branching. There is of course some communication about that, but it is mostly internal and informal.

That being said, specially when branching a major branch, it is hard to get an overview what has been added but not merged (for e.g. the release manifest), and some more administration on this front wouldn't be bad.

Something like Jonas did with User changes, and then for all features, not just the breaking ones.

I don't know whether I've understood your intention right, but what about this: http://wiki.lazarus.freepascal.org/FPC_New_Features_Trunk ?

Regards,
Sven

Yes something like that. It is fairly new(december) which is why I didn't know about it.

AFAIK, Lazarus 0.9.30 will be the last Lazarus release able to be compiled with an official FPC release. The current Lazarus trunk needs FPC 2.5.1 and FPC 2.6.0 is going to be released in a distant future. So we have, for the first time, a "gap": you can't be partly bleeding-edge anymore. Before that, I used to get Lazarus from SVN (and report a few issues/send some patches along the way) with a "stable" FPC. When 0.9.30 comes out in a few days, we will have to choose between Lazarus/FPC both official releases (an no more bug reports/patches) or Lazarus/FPC both from bleeding edge SVN, with 2 times more probability of instability. I'm aware I'm whining here, but I think I'm not the only one in this situation.

2011/3/4 Marco van de Voort

2011/3/4 Alexsander Rosa :

The current Lazarus trunk needs FPC 2.5.1 and FPC 2.6.0 is going to be released in a distant future. So we have, for the first time, a "gap": you can't be partly bleeding-edge anymore.

I am sure that Lazarus SVN compiles with FPC 2.4.2 in Linux and Mac OS X. Which problem are you having?

AFAIK, Lazarus 0.9.30 will be the last Lazarus release able to be compiled with an official FPC release. The current Lazarus trunk needs FPC 2.5.1

Why do you think so?
It compiles with 2.4.2.

Mattias

A few weeks ago, when 0.9.30 fixes was branched, I've tried to compile Lazarus trunk with a released FPC and it failed. At the same time, someone else complained here with the same error I had and the answer was:

After that I moved to 0.9.30 fixes and did not tried again. I will try again.

2011/3/4 Mattias Gaertner

2011/3/4 Alexsander Rosa :

If you use lazarus trunk svn head,with fpc trunk, you must use fpc trunk *svn head* too. You did not, so your fpc 2.5.1 was too old.

Vincent

2011/3/4 Vincent Snijders :

If you use lazarus trunk svn head,with fpc trunk, you must use fpc trunk *svn head* too. You did not, so your fpc 2.5.1 was too old.

So, if you update lazarus and compilation fails with fpc 2.5.1, you must update fpc too.

Vincent

Just as a note, sometimes there can be additional problems with compiling FPC/Lazarus from SVN.
In both the case of FPC and Lazarus, sometimes a file or two gets moved between directories in the SVN directory tree and when someone does a "make clean..." after an "svn update..." the clean will not remove the older one from the install "units" directory and that can cause problems with future compiles, rebuilds.
Sometimes I got "checksum changed" error in a file at rebuild, sometimes packages did not compile, sometimes the rebuild did not find things, etc.

I just had this problem a few days ago when after 2-3 months I updated my FPC and Lazarus SVN from the trunk and tried to recompile both.

1. First of all I had to delete the target directories of the installed versions of FPC and Lazarus ("make clean" should do this but since the moved file is now in a new directory, it tries to delete it from the new place instead of from the old place therefore leaving the old one there)

2. Then I deleted all SVN checkouts for both FPC and Lazarus and checked them out again into a clean directory

3. I used the last stable FPC version to compile the new FPC trunk first (sometimes you can not successfully compile the latest FPC 2.5.1 with a one or two months old FPC 2.5.1)

4. Then I could compile the latest SVN FPC again with itself (compiled a 2.5.1 with a 2.5.1 made by a 2.4.x....confused enough yet?)

5. Checked out Lazarus from SVN into a clean dir and built it, installed it

6. Removed the Lazarus settings directory before 1st start and then tested a rebuild from within Lazarus after setting the FPC dir in the environment menu. If this works without a problem, you can start adding the packages you use.

7. I had a problem with the latest stable Zeos 6.6.6 because it did not compile. After looking it up on the net, I found the necessary changes needed for Zeos to compile (changes were needed in one of the source files, ZClasses.pas) under FPC 2.5.1.

After a few hours I had a newly working FPC/Lazarus installation. This all is not for the faint heart... but can be done.

AB

That's why I do it the following way:

I have one directory for FPC and one for Lazarus which are the SVN working copies (but I'm not "working" in them). When I do an update I export that working copy to a build directory and build the new version there. If that new build works I remove my old build and move the new one to the location of the old build. So I don't have the problem of forgotten files ^^ (and I normally keep my Lazarus configuration as well)

Regards,
Sven

I just run svn status from time to time after clean. Saves an export step each time.

The export trick is better for unattended building though.

BTW, Is it already ok to break compilation of Lazarus trunk with 2.2.4?

2011/3/5 Alexander Klenin :

Generally, yes, but Felipe wanted to keep it compatible with fpc 2.2.4 to make it easier to find regressions on arm-wince.

Vincent

Vincent Snijders wrote

Generally, yes, but Felipe wanted to keep it compatible with fpc 2.2.4 to make it easier to find regressions on arm-wince.

I think that this issue isn't a problem anymore, because the issue which I was tracking was a crash in phones, and now wince is no longer being used in new phones.