Expose the Go library for use in other projects

[madpipeline]

Hello,

Id like to use your go library in my project. Would you be interested giving more focus on this idea?

Here are few things I've thought about on the topic:

• Use git submodules for the C driver to be easily updateable and tracked
• Contribute the Go library to upstream: https://github.com/Sensirion/raspberry-pi-i2c-sen5x
• Setup CI for tracing builds and binaries

What do you think?

[aggellos2001]

Hello,

Thank you for your input. I liked this idea for exposing the CGO wrapper for other projects. I wanted to do this before, however I completely forgot it.

Since Go is a beautifully designed language, I extracted the library wrapper, made its own module and released it on GitHub separately. So the need for Git submodules is eliminated since this project can just add the library directly like any other Go package.

You can view and use the now separated library here!.

Let me know your opinion!

[madpipeline]

This is awesome. I'll update my project to use the new module.

I proposed git sub-modules to fetch the Sensirion C files. The way it is now, how can you tell from what commit were the C files copied from upstream?

[madpipeline]

Also I've noticed the C files were modified. How do you keep track of these changes when you want to update the upstream?

[aggellos2001]

Hi,

Ah, I see what you had in mind. Sensirion updates their C files quite rarely as it seems and when it does, it's small changes that can be easily tracked manually. Also, given that CGO will only compile C files that the same directory as the Go package directory, this could add unnecessary effort.

Let me know your thoughts!

[madpipeline]

Ah, yes, I forgot about that. How do you keep track of the changes you've made when you want to update the upstream then?

[aggellos2001]

Since the C files are just that, a text file, If I update a file from upstream the changes will also reflect here quite easily. And also, since this is a wrapper, it's not a good idea to update the underlying code without also updating the wrapper.