Marcus and Andrej,
Based on the information from:
https://stackoverflow.com/questions/1242904/finding-python-site-packages-directory-with-cmake
I modified GrPython.cmake by adding a new variable, PYTHON_SITE:
# Sets the pytho
A-Ha! So, that leads us the next bigger question: How can we make
GR_PYTHON_DIR a relative path? I'm taking Andrej into CC, because he
did a lot of the actual "modern CMake" conversion and is back home :)
Best regards,
Marcus
On Tue, 2019-05-21 at 14:34 -0400, Toby Flynn wrote:
> Marcus,
> I thi
Marcus,
I think I have found the issue, just not a correct solution yet. Based
on the bug report:
https://cmake.org/Bug/print_bug_page.php?bug_id=14367
Which is marked as not a bug, but explains the issue I am seeing very
well.
gnuradio-runtime.swig/CMakeLists.txt uses an absolute path for the
Marcus,
I think have tracked down the root of the issue, I still do not have a
fix. CMake cmExportFileGenerator.cxx,starting at line 318 prefixItems,
appears to be seeing the installed path for the files as an absolute path.
it is not seeing the sysroot information from the system to know the f
Marcus,
The last file differences I sent are in a file created from
CMakeLists.txt, lines 74-78. Swig builds with no issues, it is when I link
an OOT that the file _runtime_swig.so cannot be found because the
runtime_swigTargets-release.cmake file has the wrong directory location,
somehow it lo
Marcus,
I have tracked this up one more file. The file:
build/gnuradio-runtime/swig/CMakeFiles/Export/lib/cmake/gnuradio/runtime_swigTargets.cmake
on the host system has lines starting around line 44:
# Compute the installation prefix relative to this file.
get_filename_component(_IMPORT_PREFI
Hi Toby,
I don't really doubt it's a CMake issue; to be precise, I think it's an
issue in the triangle between CMake, CMake instructing SWIG and
detecting the right Python libs along the way.
Anyway, I'll take a minute to literally parse your email :)
Thanks!
Marcus
On Mon, 2019-05-20 at 09:09
Marcus,
I think what you want to see if the configuration for CMake, the actual
build line is fairly normal. This is the contents of the file which
configures CMake. I believe this is a CMake issue, not a Python issue.
It is only the creation of one .cmake file which leads to OOT building
err
Marcus,
Thank you for the quick reply. I cannot get to the computer with the
full Yocto command until maybe Monday, I will send a response with that
command when I can get to the computer.
I believe the issue is with CMake and not Python. CMake makes the file
'build/gnuradio-runtime/swig/CM
Hi Toby,
what's the verbatim cmake command line Yocto is executing?
Since it's impossible for the build system to know by itself what the
target python will be, unless you tell it which, we'll have to figure
out a way to consistently set Python used during CMake, Python used
during build, and Py
I am attempting to install OOT modules using a Yocto/Openembedded
enviroment and the latest GNURadio 3.8. This process was working before
the latest cmake changes to 3.8 were incorporated. I am now having issues
with the cross-complitaion. I have tracked the issue down to a file I
believe is cre
11 matches
Mail list logo
