macro that returns the lazarus/lcl version

[taazz]

OK the problem is that you guys release faster than I test or install. Good for you but I end up with multiple installations until I get thinks going at this time I have two 1.0.14 and 1.2.0 the problem starts when I try to install the 3rd party component to one of my installations they overwrite the existing ppus making switching from one version to an other a bit slower to get up to speed. I was thinking to editing all the packages and adding something like $(FPCVer) in the output path bat since most of your releases use the same fpc this wouldn't help at all.


So is there a way to retrieve the lazarus version similar to $(FPCVer) to be used in paths?

[Mike.Cornflake]

Brilliant idea, and will help me tidy my projects as well.

I've had a look on the wiki, and briefly in the code.   I can't see anything.

[BigChimp]

From my notes: it's at least available for the LCL version; can't seem to find a reference on the wiki
  similr lcl_fullversion for lazarus (needs LCLVersion in uses clause) (better than lcl_major and lcl_minor)
   {$IF LCL_FULLVERSION>=1000000} //for laz 1.0.0.0 (major,minor,release,patch)
   {$IF LCL_FULLVERSION>=1000200} //for laz 1.0.2.0

[Mike.Cornflake]

   {$IF LCL_FULLVERSION>=1000000} //for laz 1.0.0.0 (major,minor,release,patch)
   {$IF LCL_FULLVERSION>=1000200} //for laz 1.0.2.0

That's in Code.   @Taazz is talking about IDE Macros.  Well, I assume that's what @Taazz is taking about.  We all know assumption makes an "ASS out of U and MPTION".  Wait, that doesn't sound right...

Either way, this is what I think the topic is about
http://wiki.lazarus.freepascal.org/IDE_Macros_in_paths_and_filenames

UPDATE: I particularly like the idea of using this for all those little bugtracker demo's.  Keep each build separate....

[BrunoK]

Would :

procedure TfmAccelChar.FormShow(Sender: TObject);
begin
  Caption := Caption + ' [FPC ' +
{$I %FPCVERSION%}
    +'/Laz ' +
{$I version.inc}
    +']';

That gives :
Caption='fmAccelChar [FPC 2.6.4/Laz 1.2.0]'

Be useful ?

[Mike.Cornflake]

Would :

procedure TfmAccelChar.FormShow(Sender: TObject);
begin
  Caption := Caption + ' [FPC ' +
{$I %FPCVERSION%}
    +'/Laz ' +
{$I version.inc}
    +']';

That gives :
Caption='fmAccelChar [FPC 2.6.4/Laz 1.2.0]'

Be useful ?

I don't think so, I think we're talking about "Project" - "Options" - "Paths".   Have a look at the screenshot I've added here.  See I'm using $(TestDir), $(TargetCPU) etc.  Taazz is asking if there is a %(LAZVer) equivalent.

[BigChimp]

   {$IF LCL_FULLVERSION>=1000000} //for laz 1.0.0.0 (major,minor,release,patch)
   {$IF LCL_FULLVERSION>=1000200} //for laz 1.0.2.0

That's in Code.   @Taazz is talking about IDE Macros.

Sure, but LCL_FULLVERSION is a macro, conditional define or whatever it is (as you see I'm not clear on the distinctions). So perhaps it can be used as an IDE macro like its FPC equivalent.

[Mike.Cornflake]

I've had a look in the code (for 1.2.2, I don't have trunk with me).  buildmanager.pas has a series of functions, one for each of IDE Macros defined in that wiki page.  Nothing there for Lazarus version. 

Doesn't look too hard to extend though, a string constant needs defining (elsewhere) and a matching function needs implementing and registering against the string.  Looks like a simple design - I like those...  I might have a play tonight and submit a patch.  Though there will be a new String that needs a translation creating for it.  That's the only bit I'm nervous about.  Don't want to a add a string that breaks other translations if there is no translation - really not sure how that side of life works...   I'll play though :-)

Mind you, there still might be a way with the existing macros and functions.  Just because I can't see it, don't mean it aint there :-)

LCL_FULLVERSION is a macro, conditional define or whatever it is (as you see I'm not clear on the distinctions)

I suspect the correct term is "hack" :-)

UPDATE: Forgot - dinner plans tonight :-(   I'll play with the code over the weekend...

[taazz]

As mike already said I'm interesting exclusively on IDE Macros and since we or subject how about extending those to allow me to add my own static macros as well eg I could add a macro named projects or components or what ever I need for that matter this ofcourse will be static for now or have a pascal script attach to it?

[Mike.Cornflake]

Good golly.  I got $(LAZVer) working in 4 to 5 lines of code (depending on whether you count an if then else as three or four lines).  I had half an hour free before dinner and it was really was as easy as a first glance at the code suggested.  Mind you, I've got a lot of testing to do before I submit the patch, and I want to see if I can add a $(SVNRevision) as well.

since we or subject how about extending those to allow me to add my own static macros as well

or have a pascal script attach to it?

I'll leave that to my betters :-)   For now I'll see how I go with my first IDE patch.

Mind you, after a quick think - if you want to go down the pascal script side of things wouldn't a makefile be a better solution for you?  I vaguely remember discussion of fpmake being either developed, or rewritten, or, you know, something.  Not my world I'm afraid...

[taazz]

Good golly.  I got $(LAZVer) working in 4 to 5 lines of code (depending on whether you count an if then else as three or four lines).  I had half an hour free before dinner and it was really was as easy as a first glance at the code suggested.  Mind you, I've got a lot of testing to do before I submit the patch, and I want to see if I can add a $(SVNRevision) as well.

since we or subject how about extending those to allow me to add my own static macros as well

or have a pascal script attach to it?

I'll leave that to my betters :-)   For now I'll see how I go with my first IDE patch.

Mind you, after a quick think - if you want to go down the pascal script side of things wouldn't a makefile be a better solution for you?  I vaguely remember discussion of fpmake being either developed, or rewritten, or, you know, something.  Not my world I'm afraid...

I'm a borlander we borlanders never learned or needed the use of make make files and all that barbaric command line interfaces and options. Those are shameful memories of the past we are not going back to such a barbaric era ever again give me death or give me a smashing IDE and all that 

[Mike.Cornflake]

Those are shameful memories of the past

What?!  That's the bit you took from my glorious post about my first ever IDE mod going unexpectedly well?!?  Particularly with those mods being in the direction you personally were enquiring about?  For shame... 

Seriously though, I personally agree - never liked Makefiles.  I'll need to mull it over but right now I just can't picture how Pascal Scripts embedded within a part of the UI only are going to be any less evil though.

[Mike.Cornflake]

Darned :-(   I've mulled it over.  There's already a PascalScript mechanism for build time.  Project Options - Other.  You want to be able to declare variables or functions here somehow and access them as $(XXX) elsewhere....

I'll play, but I'm not promising anything.  Let's see how I go with the easier stuff first...  This honestly might need to be handed over to the grownups....

[taazz]

Those are shameful memories of the past

What?!  That's the bit you took from my glorious post about my first ever IDE mod going unexpectedly well?!?  Particularly with those mods being in the direction you personally were enquiring about?  For shame... 

Seriously though, I personally agree - never liked Makefiles.  I'll need to mull it over but right now I just can't picture how Pascal Scripts embedded within a part of the UI only are going to be any less evil though.

well it will enable me to add extra dynamic macros that will return the loged in user the users temp folder or any other special interest folder. this will enable me to have single installation for multiple users instead of one installation per user that is now.

It doesn't have to be pascal script you know as long as I can register my own functions and names through a package I could do the same and for god sake I do not mean that you should implement it the only thing I said was that now that I'm thinking about macros it would be good to have all or part of the above just an idea nothing more.

[Mike.Cornflake]

it will enable me to add extra dynamic macros that will return the loged in user the users temp folder or any other special interest folder.

Been too long since I played with Delphi - can't remember this being a feature, or how it would have been implemented...  Sounds useful though.

Darned :-(   I've mulled it over.

This bit wasn't serious.  One of those dry humour things that loses translation without the body language or tone to help convey it...

for god sake I do not mean that you should implement it

And I never said I would, only that I would play.  I'll be honest, I'm intrigued by the whole concept (of expanding the IDE), and would genuinely love to play with this code...