Re: problem building gr-howto-write-a-block-cmake

Success!

Everything works fine as long as I make the following change on the top
CMakeLists.txt file in gr-howto-write-a-block-cmake
from
project(gr-howto-write-a-block CXX)
to
project(gr-howto-write-a-block CXX C)

Cmake is now finding the PythonLibs at:
/usr/lib64/libpython2.7.so

I have no idea why this works…

Also note that the sample project directories generated by the
gr_modtool.py
script produce CMakeLists.txt files with the former declaration of
“project”
and thus do not work for me without the above modification.

thanks everyone for the help,
Achilleas

On 03/20/2012 03:02 PM, Achilleas A. wrote:

/usr/lib64/libpython2.7.so

I have no idea why this works…

Hah, I thought of this to myself and said no way… Good find.

The check for python libs (in the version you have) may be using one of
the macros that uses a C compiler. The call: enable_language© would
also be an equivalent to this.

-josh

On Tue, Mar 20, 2012 at 6:05 PM, Josh B. [email protected] wrote:

project(gr-howto-write-a-block CXX C)
the macros that uses a C compiler. The call: enable_language© would
also be an equivalent to this.

-josh

Achilleas,

Good catch! I just updated master and next with this fix.

Thanks!

Tom

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