Design pattern to integrate with many libraries offering the same thing

I'm writting a simulator that could make use of a number of libraries for a card game with different pros and cons. The libraries have similair concepts(e.g. they all know about a card) which allows me to write mostly a single structure of code and swap in the various libaries. My problem is that the entities in the libraries differ slightly and obivous the only common ancestor across the two libraries is object. Is there a standard approach to this problem?