Skip to content
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

Request: Create libuvc separate fork #38

Closed
nsknyc opened this issue Dec 21, 2023 · 2 comments
Closed

Request: Create libuvc separate fork #38

nsknyc opened this issue Dec 21, 2023 · 2 comments

Comments

@nsknyc
Copy link
Contributor

nsknyc commented Dec 21, 2023

Hello Peter,
I noticed that the libuvc library you have included in the repo has a readme to ktossell github. I checked and that seems to be the old name. Anyways I was wondering if it's possible for you to fork libuvc to keep track of changes. The reason I ask is that groupgets (purethermal) also has some modifications to libuvc, and I'd hate to cause some conflicts. I also don't want to replace your libuvc version with a potentially older version (when I do pull requests). With a fork I can compare the official repo, with your modifications and merge groupgets' as well.

I hope I wasn't too confusing. I have radiometric data working on a test app with Y16 and would like to implement it here. I don't have much experience with other thermal cameras, but I can assume that they function the same way. Maybe this addition will help other.

Thanks!

@Peter-St
Copy link
Owner

Peter-St commented Dec 24, 2023

Hi nsknyc,

The libuvc version in this Repo is modified 2 times. First it was modified to work with an older LibUsb versions and working with Android. After that I modified the version again to work with my custom driver input.
Replacing the libuvc version of this repo with an official fork of the libuvc version will follow in a lot of overlaps in the code. It's even hard to solve all the overlaps "I" commited to this version. Then all the previous commits needs to be merged too, which I think I'm not aware of. I have tried to get it done, but got a lot of errors and sigsegv's, because my app also uses a lot to tracking over jna.

I think at this point it would be easier to create a new app based on the latest libuvc version to get it running, before getting this merged version sucessfully running with the latest libuvc version.
Another thing would be, that differnet upgrads in my app and in the official libuvc version will lead to a lot of conflicts during time. I think I will spare this work to me.

So far, upgrades in the official LibUvc version can also be commited to this libuvc version relativ easily, because the two libuvc versions are still quite related. If you have some suggestions, I`m quite interested in hearing them.

Thx, Peter

@nsknyc
Copy link
Contributor Author

nsknyc commented Dec 24, 2023

Understood! I'll bring over the modifications (from another fork) over to this one. This way we can have radiometric data in this app.
"If you have some suggestions, I`m quite interested in hearing them."
As far as the lib, that was pretty much it. Any modifications to the app itself I'll just test in another branch.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants