-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't compile #110
Comments
Did you install the pylon software suite? |
yep i install everything by the guide |
Have you found the solution? I have the same issue. |
I have tried moving to newer versions of meson, messing with environment variables, and applying arguments to commands. Nothing worked for me. `Determining dependency 'pylon' with CMake executable 'C:\Program Files\CMake\bin\cmake.EXE'
Determining dependency 'pylon' with CMake executable 'C:\Program Files\CMake\bin\cmake.EXE'
gst-libs\gst\pylon\meson.build:28:16: ERROR: Dependency "pylon" not found, tried cmake |
Our CI builds on windows gst-plugin-pylon/.github/workflows/ci.yml Line 100 in f9dc08c
Can you check your steps against our setup? |
Unfortunately, it didn't work. Here are my steps:
Output: gst-libs\gst\pylon\meson.build:28:16: ERROR: Dependency "pylon" not found, tried cmake |
It seems similar to #68 , is there a work around the issue? |
can you list contents of: C:\Program Files\Basler\pylon 7\Development\CMake\pylon dir "%CMAKE_PREFIX_PATH%" We did a cross check with also latest cmake latest meson ninja ( that you get for a fresh install ) it works on our side CMake binary for host machine is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Found CMake: C:\xxxxxxxxx\miniconda3\envs\test_gst\Library\bin\cmake.EXE (3.30.0)
Extracting basic cmake information
CMake Toolchain: Calling CMake once to generate the compiler state
Calling CMake (['C:\\xxxxxxxxx\\miniconda3\\envs\\test_gst\\Library\\bin\\cmake.EXE']) in C:\xxxxxxxxxx\gst-plugin-pylon\test_build\meson-private\__CMake_compiler_info__ with:
- "--trace-expand"
- "--trace-format=json-v1"
- "--no-warn-unused-cli"
- "--trace-redirect=cmake_trace.txt"
- "-G"
- "Ninja"
- "-DCMAKE_TOOLCHAIN_FILE=C:/xxxxxxxxx/gst-plugin-pylon/test_build/meson-private/__CMake_compiler_info__/CMakeMesonTempToolchainFile.cmake"
- "."
- "-DCMAKE_PREFIX_PATH=C:\Program Files\Basler\pylon 7\Development\CMake\pylon\" |
You call meson with an Option vs2022 .. |
this is a working script using conda python: rem "using conda to install all deps"
call conda install -y cmake meson ninja
call conda --version
echo "cmake ( installed in conda)"
call cmake --version
echo "python interpreter"
call python --version
echo "meson"
call meson --version
echo "ninja"
call ninja --version
rem setup the paths to gstreamer
set PKG_CONFIG_PATH=%GSTREAMER_1_0_ROOT_MSVC_X86_64%lib\pkgconfig
set PATH=%PATH%;%GSTREAMER_1_0_ROOT_MSVC_X86_64%\bin
cd gst-plugin-pylon
rmdir /q /s builddir
meson setup --vsenv builddir --prefix=%GSTREAMER_1_0_ROOT_MSVC_X86_64%
meson compile -C builddir
meson install -C builddir |
Thank you! I was able to build it in a conda environment by following your instructions. Great support! Thank you again for your work! Unfortunately, the issue wasn't opened by me, so I can't close it. |
Hello, @thiesmoeller, there's one more issue. Even though the meson succeeds, I get "No such element or plugin 'pylonsrc'" when running "gst-inspect-1.0 pylonsrc". What might be the cause? |
first check if gst-inspect has blacklisted the plugin from a failed start in the past:
if this is the case delete the cache file in
if you now call |
It wasn't in the list, but I deleted cache just in case. However, pylonsrc still doesn't show up despite all the libraries and config files being in respective folders |
what was the output of |
Thank you, I found how to do it by launching it from the bin directory |
this still shouldn't be the way it is on your system.. :-\ can you run other plugins or inspect them like
|
After following the guide I always come to this result
The text was updated successfully, but these errors were encountered: