Re: Version info

Thanks for the info.
I see the wrong version info depends on git describe which depends on a
correct tagging.

As every branch has it's own version info, why don't we use

git rev-parse --short HEAD instead of git describe to get the commit hash ?

So we would be independent of missing tags.

-- Volker


> I filed an issue for this.
>
> https://github.com/gnuradio/gnuradio/issues/4059
>
> Ron
>
> On 1/15/21 08:58, Jeff Long wrote:
>> The v3.8.0.0 part is incorrect, but commit be21c299 shows you built a
>> recent master. There is no 3.9 or 3.10 tag yet, so everything shows up
>> as 3.8.
>>
>> On Fri, Jan 15, 2021 at 11:46 AM Volker Schroer <dl1ksv@gmx.de
>> <mailto:dl1ksv@gmx.de>> wrote:
>>
>> Hi,
>> I just build a fresh version of gnuradio from latest git master
>> branch.
>> After running cmake I get:
>>
>> Building for version: v3.8.0.0-891-gc4b33434 / 3.10.0git
>>
>> and after building I get
>>
>> gnuradio-config-info -v
>> v3.8.0.0-879-gbe21c299
>>
>> What does v3.8 means at that point. I'd expected at least 3.9 or
>> even 3.10.
>>
>> Is this an error or do I understand somehing wrong ?
>>
>> -- Thanks
>>
>> Volker
>>
>>
>>
>>
>>
>>