Control: block -1 by 790317 Hi Martin,
On Sat, Jun 27, 2015 at 3:26 PM, Martin Michlmayr <t...@cyrius.com> wrote: > Package: 0ad > Version: 0.0.18-1 > Severity: wishlist > Tags: upstream > User: debian-...@lists.debian.org > Usertags: arm64 > > It would be nice if 0 A.D. would support ARM64. There are Android > based devices on ARM64 already and I suspect we'll be seeing Linux > desktop devices based on ARM64 soon as well. > > I know this is really an upstream issue, but it would be great if you > could raise an upstream feature request. > > I briefly looked into it and created a patch with some obvious > locations where ARM64 (or AARCH64, as it's officially called) should > be added, but I'm sure it's incomplete. I also noticed > libraries/source/nvtt where ARM is referenced. It's worth noting that 0ad build-depends on nvidia-texture-tools in Debian, so we can ignore the embedded copy of nvtt in 0ad's source. > Note that I followed the existing code in source/lib/byte_order.h but > imho this is not an optimal way to do things as e.g. MIPS and ARM can > be both little or big endian. Would you consider filing this bug report directly upstream [1][2], with your patch (just like you did with nvidia-texture-tools)? I'm not a porter myself and I don't think there's any value in me being a middleman, in case upstream has any questions to ask you etc. Thanks! [1] http://trac.wildfiregames.com/newticket [2] alternatively, upstream is pretty active on IRC (freenode #0ad-dev) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
