Another solution is to direct the user to install the library as-supplied from the third party. While this may seem like another unnecessary step, this way the user gets the most updated version of the driver/library that the third party has to offer, and you don't have to continually update your installer when the manufacturer updates their drivers. It also reduces the probability that you will end up with two different versions of the vis on the host computer and have to sort out cross-referencing issues, which are always ugly. Dealing with different paths can also be problematic, so this technique allows the user to put the third-party library wherever they want, without you having to depend on a fixed path.
To mitigate the possibility of incompatibility with new releases of the drivers, you will need to stay abreast of changes and potentially introduce version detection and management within your code for the third-party library.
This solution also eliminates complications to do with bundling third-party software into your releases from an IP perspective.