Cannot build on Pi4 #35
Comments
|
Debugging the first of many errors in the output |
|
So |
|
then then success!! :-) So, those could be added to the readme along with libcec6 and libcec-sys etc. |
|
Now I just need to get the example building: |
|
Tried adding: in the lib's build.rs, but no change |
|
Did you install p8 from system package repositories? It is probably called libp8-platform-dev |
|
initially I built and installed from source. Then I noticed: So I did: as a bit of an experiment, and now I am back to original error: |
|
At least previously no such hacking was needed, checkout github actions Did you also install non-dev version of p8 platform. |
|
Looks like all the CI uses cross-compiling on Ubuntu. I am compiling natively on RPi, and RPiOS. |
|
That is true indeed. Let's walk this through step by step:
With example app:
|
|
I get this I did the copy/link trick described here: You can see all the version numbers there I think: Output of OS Version: Then I did in lib:
Then in the sample app I did:
Output: No change. |
|
Thank you Are you sure you copy pasted full build output with double verbose (-vv) setting? I think this is only few lines now Full output would show compilation and other steps |
|
I include long-line AND wrapped versions WRAPPED
= note: some error: could not compile Caused by: |
|
I will try to reproduce as well, I am not sure what that error means exactly. |
|
WIP (for my own notes) Reproducing using QEMU emulating raspberry pi 3 (https://blog.ramdoot.in/emulating-raspberry-pi-on-with-qemu-951283daf2bd) and |
|
SInce they are linker symbol problems, they don't show up with cargo check. |
|
I am having lack of time trying to reproduce and debug this now, but will come back to it in the coming weeks. In the meantime, can you compile this simple C program: Pulse-Eight/libcec#602 ? |
|
@andrewdavidmackenzie I could not reproduce this issue using qemu setup above... Build went just fine with no issues I wonder what is different to your setup? |
How are you building the example? I don't have thsoe example files in target/debug |
|
I built it using "cargo build", inside the example folder, see #35 (comment) No need to build cec-rs, it gets automatically built |
|
OK, when you say "inside the example folder" you mean: that produces the original error: and there is no |
|
Yes, correct on That is what I did. Others steps are documented also above I do not have cec-rs/target folder at all, only cec-rs/examples/cec-example-cli/target. All build artifacts from the example end up there, including build output from the dependency cec-rs Are you sure you have cleaned build artifacts properly after removing the self-built libraries? I presume that cargo clean in cec-rs does not clean cec-rs/examples/cec-example-cli/target |
|
So, the bit of your previous comment that I cannot reproduce (running ldd) is this: in my machine: when inside "cec-rs/examples/cec-example-cli" (even after running build) there is no sub folder of "target/debug" called "cec-example-cli" |
|
I think it is expected pi@raspberrypi:~/cec-rs/examples/cec-example-cli $ ldd target/debug/cec-example-cli works only if -- Would it be possible for you to take a new SD card, install OS and try again? |
|
Another thing I just realized Last time I checked, in 2022, the libcec as offered by debian repos did not have support for raspberry pi hdmi cec. Presumably, the library was built without support to RPi HDMI cec driver. At least I did not get it to work in my personal setup Things might work better nowadays, who knows I have updated the build instructions specifically with Raspberry Pi OS: |
|
@andrewdavidmackenzie any update on this? |
|
No, I did not make any progress. I did buy the pulse8 HDMI/USB controlled dongle but haven't had the chance to play with it yet. |
|
I will close this now (as I could not reproduce in qemu), pleasw re-open if the issue persists |
I am trying to build cec-rs on my Raspberry Pi 400.
I have installed:
When I try
cargo buildI get "No such file or directory" for#include <cecc.h>in thebuild/smoke_abi*.cfilesThe text was updated successfully, but these errors were encountered: