neumoDVB

neumodvb in Manjaro (CMake 4.0.2-1) builds with no problems when I use the basic pybind11 library - no development package is available.
Whether pybind11 in Manjaro's neumodvb causes problems is probably academic, as some issues with wxWidgets in Manjaro are still prevalent - no blindscanning or channel video using capable cards at present.
Checking my Fedora 42, CMake is using 3.31.6. there, but I still have the pybind11 problem as in Ubuntu, so perhaps I would still have the pybind11 error in Ubuntu if I updated CMake.

fc42 -

Code:
- xxx=/Adams/
-- Modern OS detected - using clang 20
CMake Error at CMakeLists.txt:79 (find_package):
  By not providing "Findpybind11.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "pybind11",
  but CMake did not find one.

  Could not find a package configuration file provided by "pybind11" with any
  of the following names:

    pybind11Config.cmake
    pybind11-config.cmake

  Add the installation prefix of "pybind11" to CMAKE_PREFIX_PATH or set
  "pybind11_DIR" to a directory containing one of the above files.  If
  "pybind11" provides a separate development package or SDK, be sure it has
  been installed.
You have not installed pybind11. Did you follow the installation procedure in the documentation? Probably not?
 
You have not installed pybind11. Did you follow the installation procedure in the documentation? Probably not?
In my Fedora 42, Pybind11-devel is empty of the necessary files, in comparison with my Fedora 39, where I have e.g. /usr/include/pybind11 and /usr/share/cmake/pybind11.

Without those files, I have no pybind11, hence I am unable to build neumodvb , at least in my version. Perhaps others using Fedora 42 have the necessary files in Pybind11-devel?
 

Attachments

  • neumodvb cmake.webp
    neumodvb cmake.webp
    36.5 KB · Views: 21
  • No file info in pybind11-devel in dnfdragora.webp
    No file info in pybind11-devel in dnfdragora.webp
    44.5 KB · Views: 21
In my Fedora 42, Pybind11-devel is empty of the necessary files
Must be in rpmlib (CompressedFileNames). I don't have the expertise to extract the necessary files, if that's what you need to do.

FR39 lists them separately in Pybind11-devel, and of course placed in their respective directories.
 
In my Fedora 42, Pybind11-devel is empty of the necessary files, in comparison with my Fedora 39, where I have e.g. /usr/include/pybind11 and /usr/share/cmake/pybind11.

Without those files, I have no pybind11, hence I am unable to build neumodvb , at least in my version. Perhaps others using Fedora 42 have the necessary files in Pybind11-devel?
Llew,
There should be no capittal P. It is pybind11-devel
 
There should be no capittal P. It is pybind11-devel
Maybe important if capitalised when searching for the package. Obviously I used pybind11-devel in dnfdragora.
 
Maybe important if capitalised when searching for the package. Obviously I used pybind11-devel in dnfdragora.
and pybind11-devel does include what is needed!
 
and pybind11-devel does include what is needed!
I know deeptho, but with pybind11-devel installed in Fedora 42, the necessary files were not present in their respective directories, namely : -

/usr/include/pybind11
/usr/lib/cmake/pybind11
/usr/share/cmake/pybind11
usr/share/doc/pybind11-devel

/usr/share/pkgconfig was the only file that pybind11-devel added.



I had to copy the files from Ubuntu :lol: This allowed me to build neumodvb with no errors.

But wait - there's a problem with spectrum scanning in that I'm not getting the peaks marked with the parameters (frequencies and SRs). I had this happen with Manjaro, but after a Manjaro and neumodvb version update there they miraculously reappeared.

Perhaps you would be kind enough to check the logs when I post them in due course?
 
I know deeptho, but with pybind11-devel installed in Fedora 42, the necessary files were not present in their respective directories, namely : -

/usr/include/pybind11
/usr/lib/cmake/pybind11
/usr/share/cmake/pybind11
usr/share/doc/pybind11-devel

/usr/share/pkgconfig was the only file that pybind11-devel added.



I had to copy the files from Ubuntu :lol: This allowed me to build neumodvb with no errors.

But wait - there's a problem with spectrum scanning in that I'm not getting the peaks marked with the parameters (frequencies and SRs). I had this happen with Manjaro, but after a Manjaro and neumodvb version update they miraculously reappeared.

Perhaps you would be kind enough to check the logs when I post them in due course?
Herewith logs and denuded spectrum.

Maybe something obvious somewhere in the logs?

Spectrum minus peak markings.webp
 

Attachments

I know deeptho, but with pybind11-devel installed in Fedora 42, the necessary files were not present in their respective directories, namely : -

/usr/include/pybind11
/usr/lib/cmake/pybind11
/usr/share/cmake/pybind11
usr/share/doc/pybind11-devel

/usr/share/pkgconfig was the only file that pybind11-devel added.



I had to copy the files from Ubuntu :lol: This allowed me to build neumodvb with no errors.

But wait - there's a problem with spectrum scanning in that I'm not getting the peaks marked with the parameters (frequencies and SRs). I had this happen with Manjaro, but after a Manjaro and neumodvb version update there they miraculously reappeared.

Perhaps you would be kind enough to check the logs when I post them in due course?
Then you must have erased the files yourself, because they are definitely in th rpm:
Code:
rpm -q -l pybind11-devel
/usr/bin/pybind11-config
/usr/include/pybind11
/usr/include/pybind11/attr.h
/usr/include/pybind11/buffer_info.h
/usr/include/pybind11/cast.h
/usr/include/pybind11/chrono.h
/usr/include/pybind11/common.h
/usr/include/pybind11/complex.h
/usr/include/pybind11/detail
/usr/include/pybind11/detail/class.h
/usr/include/pybind11/detail/common.h
/usr/include/pybind11/detail/cpp_conduit.h
/usr/include/pybind11/detail/descr.h
/usr/include/pybind11/detail/exception_translation.h
/usr/include/pybind11/detail/init.h
/usr/include/pybind11/detail/internals.h
/usr/include/pybind11/detail/type_caster_base.h
/usr/include/pybind11/detail/typeid.h
/usr/include/pybind11/detail/value_and_holder.h
/usr/include/pybind11/eigen
/usr/include/pybind11/eigen.h
/usr/include/pybind11/eigen/common.h
/usr/include/pybind11/eigen/matrix.h
/usr/include/pybind11/eigen/tensor.h
/usr/include/pybind11/embed.h
/usr/include/pybind11/eval.h
/usr/include/pybind11/functional.h
/usr/include/pybind11/gil.h
/usr/include/pybind11/gil_safe_call_once.h
/usr/include/pybind11/iostream.h
/usr/include/pybind11/numpy.h
/usr/include/pybind11/operators.h
/usr/include/pybind11/options.h
/usr/include/pybind11/pybind11.h
/usr/include/pybind11/pytypes.h
/usr/include/pybind11/stl
/usr/include/pybind11/stl.h
/usr/include/pybind11/stl/filesystem.h
/usr/include/pybind11/stl_bind.h
/usr/include/pybind11/type_caster_pyobject_ptr.h
/usr/include/pybind11/typing.h
/usr/share/cmake/pybind11
/usr/share/cmake/pybind11/FindPythonLibsNew.cmake
/usr/share/cmake/pybind11/pybind11Common.cmake
/usr/share/cmake/pybind11/pybind11Config.cmake
/usr/share/cmake/pybind11/pybind11ConfigVersion.cmake
/usr/share/cmake/pybind11/pybind11GuessPythonExtSuffix.cmake
/usr/share/cmake/pybind11/pybind11NewTools.cmake
/usr/share/cmake/pybind11/pybind11Targets.cmake
/usr/share/cmake/pybind11/pybind11Tools.cmake
/usr/share/doc/pybind11-devel
/usr/share/doc/pybind11-devel/README.rst
/usr/share/licenses/pybind11-devel
/usr/share/licenses/pybind11-devel/LICENSE
/usr/share/pkgconfig/pybind11.pc
$
 
Herewith logs and denuded spectrum.

Maybe something obvious somewhere in the logs?

View attachment 163592
The log files do not indicate anything wrong. It is probably some problem with the fedora packages you installed.
Perhaps some information appeared on the console? Python errorsindicating which pacakage is incorrectly installed?
 
Then you must have erased the files yourself, because they are definitely in th rpm:
Code:
rpm -q -l pybind11-devel
/usr/bin/pybind11-config
/usr/include/pybind11
/usr/include/pybind11/attr.h
/usr/include/pybind11/buffer_info.h
/usr/include/pybind11/cast.h
/usr/include/pybind11/chrono.h
/usr/include/pybind11/common.h
/usr/include/pybind11/complex.h
/usr/include/pybind11/detail
/usr/include/pybind11/detail/class.h
/usr/include/pybind11/detail/common.h
/usr/include/pybind11/detail/cpp_conduit.h
/usr/include/pybind11/detail/descr.h
/usr/include/pybind11/detail/exception_translation.h
/usr/include/pybind11/detail/init.h
/usr/include/pybind11/detail/internals.h
/usr/include/pybind11/detail/type_caster_base.h
/usr/include/pybind11/detail/typeid.h
/usr/include/pybind11/detail/value_and_holder.h
/usr/include/pybind11/eigen
/usr/include/pybind11/eigen.h
/usr/include/pybind11/eigen/common.h
/usr/include/pybind11/eigen/matrix.h
/usr/include/pybind11/eigen/tensor.h
/usr/include/pybind11/embed.h
/usr/include/pybind11/eval.h
/usr/include/pybind11/functional.h
/usr/include/pybind11/gil.h
/usr/include/pybind11/gil_safe_call_once.h
/usr/include/pybind11/iostream.h
/usr/include/pybind11/numpy.h
/usr/include/pybind11/operators.h
/usr/include/pybind11/options.h
/usr/include/pybind11/pybind11.h
/usr/include/pybind11/pytypes.h
/usr/include/pybind11/stl
/usr/include/pybind11/stl.h
/usr/include/pybind11/stl/filesystem.h
/usr/include/pybind11/stl_bind.h
/usr/include/pybind11/type_caster_pyobject_ptr.h
/usr/include/pybind11/typing.h
/usr/share/cmake/pybind11
/usr/share/cmake/pybind11/FindPythonLibsNew.cmake
/usr/share/cmake/pybind11/pybind11Common.cmake
/usr/share/cmake/pybind11/pybind11Config.cmake
/usr/share/cmake/pybind11/pybind11ConfigVersion.cmake
/usr/share/cmake/pybind11/pybind11GuessPythonExtSuffix.cmake
/usr/share/cmake/pybind11/pybind11NewTools.cmake
/usr/share/cmake/pybind11/pybind11Targets.cmake
/usr/share/cmake/pybind11/pybind11Tools.cmake
/usr/share/doc/pybind11-devel
/usr/share/doc/pybind11-devel/README.rst
/usr/share/licenses/pybind11-devel
/usr/share/licenses/pybind11-devel/LICENSE
/usr/share/pkgconfig/pybind11.pc
$
There were no files distributed by dnfdragora's pybind11-devel. As I said, the files I mentioned appear to be stored in something called rpmlib (CompressedFileNames), whatever that is. In my Fedora 42's dnfdragora's pybind11-devel, there is no separate 'files' to open and show in dnfdragora's pybind11-devel.

Of course, I then tried to install pybind11-devel via terminal, but It said already installed. Checking and finding none of the files actually having been installed, I had to copy and paste them from a working OS.

There was nothing in the console.
 
There were no files distributed by dnfdragora's pybind11-devel. As I said, the files I mentioned appear to be stored in something called rpmlib (CompressedFileNames), whatever that is. There is no separate 'files' to open and show in dnfdragora's pybind11-devel that I have in my Fedora 42.
rpmlib is just a library. dnfdragora is just a layer on top of dnf.

Of course, I then tried to install pybind11-devel via terminal, but It said already installed. Checking and finding none of the files actually having been installed, I had to copy and paste them from a working OS.

There was nothing in the console.
You can try reinstalling with

Code:
sudo dnf reinstall pybind11-devel
 
rpmlib is just a library. dnfdragora is just a layer on top of dnf.


You can try reinstalling with sudo dnf reinstall pybind11-devel


rpmlib is just a library. dnfdragora is just a layer on top of dnf.


You can try reinstalling with

Code:
sudo dnf reinstall pybind11-devel
That has installed an earlier version (pybind11-devel-0:2.1) Mine was pybind11-devel-0:2.13.6. I'll check how neumodvb performs.
 
That has installed an earlier version (pybind11-devel-0:2.1) Mine was pybind11-devel-0:2.13.6. I'll check how neumodvb performs.
Spectrum still missing peaks info.
 
Some news about neumoDVB: the next version will be able to handle "transport streams embedded in transport streams",
like for instance the Abertis DVB-T services on 30.0W.

This is the first working example:

1.webp


Configuration is easy and does not require stream relay and all that complicated stuff.
 
Will this work out of the box or is special configuration needed?
 
Will this work out of the box or is special configuration needed?
Years ago you could configure E2 boxes to work. they were biss encrypted. Not all the muxes used the usual plain type. Is that still the case today?
 
Back
Top