I’ve Installed itpp via MacPorts too.

Actually I've solved this library problem by adding ITPP_LIBRARIES to 
target_link_libraries in lib/CMakeLists.

However, I got another issue.

Although ofdm_parse_payload block (from the OOT module) is well recognized in 
gnuradio (in GUI app. as shown in the figure),

it gives me an error when I try to execute it:
self.wifirecv_ofdm_parse_payload_1 = wifirecv.ofdm_parse_payload('')
AttributeError: module 'wifirecv' has no attribute ‘ofdm_parse_payload’) 

Can I get any help?

Best,


> 2021. 3. 15. 오후 7:51, Marcus Müller <mmuel...@gnuradio.org> 작성:
> 
> Sadly, it's really the issue as shown by your output that your linker can't 
> find the itpp
> library. Since you've said you've installed it, please check whether it's 
> installed where
> your toolchain expects it. *how* you've installed it, specifically, might be 
> helpful. Was
> it also using macports?
> 
> Best regards,
> Marcus
> 
> On 15.03.21 03:22, Louis Jung wrote:
>> Thank you for your reply!
>> 
>> Actually I’ve installed itpp and itpp-dev (command was different, cause I’m 
>> using Mac),
>> but it showed the same error..
>> 
>> I think there is another issue.
>> 
>>> 2021. 3. 10. 오후 7:56, Andi Kita <ak...@qmail.qcc.edu 
>>> <mailto:ak...@qmail.qcc.edu>> 작성:
>>> 
>>> sudo apt-get install libitpp-dev
>>> 
>>> On Tue, Mar 9, 2021, 9:05 PM Louis Jung <insom...@asleep.ai 
>>> <mailto:insom...@asleep.ai>>
>>> wrote:
>>> 
>>>    Hello,
>>> 
>>>    I’m currently trying to port ‘gr-csitool’ 
>>> (https://github.com/qiank10/gr-csitool
>>>    <https://github.com/qiank10/gr-csitool>) from gnuradio v3.7 to v3.8 in 
>>> OS X.
>>> 
>>>    I’ve installed gnuradio via MacPorts.
>>> 
>>>    While I’ve followed instruction from
>>>    
>>> 'https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide’
>>>    
>>> <https://wiki.gnuradio.org/index.php/GNU_Radio_3.8_OOT_Module_Porting_Guide%E2%80%99>,
>>>    I got a problem while linking (I think).
>>> 
>>>    Since gr-csitool requires ‘itpp’ library, I’ve installed and trying to 
>>> include it to
>>>    OOT modules, but it seems not working.
>>> 
>>>    In lib/CMakeLists.txt, I added 'target_link_libraries(gnuradio-csitool
>>>    gnuradio::gnuradio-runtime gnuradio::gnuradio-blocks 
>>> gnuradio::gnuradio-fft
>>>    gnuradio::gnuradio-filter Volk::volk itpp)’
>>> 
>>>    Then, while making, it shows linker failure as below:
>>>    *Scanning dependencies of target gnuradio-csitool*
>>>    [  8%] Building CXX object
>>>    lib/CMakeFiles/gnuradio-csitool.dir/ofdm_sync_and_decode_header_impl.cc.o
>>>    [ 16%] Building CXX object
>>>    
>>> lib/CMakeFiles/gnuradio-csitool.dir/ofdm_sync_and_decode_header_history_impl.cc.o
>>>    [ 25%] Building CXX object
>>>    lib/CMakeFiles/gnuradio-csitool.dir/ofdm_equalize_symbols_impl.cc.o
>>>    [ 33%] Building CXX object
>>>    
>>> lib/CMakeFiles/gnuradio-csitool.dir/ofdm_equalize_symbol_simpledfe_impl.cc.o
>>>    [ 41%] *Linking CXX shared library libgnuradio-csitool.dylib*
>>>    ld: library not found for -litpp
>>>    clang: *error: *linker command failed with exit code 1 (use -v to see 
>>> invocation)
>>>    make[2]: *** [lib/libgnuradio-csitool.v1.0-compat-xxx-xunknown.dylib] 
>>> Error 1
>>>    make[1]: *** [lib/CMakeFiles/gnuradio-csitool.dir/all] Error 2
>>>    make: *** [all] Error 2
>>> 
>>>    Here is my cmake command (if neededd)
>>>    CC=/usr/bin/llvm-gcc CXX=/usr/bin/llvm-g++ cmake \
>>>    
>>> -DPYTHON_EXECUTABLE=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7
>>>    \
>>>    
>>> -DPYTHON_INCLUDE_DIR=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/Headers
>>>    \
>>>    
>>> -DPYTHON_LIBRARY=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python
>>>  \
>>>    -DSPHINX_EXECUTABLE=/opt/local/bin/rst2html-3.7.py 
>>> <http://rst2html-3.7.py/> \
>>>    
>>> -DGR_PYTHON_DIR=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages
>>>    \
>>>    -DCMAKE_INSTALL_PREFIX=/opt/local ..
>>> 
>>>    Can I have any hint?
>>> 
>>>    Thanks a lot!
>>> 
>> 
> 

Reply via email to