Guys,
Thanks for the input.
I followed the build detail associated with the GitHub source code repository simply to understand how I would build any resulting program that embeds what I can learn from available rpi_cam-apps source code. Given these things are currently bundled in Bookworm a) there's little point of head banging my way through the build process just for fun and b) I want to understand how they work then steal bits of the functionality from them to include in my remoted telescope system and then be able to build it easily.
The link above hidden under the "here" is brilliant for anyone needing to better understand how to run the new improved apps. Its a whole lot less brilliant at explaining how the build process is done. I have always been very suspicious when told "one simply waves one's magic wand like this, no not like that, this ..." and it all works. Agreed, following this method gets stuff working but in this context nobody learns how its really done. It's the world of "Write-Only" coding. No one can follow it. More importantly, no one can learn from it.
As outlined above, I did get to start the build but it immediately barfed because it didn't find the necessary header files. Being quite late by then I'd had it although did have a quick look for the missing headers. Yes I found them but in deeper sub-directories so assumed something not obvious to me was needed hence questioning here. I do have to admit to being a bit punchy by the time I started the build. At the end of the day I will have to adapt everything learnt into my current MJPG Streamer CMake system which I also struggled with before extending it.
At the end of the day its all about attempting the impossible. One never knows what might come of it. Its not rocket science but at this time it is very Harry Potter.
Will have another go.
Edit: bottom line ... I don't want or need to run the new Apps. Did all that years ago when the Pi camera came out. I want to learn and build forward from them.
Thanks for the input.
I followed the build detail associated with the GitHub source code repository simply to understand how I would build any resulting program that embeds what I can learn from available rpi_cam-apps source code. Given these things are currently bundled in Bookworm a) there's little point of head banging my way through the build process just for fun and b) I want to understand how they work then steal bits of the functionality from them to include in my remoted telescope system and then be able to build it easily.
The link above hidden under the "here" is brilliant for anyone needing to better understand how to run the new improved apps. Its a whole lot less brilliant at explaining how the build process is done. I have always been very suspicious when told "one simply waves one's magic wand like this, no not like that, this ..." and it all works. Agreed, following this method gets stuff working but in this context nobody learns how its really done. It's the world of "Write-Only" coding. No one can follow it. More importantly, no one can learn from it.
As outlined above, I did get to start the build but it immediately barfed because it didn't find the necessary header files. Being quite late by then I'd had it although did have a quick look for the missing headers. Yes I found them but in deeper sub-directories so assumed something not obvious to me was needed hence questioning here. I do have to admit to being a bit punchy by the time I started the build. At the end of the day I will have to adapt everything learnt into my current MJPG Streamer CMake system which I also struggled with before extending it.
At the end of the day its all about attempting the impossible. One never knows what might come of it. Its not rocket science but at this time it is very Harry Potter.
Will have another go.
Edit: bottom line ... I don't want or need to run the new Apps. Did all that years ago when the Pi camera came out. I want to learn and build forward from them.
Statistics: Posted by RaspISteve — Tue Mar 05, 2024 3:31 pm