Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: Shared/static library naming advice  (Read 11960 times)

0 Members and 2 Guests are viewing this topic.

Jebbs

  • Sr. Member
  • ****
  • Posts: 358
  • DSFML Developer
    • View Profile
    • Email
Shared/static library naming advice
« on: February 11, 2015, 08:11:02 pm »
Hey all,

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. :P
DSFML - SFML for the D Programming Language.

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11030
    • View Profile
    • development blog
    • Email
AW: Shared/static library naming advice
« Reply #1 on: February 11, 2015, 10:27:21 pm »
What is "the backend"?
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

Jebbs

  • Sr. Member
  • ****
  • Posts: 358
  • DSFML Developer
    • View Profile
    • Email
Re: Shared/static library naming advice
« Reply #2 on: February 11, 2015, 10:47:30 pm »
It's basically my own version of CSFML.
DSFML - SFML for the D Programming Language.

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 11030
    • View Profile
    • development blog
    • Email
Re: Shared/static library naming advice
« Reply #3 on: February 11, 2015, 10:58:41 pm »
So why not give it a different name than dsfml (or csfml)? ;)
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

Jebbs

  • Sr. Member
  • ****
  • Posts: 358
  • DSFML Developer
    • View Profile
    • Email
Re: Shared/static library naming advice
« Reply #4 on: February 12, 2015, 01:58:48 am »
Because I thought that it would be cool to have all the shared libraries (the ones people could see) be called dsfml :P
DSFML - SFML for the D Programming Language.