Buil number as part of compiled binary file name

[srnec]

Hello, is it there a possibility to have build number included in file name or path? I searched in IDE macros and others settings but found nothing.

[Thaddy]

The version info dialog in Lazarus

[srnec]

The version info dialog in Lazarus

"The version info dialog" includes version info in compiled file itself, I am looking for build number in file name.

In the Project Options
Compiler - Paths - Target File name:
and use somethink like lib/myBinary-$(BuildNo)

[dbannon]

Lazarus will run a command or script after the compile

Code: Bash  [Select][+][-]

1. $> mv project1 project1-b343

Er, Windows, its 'rename' perhaps ?

Davo

[cdbc]

Hi
You can set the 'Target-filename' in 'Project' -> 'Options' -> 'Paths'
See the attached screen-shot...
Regards Benny

[MarkMLl]

But as far as I can see there isn't an IDE macro which expands to the build number, so it can't be automated by either setting a target filename or by renaming after the build (without having an external program which reads the build version from the binary then renames it appropriately).

MarkMLl

[n7800]

There is no such macro, but it was added to trunk. It will be released in Lazarus 5.0.

[440bx]

There is no such macro, but it was added to trunk. It will be released in Lazarus 5.0.

I am under the impression that the macro you are referring to returns Lazarus IDE information.  Is this correct ?

Also, I am under the impression that what the OP is asking for is to be able to use the _applicaton's_ build information (like what's stored in the Windows version info.)  If this is correct then the Lazarus macro you referred to does not apply.

Are either one of these impressions incorrect ?

[Thaddy]

Yes, it is info about lazarus itself, not info about your own compiled binaries and that is what is asked.
The way to do that is to use two of the tips mentioned above:
1. Use the version info dialog
2. Extract the build info into a string and add that to the executable name by using mv or rename.

There are some other ways to achieve that. Have to check if these still work.

[n7800]

It's sad to hear this, because I spent a lot of time writing the description and example of use... ((

The very first line says:

Adds a macro to the IDE that returns the project version number.

The last section "$LazVer() macro" (this is already a macro for the IDE version) says:

For consistency, the second commit adds the same optional parameters to the $LazVer() macro.

So, I added a macro for the project. And additionally added parameters for the IDE macro (which already exists, but has no parameters).

EDIT: Even the title also says:

IDE: Added IDE macro ProjVer to get project version. Issue #23198

[440bx]

It's sad to hear this, because I spent a lot of time writing the description and example of use...

Even if the macro you implemented doesn't solve the OP's problem, there is a good chance it will be useful to other people.

IOW, don't be sad, it is very likely to be useful.

[alpine]

1. Use the version info dialog
2. Extract the build info into a string and add that to the executable name by using mv or rename.

wmic can be used on Window$. Put that in a filever.cmd file:

Code: Text  [Select][+][-]

1. @echo off
2. rem display file version of an executable file
3.  
4.     setlocal enableextensions
5.  
6.     rem fully expand the file name
7.     set "file=%~dp1%~nx1"
8.        
9.     if not defined file goto :eof
10.     if not exist "%file%" goto :eof
11.  
12.     rem use wmic to get file version in %vers%
13.     set "vers="
14.     for /F "tokens=2 delims==" %%g in ('
15.         wmic datafile where name^="%file:\=\\%" get Version /value
16.     ') do set "vers=%%g"
17.  
18.     if not "%vers%"=="" echo %vers%
19.  
20.     endlocal

Then: filever.cmd somefile.exe

will output something like:

Code: Text  [Select][+][-]

1. 7.14.0.3804

Don't know for Linux.

[Thaddy]

The way I proposed is cross-platform.

You can also do it manually by specifying the -o<version> option.
If you use a version control system like git or svn for your own sources, the version should be easy to script.

[JuhaManninen]

Even if the macro you implemented doesn't solve the OP's problem, there is a good chance it will be useful to other people.

Why wouldn't the $ProjVer() macro solve this problem? It looks like a perfect match to me.
The "Target file name (-o)" field in Project Options supports macros AFAIK.

[srnec]

For me, the $ProjVer(build) looks like perfect solution. Clean and multiplatform.
There is possibility to extract "<BuildNr Value="xxx"/>" from .lpi file and rename compiled binary, but use of macro is more straightforward. I think adding new macro to IDE is useful also other purposes.