Friday, August 2, 2019

Re: [Discuss-gnuradio] [announcement] GNU Radio 3.8 Release Candidate 2

You should run:

git pull origin master

Then you should see a v3.8.0.0.-rc2 tag when you run:

git tag -l

Then you can checkout the branch, and run the submodule update to update the volk module.



On Fri, Aug 2, 2019 at 7:24 AM Barry Duggan <barry@dcsmail.net> wrote:
Thanks Nate.

The two lines I wasn't clear about were:
- git checkout v3.8.0.0-rc2
- git submodule update

Since I already have a clone of rc1, I assume I can just start with 'cd
gnuradio'. Right?
'git status' says I am up to date with 'origin/master'.

Best wishes,
---
Barry Duggan


On 2019-08-02 09:55, Nate Temple wrote:
> Hi Barry,
>
> You should use git in the command line:
>
> git clone --recursive https://github.com/gnuradio/gnuradio
> cd gnuradio
> git checkout v3.8.0.0-rc2
> git submodule update
> mkdir build
> cd build
> cmake ..
> make
> sudo make install
>
>
> Regards,
> Nate Temple
>
> On Fri, Aug 2, 2019 at 6:41 AM Barry Duggan <barry@dcsmail.net> wrote:
>
>> I should have put "Re:" on the subject.
>>
>> ---
>> Barry Duggan
>>
>>
>> -------- Original Message --------
>> Subject: [Discuss-gnuradio] [announcement] GNU Radio 3.8 Release
>> Candidate 2
>> Date: 2019-08-02 08:00
>>  From: Barry Duggan <barry@dcsmail.net>
>> To: Müller, Marcus (CEL) <mueller@kit.edu>
>> Cc: Discuss Gnuradio <discuss-gnuradio@gnu.org>
>>
>> Hi Marcus,
>>
>> I am planning on upgrading from rc1 to rc2, but (as a git newbie) I
>> don't know how to do it with git. Obviously I could get the source
>> zip,
>> but that would lose the git tracking functionality.
>>
>> What is the 'proper' way to do it?
>>
>> Best regards,
>> --
>> Barry Duggan
>>
>> On Sat, 20 Jul 2019 22:30:18 +0200, Marcus wrote:
>>
>> You'll find the release on
>>
>> https://github.com/gnuradio/gnuradio/releases/tag/v3.8.0.0-rc2
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>

No comments:

Post a Comment