4

I am writing a game engine with an abstraction layer that allows different external libraries to be used as backends for graphics, sound, input, physics, etc. For each of these backends/external libraries I have a wrapper library.

Assuming my game engine is called libge.so, and there are 2 libraries called libgraphics1.so and libgraphics2.so, with my current naming convention I would name the wrappers libge_graphics1.so and libge_graphics2.so.

Does this naming convention cause any copyright conflicts, whether the external library is FOSS or not?

I'm leaning towards licensing my code LGPL if that is relevant.

Improve this question

1 Answer 1

Reset to default
5

Simple names are not protected by copyrights, so there is no objection from that side to your naming convention.

The intellectual property law to keep an eye on with simple names is trademark law. That law basically states that if someone has registered their name as a trademark, then you cannot use a confusingly similar name for a similar product. But with your naming scheme, you are also not creating confusingly similar names.

TL/DR: There are no problems with using your proposed naming scheme.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.