Author Topic: Hydra Slayer (now at 16.1), NotEye (now at 8.1)  (Read 102788 times)

Zireael

  • Rogueliker
  • ***
  • Posts: 604
  • Karma: +0/-0
    • View Profile
Re: Hydra Slayer (now at 16.1), NotEye (now at 8.1)
« Reply #180 on: October 03, 2014, 09:40:19 AM »
Any chance of supporting Incursion? After all, it uses libtcod...

Z

  • Rogueliker
  • ***
  • Posts: 905
  • Karma: +0/-0
    • View Profile
    • Z's Roguelike Stuff
Re: Hydra Slayer (now at 16.1), NotEye (now at 8.1)
« Reply #181 on: October 03, 2014, 05:42:20 PM »
The original Incursion does not uses libtcod, but the community version does. Is this right?

I could look into it. I suppose the best solution would be to edit the sources so that NotEye is used instead of libtcod, though (the NotEye-libtcod adapter does not work very well, and also it works with 1.5.1 for MinGW only, and Incursion apparently uses 1.6.0 for MSVC). Although it would have to be a copyleft-licensed derivative of Incursion, and Julian says that he does not want such things.

chooseusername

  • Rogueliker
  • ***
  • Posts: 329
  • Karma: +0/-0
    • View Profile
    • Email
Re: Hydra Slayer (now at 16.1), NotEye (now at 8.1)
« Reply #182 on: October 06, 2014, 08:22:18 PM »
The original Incursion does not uses libtcod, but the community version does. Is this right?

I could look into it. I suppose the best solution would be to edit the sources so that NotEye is used instead of libtcod, though (the NotEye-libtcod adapter does not work very well, and also it works with 1.5.1 for MinGW only, and Incursion apparently uses 1.6.0 for MSVC). Although it would have to be a copyleft-licensed derivative of Incursion, and Julian says that he does not want such things.
Yes, the community version uses libtcod.  All the related code is isolated in one file.

I do not know what copyleft is, and the meaning is non-obvious, but assuming it is some in-group way of referring to GPL..  All the changes in the community version are pretty much mine, and I am also disinterested in licensing my changes under the GPL.

That said, GPL if your goal, should be irrelevant.  You should be able to add a Wnoteye.cpp to match a Wlibtcod.cpp and license that isolated file under the GPL and have it optionally compiled in.  Licensing some of the code under the GPL does not require that all the code be licensed under the GPL, just that all the source code for a distributed end product be available for any recipient to recreate that same end product.  At least, that was my conclusion of GPLv3 last time I refreshed from it.