LCL For Win32 GTK2 take 2

[Leledumbo]

One last question is there any lcl as well as fpc version define I can use in my code if needed?

lcl: http://wiki.lazarus.freepascal.org/Lazarus_0.9.26_release_notes#LCL_major_changes (it's not a define though, but rather a constant)
fpc: FPC_FULLVERSION. For 2.6.0 -> 20600

[JuhaManninen]

1st impression :
The build configuration dialog is for advanced users only on this build, no easy way to select what you want remembering all those command line params isn't going to float well with me.

So what do you want to select then?
The new dialog is simpler than the previous one. Most notably you don't need to select different things (like LCL) to build because it happens automatically now. You don't need command line params any more than before.

Building of Examples was in a wrong place anyway IMO and I replaced it with Tools -> Example Projects ...
The controls got reorganized but they are not more complex in any way.

A few flicker problems are not present any more.

Good. I told you to use a recent version!

Juha

[Martin_fr]

If you update your Lazarus, then add EnableLibOverlay to the defines and enable it.

Or Lazarus may not start.

[taazz]

So what do you want to select then?

Simple answer, everything that I can.

The problem with the new dialog  is that I don't know what I can

Most important in my situation is to be able to build every single package by hand and then build the IDE to use them with out rebuilding them.

This is important because the laptop I'm working on has heating problems and shuts down when is over heated if I can't break the process up to smaller more manageable steps I'll not be able to actually do any installation after a number of packages.

The new dialog is simpler than the previous one. Most notably you don't need to select different things (like LCL) to build because it happens automatically now. You don't need command line params any more than before.

Agreed, its so simple that it needs an expert to know what and how to set it up.

Just a Noob's perspective though as I get more experience I might even prefer the new dialog than the old one, until then....

Building of Examples was in a wrong place anyway IMO and I replaced it with Tools -> Example Projects ...
The controls got reorganized but they are not more complex in any way.

That was the 1st that got disabled after I failed to install a few packages (over heating problem) and I do agree examples do not belong in that dialog at all.
A menu entry might be nice for testers but its not required for every day use and it can easily be added as an external tool on the tools menu I think.

If you update your Lazarus, then add EnableLibOverlay to the defines and enable it.

Or Lazarus may not start.

Thank you I noted that down.

Edit :

One last question is there any lcl as well as fpc version define I can use in my code if needed?

lcl: http://wiki.lazarus.freepascal.org/Lazarus_0.9.26_release_notes#LCL_major_changes (it's not a define though, but rather a constant)
fpc: FPC_FULLVERSION. For 2.6.0 -> 20600

Thats something but you should consider adding some defines for fpc as well as for lazarus to make it easier for component writers to support multiple versions and stop all this requirements of getting the latest svn - snapshot build in order to use a package.

Thank you all for your valuable inside and time it is very much appreciated.

[marcov]

One last question is there any lcl as well as fpc version define I can use in my code if needed?

for FPC: fpcfullversion, see http://www.freepascal.org/docs-html/user/userse18.html

[JuhaManninen]

Simple answer, everything that I can.
The problem with the new dialog  is that I don't know what I can
Most important in my situation is to be able to build every single package by hand and then build the IDE to use them with out rebuilding them.

Experts CAN add many defines and compiler options, true, but you don't have to.
In the earlier version sometimes you had to tweak with building LCL first and the rest later, but not any more. It all happens automatically now.

When a package is built once for certain flags and architecture etc., it will be reused for all projects using it with the same settings.
The logic behind it is automatic, you don't need to worry about it.

This is important because the laptop I'm working on has heating problems and shuts down when is over heated if I can't break the process up to smaller more manageable steps I'll not be able to actually do any installation after a number of packages.

Uhhh! Ok, I can see 2 possible solutions for you:
1. Put your laptop into a deep freezer for a while always before building Lazarus.
2. Get a computer that can build Lazarus without overheating.

Juha

[Martin_fr]

This is important because the laptop I'm working on has heating problems and shuts down when is over heated if I can't break the process up to smaller more manageable steps I'll not be able to actually do any installation after a number of packages.

1) You can open individual packages, and compile them one by one

2) Start compilation, watch temperature "run" menu has a "abort build". If you have NOT selected "clean all" then next build will pick up where you were.