[Lazarus] lazbuild build IDE profiles

[waldo kitty]

On 3/20/2012 04:26, Mattias Gaertner wrote:
> On Mon, 19 Mar 2012 23:50:49 -0400
> waldo kitty<wkitty42 at windstream.net>  wrote:
>
>> [...]
>>> Maybe you mean tools/svn2revisioninc.lpi or perhaps ide/revision.inc.
>>
>> yes... as i wrote before, it would be very nice to be able to have the "copy"
>> lines above read as
>>
>>     copy /q lazarus.exe lazarus-debug_r%svnversion%.exe
>>
>> where "svnversion" is an environment variable set by the make process that
>> includes updating the above file(s)...
>
> Maybe you can use the file ide\revision.inc to do that.

i've thought about that but have no way to parse it via plain old .bat syntax... 
if i were running something like 4DOS/4OS2/4NT then i would be able to do this 
but w2k (or vista) doesn't have this capability built in AFAIK...

in 4DOS style, it would be something like

   set lazrvsn=%@field["'",1,%@line[ide\revision.inc,1]]

which pulls the first '' delimited field from the second (oneth) line in the 
file eliminating the single quotes and the semicolon resulting in

   set lazrvsn=35963

but i can't do this in plain old .bat syntax and don't want or need to go thru 
the convolutions to get 4NT installed nor do i want to futz about trying to get 
a perl or some such installed... space is very limited on /this/ machine but the 
environment i duplicate on others...

so possibly svn2revisioninc could set this in the original environment? i know 
it used to take a trick or two to do this in the past... i've still got old TP6 
code around here that does this ;)

one might also preset that var with X number of characters and svn2revisioninc 
could alter it in the original environment... that was one easier trick because 
allocating space in the original environment to create a new variable was 
slightly harder to do and i don't know if it is even possible any more in these 
new environments...

then again, it might be easiest to just generate a ide/setlazrevision.bat that 
is called... if i were doing it, i would keep the environment variable's name to 
8 characters or less and start it with laz so as to keep it separate from the 
possible fpc variable of the same nature :P

i envision being able to have multiple laz compiled with multiple fpc each in 
own directory with own paths... i can currently do multiple fpc but not multiple 
laz... that's coming up "soonish" ;)