Open wilzbach opened 8 years ago
Because dmd does not compile imported modules by itself. You have to specify ALL modules used in an application to compile and link them. Usually this is done by a build tool, though (rdmd, dub etc.)
You can use rdmd to build programs if you use --build-only
.
You can use rdmd to build programs if you use --build-only.
Nice! I tried to make an AUR package out of this, here's my inital attempt. Would be nice to have your feedback on it ;-)
I'll check it out.
I'm pretty new to Arch, but here's what I noticed when comparing the PKGBUILD with some other D packages:
arch
should probably be ('i686' 'x86_64')
as those are the architectures supported by dmdgroups
can be dlang
, there's some stuff there alreadydepends
should probably include dmd
as dbuildstat
invokes itgit submodule
commands with one: git submodule update --init
md
/ms
/pt
seem a bit cryptic, I would use the full name (e.g. dbuildstat-makkedot
@Dicebot could offer more insight, he seems to have more experience making D packages for Arch.
Sure. Some quick suggestions:
git submodule update --init --recursive
is what you usually want for getting submodules. It is more common to do it as part of build()
function though unless you need applying custom patches (which is what prepare()
is intended for)dmd
as build dependency explicitly as dtools
can be installed also with ldc
or gdc
and your build script doesn't support theminstall
with explicit target file permissions is preferable over cp
(upstream build system may produce overly permissive binaries)makedot
(pacman will tell you if it conflicts with any other installed package) or use a full prefix of dbuildstat-makedot
arch('any')
should only be used if your PKGBUILD supports ldc
/gdc
and thus ARM/MIPS targets.
Why is not possible to compile DBuildStat with
dmd
?Running it with
rdmd
works fine ...