-
Notifications
You must be signed in to change notification settings - Fork 412
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
Fix cmake setup for yocto #290
Fix cmake setup for yocto #290
Conversation
I have no knowledge or experience of using cmake so can not judge the merits of this request. That said, I am happy to accept this as long as no one objects within a few days. |
I would like to second this issue, I was hunting down this for a couple of hours today for my own yocto build until I solved it myself with a patch. It would be great if this was merged. |
I'll try to include this in the next release sometime in March. |
@GertRozing Do you have pigpio recipe which works with this PR? coud you share it? I would like to add pigpio to my yocto build. Thank you. |
I have this recipe. It comes with it's own patch to prevent the issue here, but you can now of course just ditch that. It is also not very sophisticated, but it gets you going.
|
@dir-ableton thanks, I will give it a try |
The current cmake setup of the pigpio project was incompatible with a yocto build for the raspberry pi. For some reason it had problems finding standard header files like <stdio.h>. However the builds succeeded on non Yocto builds which reinforced my suspicion that the CMake setup was the cause.
Nevertheless I modernized the CMake setup, which now also builds in a yocto environment :D. The new CMake conforms with the current CMake 3.0 standard. As such the following features are available.
I wrote these enhancements for our own raspberry pi yocto builds, which require pigpio. We used to use WiringPi, however that project got disbanded by the maintainer himself, which is sad. Nevertheless the pigpio project works equally amazing.