Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
One of my applications has a dependency on a stb-library. Now I am publishing this application to Github. Should I: Include the header that was used during development with the code? Have an in...
#2: Post edited
by
matthewsnyder
·
2024-07-09T15:34:23Z (5 months ago)
Managing a dependency for a C application
One of my applications has a dependency on a [stb-library](https://github.com/nothings/stb). Now I am publishing this application to Github. Should I: * Include the header that was used during development with the code? Have an install.sh script (for UNIX and UNIX-like operating systems) that would wget the header during installation? * A drawback I see with option 1 is that there may be bugs in the library, which might have been fixed later. However, a drawback with option 2 is that the library might have changed and could be incompatible with my code. Which option should I choose, and why?
#1: Initial revision
by
Melkor-1
·
2024-06-30T08:57:08Z (6 months ago)
Managing a dependency for a C application
One of my applications has a dependency on a [stb-library](https://github.com/nothings/stb). Now I am publishing this application to Github. Should I: * Include the header that was used during development with the code? Have an install.sh script (for UNIX and UNIX-like operating systems) that would wget the header during installation? * A drawback I see with option 1 is that there may be bugs in the library, which might have been fixed later. However, a drawback with option 2 is that the library might have changed and could be incompatible with my code. Which option should I choose, and why?