That's probably a very bad idea. Let's use a practical example:
A while ago OpenSSL suffered from the Heartbleed bug. Suppose that you built a library that packaged a bad version of OpenSSL inside it. After OpenSSL got fixed, your clients would still need to wait for you to release a new version of your software that contained a good version of OpenSSL. You can imagine that this is NOT a good situation. Instead, they can just replace their own OpenSSL version with a good one, and everything will be okay.
A much better solution is to use a dependency manager. You declare what dependencies your library has, and when one of your clients in turn depends on your library, the manager will automatically let them depend on any dependencies your library has.
Take a look at
Maven.