The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2.

We invite all users to test this Release Candidate. Please read here why everybody really should join the testing now.

News in this Version
http://wiki.lazarus.freepascal.org/Lazarus_1.2.0_release_notes

On Windows the installer now allows 2 independent installations. http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus

About the release process:
http://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch#Roadmap_to_1.2

The 1.2.0RC2 is built with fpc 2.6.2.

The release is available for download on SourceForge: http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 1.2RC2" directory.

Minimum requirements:
Windows: 98, 2k, XP, Vista, 7, 32 or 64bit
FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit
Mac OS X: 10.5 to 10.8, LCL on carbon only 32bit, non LCL apps can be 64bit

== Why should everybody (including you) test the release candidate? ==

It the past months the Lazarus team has stabilized the 1.2 fixes branch. The resulting 1.2RC2 is now stable enough to be used by any one for test purposes.

However many of the fixes and new features that were committed since the release of 1.0 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million.

Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.2.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features.

== How to test ==

Download and install the 1.2RC2.
- 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
- On other platforms, if you install to a new location you need to use --primary-configpath

In either case you should make backups. (including your primary config)

Open your project in the current Lazarus (1.0.14), and use "Publish Project" from the project menu. This creates a clean copy of your project.

You can then open that copy in the RC2. Please test:
- Can you edit forms in the designer
- rename components / change properties in Object inspector / Add new events
- Add components to form / Move components on form
- Frames, if you use them
- Can you navigate the source code (e.g. jump to implementation)
- Auto completion in source code
- Compile, debug and run
- Anything else you use in your daily work

Mattias

Hi,
Can I use Lazarus on Windows 8.1?

-------- ?????????? ????? --------
??: Mattias Gaertner
???????: [Lazarus] Lazarus Second Release Candidate, 1.2RC2 ??:
????????? ??: ??????????, 2014, ?????? 13 19:34:19 EET

The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2.

We invite all users to test this Release Candidate.

Please read here why everybody really should join the testing now.

News in this Version

http://wiki.lazarus.freepascal.org/Lazarus_1.2.0_release_notes

On Windows the installer now allows 2 independent installations.

http://wiki.lazarus.freepascal.org/Multiple_Lazarus#Installation_of_multiple_Lazarus

About the release process:

http://wiki.lazarus.freepascal.org/Lazarus_1.2_fixes_branch#Roadmap_to_1.2

The 1.2.0RC2 is built with fpc 2.6.2.

The release is available for download on SourceForge:

http://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 1.2RC2" directory.

Minimum requirements:

Windows: 98, 2k, XP, Vista, 7, 32 or 64bit

FreeBSD/Linux: gtk 2.8 or qt4.5, 32 or 64bit

Mac OS X: 10.5 to 10.8, LCL on carbon only 32bit, non LCL apps can be 64bit

== Why should everybody (including you) test the release candidate? ==

It the past months the Lazarus team has stabilized the 1.2 fixes branch. The resulting 1.2RC2 is now stable enough to be used by any one for test purposes.

However many of the fixes and new features that were committed since the release of 1.0 required changes to the code of existing features too. While we have tested those ourself, there may still be problems that only occur with very specific configurations or one project in a million.

Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 1.2.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features.

== How to test ==

Download and install the 1.2RC2.

- 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

- On other platforms, if you install to a new location you need to use --primary-configpath

In either case you should make backups. (including your primary config)

Open your project in the current Lazarus (1.0.14), and use "Publish Project" from the project menu. This creates a clean copy of your project.

You can then open that copy in the RC2. Please test:

- Can you edit forms in the designer

- rename components / change properties in Object inspector / Add new events

- Add components to form / Move components on form

- Frames, if you use them

- Can you navigate the source code (e.g. jump to implementation)

- Auto completion in source code

- Compile, debug and run

- Anything else you use in your daily work

Mattias

Yes, I do so.

Michael.

Is it really necessary to mention exe size in the Windows installer? It looks very weird that from everything about Lazarus this has to be mentioned in the installer.

Maybe a "tips" or "faq" or something in a "welcome" screen that answers this and other "first" questions ("how do i enabled opengl?", "how do i use a single window?", etc) should be better? (of course such a welcome screen needs to be coded first :-P

2014/1/14 Michael Van Canneyt :

Of course, I am already using it under Windows 8.1!

Stefanos

On Wednesday, January 15, 2014 12:43 PM, Kostas Michalopoulos wrote:

Is it really necessary to mention exe size in the Windows installer? It looks very weird that from everything about Lazarus this has to be mentioned in the installer.

Maybe a "tips" or "faq" or something in a "welcome" screen that answers this and other "first" questions ("how do i enabled opengl?", "how do i use a single window?", etc) should be better? (of course such a welcome screen needs to be coded first :-P

2014/1/14 Michael Van Canneyt :

The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2. We invite all users to test this Release Candidate. Please read here why everybody really should join the testing now.

I've tried to test it, but couldn't make it work at all :-(

It would be nice to have a complete distribution package, that also performs the installation as seen by the users later. Size is not a problem (to me), but I cannot continue to use or recommend the use of Lazarus, when it takes significantly more than one hour before it's ready for testing.

DoDi

Mattias Gaertner wrote

The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2.

Well done! I'd love to stick to this branch.

lazbuild crashes for me, though:

hcv at technical09:~/source/lazarus$ ./lazbuild --help [FORMS.PP] ExceptionOccurred
Sender=Exception
Exception=Unknown Run-Time error : 210
Stack trace:
$080483E6 FILTERCONFIGFILECONTENT, line 190 of lazbuild.lpr $08051889 main, line 1679 of lazbuild.lpr
$B7590E46
TApplication.HandleException Unknown Run-Time error : 210 Stack trace:
$080483E6
$08051889
$B7590E46
exception at 080483E6:
Unknown Run-Time error : 210.

GetCfgFileContent() returns nil, since I don't have a lazarus.cfg anywhere on my computer. Code in FilterConfigFileContent() doesn't check the return result of GetCfgFileContent(), so it crashes.

Henry

I see this has been fixed in trunk (revision 43703). Can someone merge this, please.

Henry

Henry Vermaak wrote

lazbuild crashes for me, though:

That has already been fixed in r43703 in trunk and merged to 1.2.

Bart

I can't see it in fixes_1_2?

A "tip of the day" or even "tip" depending on action, that shows useful info within the IDE itself would be great. If someone would write the code... Right now, we do not have this code, and we do not have anybody who writes it.

So displaying something in the installer was the easiest option. "Exe size on windows" is (for win users) the single most often asked question. And for some reason a lot of people do not read the FAQ. So this seemed the best solution.

It was already put in 2nd place, to avoid starting with a "problem". First is the "what is Lazarus" (not very useful, in the installer, since a person running the installer will already have an idea).

Am I the only one missing this? I've fixed mine locally, for now.

Henry

Actually you were are right. It was supposed to be merged, but somehow got lost... Done now, thanks for the persistence

I think is much better change the default behavior to generate a external debug file but i don't know if it has any consequence...

2014/1/15 Martin

William Oliveira Ferreira wrote

I think is much better change the default behavior to generate a external debug file but i don't know if it has any consequence...

Definitely!
I also wondered why this is *not* the default.
What are the reasons?
Unexperienced users wonder why their exe file is so big and experienced users know how to change it anyway.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140116/02172991/attachment.html>

Buggy GDB? (at least that's what I would think is the most plausible reason ^^)

Regards,
Sven

Thanks, it's working well now.

Henry

Thanks, Michael and

Stefanos !

-------- ?????????? ????? --------
??: Stefanos Beligiannis
???????: Re: [Lazarus] Lazarus Second Release Candidate, 1.2RC2 ??: Lazarus mailing list
????????? ??: ?????, 2014, ?????? 15 12:53:30 EET

Of course, I am already using it under Windows 8.1! Stefanos

On Wednesday, January 15, 2014 12:43 PM, Kostas Michalopoulos wrote: Is it really necessary to mention exe size in the Windows installer? It looks very weird that from everything about Lazarus this has to be mentioned in the installer. Maybe a "tips" or "faq" or something in a "welcome" screen that answers this and other "first" questions ("how do i enabled opengl?", "how do i use a single window?", etc) should be better? (of course such a welcome screen needs to be coded first :-P 2014/1/14 Michael Van Canneyt >: > > > On Tue, 14 Jan 2014, Kamen Ketev wrote: > >> >> Hi, >> >> Can I use Lazarus on Windows 8.1? >> > > Yes, I do so. > > Michael. > > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140116/3638d065/attachment.html>

Don't know.. Probably "Never touch a working system". The debugger has enough issues as it is.

Changing this would need to be tested on many versions, of many OS (and for some many Distributions), with many versions of gdb, and linkers involved. (Not to mention at least 2 released fpc fixes and trunk.) That is a lot of work.
Well ok, we could just put it out there, and wait for reports.

Then IMHO, it is not just changing it. At the very least, the IDE must clean up the dbg file, if the exe is rebuild (without dbg info)

Also it needs te be changed in many places (lazbuild, makefiles...). I tried to make dwarf default, a some ,time ago. I reverted, because it it turned out to need more and yet even more changes. -------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140116/b73c38f1/attachment.html>

Hi Barth,

I use a external debug file and never noticed any issue. Can you tell something about it? I'm just curious and I wanna know that to do when happens...

2014/1/16 Sven Barth

Am 16.01.2014 15:49 schrieb "William Oliveira Ferreira" <

: Hi Barth,

Note: here we prefer first names, which for me is "Sven" ;)

I use a external debug file and never noticed any issue. Can you tell

something about it? I'm just curious and I wanna know that to do when happens...

I didn't say that it does not work. I said that this is the most likely I can imagine.

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140116/40bdbf2d/attachment.html>

16.01.2014 18:41, Martin ?????:

Somehow I don't think that this change will be as complex as changing default debug format. Anyway, we can try to enable it in trunk and see what happens.

If you want to try, go ahead.

What happens, if you have an external info file, and rebuild the exe (but without creating new debug info)? Will the wrong info be applied? Or will it be ignored?

----
Another issue is, that some people even complain about the size of a none debug exe (empty form project compiled). They compare with Delphi, but they do not add the size of any run time dependency/ package that the delphi project needs. (IIRC / Afaik).

While this is not addressed in the installer hint, there is still a chance that once a user was pointed to "the FAQ has file size info", they will look (ok maybe I am to optimistic)

"Martin" wrote

Another issue is, that some people even complain about the size of a none

debug exe (empty form project compiled). They compare with Delphi, but they do not add the size of any run time dependency/ package that the delphi project needs. (IIRC / Afaik).

No, at least in older versions (before Delphi 2009) also static ones are smaller than stripped Lazarus ones. But then they only have to support one platform... (in younger versions the extended RTTI blows up quite a bit).

Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140116/40bb3b56/attachment.html>

16.01.2014 23:55, Martin ?????:

I think that it should be your decision, because you will have to sort out possible bugs. Personally I am fine with current default.

What happens, if you have an external info file, and rebuild the exe (but without creating new debug info)? Will the wrong info be applied? Or will it be ignored?

Don't know, I think this should be handled by GDB? AFAIK if exe was built without debug info, old debug info file won't be applied. The case you describe can happen only if user manually moves/copies exes without correct debug file, but even then probably GDB has some protections.

For me it is not a priority at the moment. Especially not, if I have to sort out the problems from it.

I dont know, but it needs to be tested, and that takes time. (Again different GDB, different platform, potentially different linkers)

2014/1/16 Martin

??
?well, i think this issue affects expecially the IDE users and I wondering that lazarus always make their way to rebuild that file?

I don't quite understand your answer.
AFAIU, Martin is describing this scenario:
1. You build a project with external gdb info file
2. You change the settings (or choose a different build mode) so it does not generate an external gdb info file, but do not remove the existing gdb info file
3. You change the code and recompile, generating a new executable (and now the gdb info file and executable are out of sync)

Are you saying the gdb info file will be ignored? If so, that is good to know.

Hello M-List,

I am pleased with the progress/effort in the freepascal/lazarus eco-space and would like to do a little donation. I already did two donations in the past for lazarus, but this time I'd like to donate to the freepascal team.

Does the freepascal team also have a donation account?

Regards,

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20140118/f74c0e54/attachment-0001.html>

as I said, I'm just a user of the feature, I don't really know what implications can came with this change. Today, if you change debug profile to another that doesn't generate that file, the compiler doesn't ignore it?Here, I tested (Lazarus 1.0.14 r43446 FPC 2.6.2 i386-win32-win32/win64)
with an old project that have 2 build modes and one of them doesn't generate any debug symbols. Lazarus has just ignored my break points. Lazarus doesn't removed my debug file. Could this be a hint that external debug symbols could be used without issues?

2014/1/18 Reinier Olislagers

No, it does not.

Michael.

I noticed that the behavior of separatators and dividers in TToolbar changed so that it now draws two lines for separators while previously it only left some space... i do not think this is a good thing - actually i initially i thought it was a bug and tried to dig in the code to see why it happens, which is how i saw the comment about it actually being intentional.

IMO the two lines look bad visually (i noticed them in the SVN version and thought they were just a temporary bug that someone certainly will notice and fix so i didn't mentioned them here) since in many themes the divider's style is already made of two lines forming a relief. I think that if something has to be shown there, it should be a single centered line with bigger padding, which is at least visually distinct from the separator. But in addition to that, changing this behavior loses the previous ability for adding empty space between the buttons (it can be "hacked" by adding a disabled button without label or icon... but imo it is an ugly hack), so an extra style for empty space should be added.

Alternatively restoring the previous behavior with an option in the TToolbar to show separators in flat styled toolbar could be added (although i'd suggest to avoid the double separators, they really look ugly in my opinion :-P).

El 13/01/14 18:34, Mattias Gaertner ha escrit:

The Lazarus team would like to announce the second Release Candidate for the upcoming Version 1.2.

...

I don't know if it's a known problem or it has already been reported, but even with the option "Always build (even if nothing changed)" unchecked, every time I try to run it recompiles and relinks. These are the messages (hidden and shown) in the messages window:

(under windows)

Hint: Start of reading config file C:\FPC\2.6.2\bin\i386-Win32\fpc.cfg Hint: End of reading config file C:\FPC\2.6.2\bin\i386-Win32\fpc.cfg Free Pascal Compiler version 2.6.2 [2013/02/12] for i386 Copyright (c) 1993-2012 by Florian Klaempfl and others Target OS: Win32 for i386
Compiling project1.lpr
project1.lpr(10,10) Hint: Unit "nodavelib" not used in project1 project1.lpr(10,21) Hint: Unit "synapse" not used in project1 project1.lpr(10,48) Hint: Unit "datos" not used in project1 Compiling resource
D:\1354_vision_dot\programas_pc\test_plc\lib\i386-win32\project1.or Linking project1.exe
20 lines compiled, 5.3 sec , 1420768 bytes code, 379340 bytes data 5 hint(s) issued
Project "project1" successfully built

(under linux)

Hint: Start of reading config file /etc/fpc.cfg
Hint: End of reading config file /etc/fpc.cfg
Free Pascal Compiler version 2.6.2 [2013/07/06] for x86_64 Copyright (c) 1993-2012 by Florian Klaempfl and others Target OS: Linux for x86-64
Compiling project1.lpr
project1.lpr(10,10) Hint: Unit "nodavelib" not used in project1 project1.lpr(10,21) Hint: Unit "synapse" not used in project1 project1.lpr(10,48) Hint: Unit "datos" not used in project1 Compiling resource
/home/luca/Datos/1354_vision_dot/programas_pc/test_plc/lib/x86_64-linux/project1.or Linking project1
/usr/bin/ld: aviso: link.res contiene secciones de salida. ?Olvid? -T? 20 lines compiled, 1.4 sec
5 hint(s) issued
Project "project1" successfully built

Bye

Please create a bug report.

(under windows) Hint: Start of reading config file C:\FPC\2.6.2\bin\i386-Win32\fpc.cfg Hint: End of reading config file C:\FPC\2.6.2\bin\i386-Win32\fpc.cfg

Please start the IDE with the command line
parameter --debug-log=log.txt. This will log why it recompiles.

Mattias

El 13/02/14 19:22, Mattias Gaertner ha escrit:

Please create a bug report.

Fist I want to be sure is not a PEBKAC ;-)

TBuildManager.DoCheckIfProjectNeedsCompilation icon has changed Project "/home/luca/Datos/1354_vision_dot/programas_pc/test_plc/project1.ico"

don't know why (I didn't change it but the date changes every time I try to run the project).

Bye

Fixed. Please test.

Mattias

El 14/02/14 00:21, Mattias Gaertner ha escrit:

It works, thank you!
(Note that I just took ide/buildmanager.pas and ide/projecticon.pas from svn revision 44062).

Bye