discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] build gnuradio without volk module


From: Arturo Rinaldi
Subject: Re: [Discuss-gnuradio] build gnuradio without volk module
Date: Thu, 15 Mar 2012 16:11:44 +0100
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0

Nella citazione in data Thu Mar 15 03:07:49 2012, Tom Rondeau ha scritto:
On Wed, Mar 14, 2012 at 8:49 PM, Johnathan Corgan
<address@hidden <mailto:address@hidden>>
wrote:

    On Wed, Mar 14, 2012 at 17:41, Josh Blum <address@hidden
    <mailto:address@hidden>> wrote:

    > Is this the official github for gnuradio?
    > https://github.com/gnuradio/gnuradio/tags
    >
    > Any chance we could get tags pushed there as well (maybe
    automated)? It
    > would be super easy to link to source tarballs that way.

    Tom is setting up this github repo to automatically mirror the
    contents of gnuradio.org <http://gnuradio.org>'s repo, but the
    work isn't complete, and the
    repo itself doesn't have everything in it (like the tags, as you
    noticed.)

    He and I are working out some security issues with the automation, but
    maybe we can do a manual push of the tags there.

    Johnathan



Yes, we should definitely push the tags. Have done that manually for now.

Arturo,

My suggestion would be to use either the github gnuradio account or
gnuradio.org <http://gnuradio.org>'s git repo. Clone the repo and then
checkout tag v3.5.2. This tag is equivalent to the tarball release
except that it will contain the cmake files to build that way. Here's
the link to the tarball for the v3.5.2 tag on github:

https://github.com/gnuradio/gnuradio/zipball/v3.5.2

One thing to note, though, is that with this, you a) get everything in
the repo and b) don't have some generated stuff that normally goes
into the release tarballs. Issue a shouldn't affect you. For issue b,
you will just have to remember to run ./bootstrap before running
./configure.

As of 3.5.2, we've started using Volk inside of gnuradio-core blocks,
so it has become a requirement, not just an option, so disabling volk
should disable gnuradio-core, too. If that's not happening, I'll fix it.

We will be releasing a 3.5.3 (possibly soon) to fix some other issues
that have recently come up. Due to the autotools issue with volk, we
will try to include the cmake build files in this release, though.

Tom



_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

thx very much to all of you. I look forward to work with the 3.5.3 official tarball.

Regards, Arturo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]