I'm gearing up for the next release of DSFML, and there was one issue that I can't really decide on my own as I am not sure what is best. I wanted to get some advice from the community before I made a final choice.
My dilemma is that the naming conventions of the libraries needed to get DSFML going are a little wonky. If you don't use DUB
, then you have to link to two sets of libraries to get everything building correctly. The back end (C/C++) shared libraries use dsfml-xxx, and the front end (D wrapper code) uses dsfml-xxx-2. This has caused confusion for more than a few people.
I have thought of a couple of solutions, but I am not terribly happy with any of them.
So far I have:
- Rename the back end to something else, such as dsfmlc-xxx, and use dsfml-xxx for the D wrapper code.
- Rename the front end library names to something else to make it more apparent that they are the wrapper code, perhaps dsfml-xxx-lib.
I know this is a weird question to ask, but I don't really get a lot of feedback on this kind of thing when I try to discus it with the users on github.
People that don't use D are welcome to chime in as well.