Can't link against libgnuradio-core (cmake)

Greetings,

I’m trying to rebuild my gr-fcd block
(https://github.com/csete/gr-fcd) with gnuradio v3.5.0rc0-1-g037c5f60
When I build gnuradio using the autotools everything is fine and I can
build gr-fcd without problems.
When I build using cmake gnuradio still builds and install fine, but
when I try to build gr-fcd I get:

libtool: link:
/opt/gnuradio/v3.5.0rc0-1-g037c5f60/lib/libgnuradio-core.la' is not a valid libtool archive make[3]: *** [libgnuradio-fcd.la] Error 1 make[3]: Leaving directory/home/alexc/gnuradio/gr-fcd.git/lib’
make[2]: *** [all] Error 2
make[2]: Leaving directory /home/alexc/gnuradio/gr-fcd.git/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory/home/alexc/gnuradio/gr-fcd.git’
make: *** [all] Error 2

Looking at the contents of gnuradio-core.la from the two builds I can
indeed see many differences, actually they seem to be more different
than similar.

Alex

On 10/31/2011 01:50 PM, Alexandru C. wrote:

is not a valid libtool archive
than similar.

Basically, the build system is generating .la files for each library
using this macro: http://www.vtk.org/Wiki/CMakeMacroLibtoolFile
I dont know why we are doing this or why we want it.

If you link against libraries in the normal way, everything should be
fine. So my best guess is that the generated la files are confusing for
autotools.

Try deleting the la files. You can also turn the generation off w/
-DLIBRARY_EXTRAS=OFF

-Josh

On Mon, Oct 31, 2011 at 11:44 PM, Josh B. [email protected] wrote:

Looking at the contents of gnuradio-core.la from the two builds I can
autotools.

Try deleting the la files. You can also turn the generation off w/
-DLIBRARY_EXTRAS=OFF

Thanks for the tip! Using -DLIBRARY_EXTRAS=OFF works :slight_smile:

Alex

On Mon, Oct 31, 2011 at 15:44, Josh B. [email protected] wrote:

You’re right, I don’t think the .la files are necessary for linking
against
when using cmake.

Johnathan

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs