Package Details: libtcod 1.13.0-1

Git Clone URL: https://aur.archlinux.org/libtcod.git (read-only)
Package Base: libtcod
Description: Roguelike graphics/utility library
Upstream URL: https://github.com/libtcod/libtcod
Licenses: BSD
Submitter: feufochmar
Maintainer: feufochmar
Last Packager: feufochmar
Votes: 28
Popularity: 0.019077
First Submitted: 2012-08-31 18:06
Last Updated: 2019-07-07 12:29

Latest Comments

1 2 3 Next › Last »

feufochmar commented on 2018-07-01 21:18

@Eremiell That was always the case. I've open an issue upstream ( https://bitbucket.org/libtcod/libtcod/issues/125/ ).

Eremiell commented on 2018-07-01 20:06

Seems to produce libtcod.so.0.0.0 etc. for me instead of e.g. libtcod.so.1.7.0.

Viech commented on 2018-04-10 02:06

Just letting you know that I used your package as a basis for a python-libtcod package (https://aur.archlinux.org/packages/python-libtcod/). If you ever decide to include python bindings in your package let me know and I'll dispose of it again.

feufochmar commented on 2018-04-06 23:40

The problem raised by Viech has been fixed in the 1.6.6 release, with the correction of the autotools building files (fixing where the pstdint.h is located when installed).

feufochmar commented on 2018-04-04 16:56

I don't encounter a problem when I build the package. There may be a problem when using it though. From the PKGBUILD directory path, that file is located after building the package at:

  • ./src/libtcod/include/external/pstdint.h => source file is inside include/external

  • ./pkg/libtcod/usr/include/libtcod/pstdint.h => when installed, the file is located in the /usr/include/libtcod directory, not /usr/include/libtcod/external

Viech commented on 2018-04-04 16:36

Hello, I just posted an issue on the libtcod tracker that appears to break this package: https://bitbucket.org/libtcod/libtcod/issues/121/include-of-external-pstdinth-fails

If it's not receiving a fix you might want to patch around it like the Debian maintainer did.

feufochmar commented on 2015-08-27 18:47

I've changed the source for the bitbucket one.
I've also uploaded a development version of this package or AUR (libtcod-hg).

feufochmar commented on 2015-08-27 17:31

@elimik31: I've unflagged the package out-of-date, since its use is not for indicating a broken or changing source link. Also, as this package builds from sources so it is not affected by the potential problems of the binary versions.
For your suggestion, it's maybe something this package should do, to avoid what happened recently. I'll probably update the package to do this.

elimik31 commented on 2015-08-27 14:10

I marked this package out-of-date, but now I think it probably was a mistake. It was due to the following message on [roguecentral](http://roguecentral.org/doryen/libtcod/):

> This website is no longer the home of libtcod. You can get the source and report issues on bitbucket : https://bitbucket.org/libtcod/libtcod
>
> The forum is still open and will be available as long as needed : forum
>
> The old material is still available but there’s no guaranty that the binary builds will still work with nowadays compilers. You’d better compile the library from the bitbucket sources.

However, the current build on bitbucket is unstable yet and the latest stable build is 1.5.1, which is identical to the one on roguecentral, which is used in this PKGBUILD. However, for the future it would be probably better to compile the source code from the latest stable tag on bitbucket.

elimik31 commented on 2015-08-27 14:09

On roguecentral (http://roguecentral.org/doryen/libtcod/) it says:
I marked this package out-of-date, but now I think it probably was a mistake. It was due to the following message on roguecentral (http://roguecentral.org/doryen/libtcod/):

> This website is no longer the home of libtcod. You can get the source and report issues on bitbucket : https://bitbucket.org/libtcod/libtcod
>
> The forum is still open and will be available as long as needed : forum
>
> The old material is still available but there’s no guaranty that the binary builds will still work with nowadays compilers. You’d better compile the library from the bitbucket sources.

However, the current build on bitbucket is unstable yet and the latest stable build is 1.5.1, which is identical to the one on roguecentral, which is used in this PKGBUILD. However, for the future it would be probably better to compile the source code from the latest stable tag on bitbucket.