Before going too far, I suggest you review the license for the library you are using. Sometimes these licenses impose restrictions on how they can be used with open source. For example, a library may say you can't use it with GPL projects.
Even if the license doesn't impose any restrictions, I recommend you look at a permissive license (like MIT or Apache 2.0) for your project. It's pretty well understood in the community that these licenses are compatible with closed source commercial software. That analysis is more complicated with restrictive licenses like the GPL and some people may bypass your project as a result.
If you want to encourage adoption and use, consider a permissive license. If you want to ensure that no one uses your code to create and distribute a closed source version of your project (and if the library's license allows it), you should consider a copyleft license like the GPL. But note that this option comes with added complexity for your users. Good luck!