Package Details: libbulletml 0.0.6-6

Git Clone URL: (read-only, click to copy)
Package Base: libbulletml
Description: C++ library to handle BulletML, a markup language to describe bullets in shooting games.
Upstream URL:
Licenses: custom:libbulletml
Submitter: escondida
Maintainer: escondida
Last Packager: escondida
Votes: 4
Popularity: 0.000000
First Submitted: 2015-12-11 23:35 (UTC)
Last Updated: 2018-10-03 18:10 (UTC)

Latest Comments

escondida commented on 2018-10-03 18:11 (UTC)

Updated to 0.0.6-6; added bulletml_d.o to OBJS in Makefile. Thanks to amunkres for pointing out the omission.

amunkres commented on 2018-09-30 14:53 (UTC) (edited on 2018-09-30 14:54 (UTC) by amunkres)

When trying to build torus-trooper, I encountered a bunch of linker errors like this:

ld: src/abagames/tt/barrage.o: in function _D8abagames2tt7barrage14BarrageManager11getInstanceFAaAaZPi': barrage.d:(.text+0xef6): undefined reference toBulletMLParserTinyXML_new'

The problem seems to have been caused by the "bulletml_d.cpp" file having been omitted from the build of libbulletml. It seems like appending "bulletml_d.o" to OBJS in this libbulletml AUR package's custom Makefile solved the problem for me; for example:

OBJS = bulletmlparser-tinyxml.o bulletmlparser.o bulletmltree.o calc.o formula-variables.o bulletmlrunner.o bulletmlrunnerimpl.o bulletml_d.o

(Also, be aware that the "debian/patches/makefile.patch" patch file included within "bulletml_0.0.6-7.debian.tar.xz" also patches the OBJS variable to include "bulletml_d.o", just like this.)

zorun commented on 2016-06-27 08:48 (UTC)

I agree with you in principle. However, a more pragmatic point of checksums is to make sure that the user builds from the same tarball as the maintainer. There are many reasons why the upstream tarball may change between the time you upload the package and a user tries to build it: - the tarball was somehow corrupted during download or storage - some malicious person added a backdoor to the upstream tarball - upstream overwrote the tarball with a new version - the tarball is no longer available upstream and returns e.g. a HTML page instead All of these are serious issues, and are catched by checksum verification.

escondida commented on 2016-06-27 00:28 (UTC) (edited on 2016-06-27 00:28 (UTC) by escondida)

No, if upstream chooses not to provide integrity checks, it would be a meaningless gesture for me to add them. Without checksums from upstream, there's no way for me to check whether or not mine match the dev's One True Tarball.

zorun commented on 2016-06-26 14:35 (UTC)

You should provide checksums for the files, even though upstream does not publish any... 7c37f3d2d52825417c5de716f89bea4b71156371e698e2579daf7921df07aa79 libbulletml-0.0.6.tar.bz2 f0a9f01ef9daaa980f876253c81e8e76eea17b7de1aa569bf23661b456c5c9d3 d_cpp.tar.bz2