Hi All,
I'm currently in the process of introducing a bunch of ebuilds
related to the D programming language into the tree. I'll begin with
the binary compiler provided by Digital Mars and then move onto the
GCC based compiler.
1) The dev-lang/dmd-bin ebuild will be fairly straightforward with
the compiler going into /opt. I'm using an env.d entry to modify the
user's path (much like ghc-bin), but I notice that the naming
convention in /etc/env.d is seemingly random. I can't really think of
what 2 digit prefix would be most appropriate prefix for DMD.
2) The dev-lang/d-gcc ebuild would require more thought. I notice the
following line in toolchain.eclass:
# support for the D language
[[ -n ${D_VER} ]] && \
GCC_SRC_URI="${GCC_SRC_URI} d? ( mirror://sourceforge/dgcc/
gdc-${D_VER}-src.tar.bz2 )"
I'd appreciate it if one of the toolchain ninjas could clarify their
stance on D :)
The toolchain eclass seems to be most appropriate for this ebuild.
However, if it turns out that toolchain.eclass requires some changes
to support D it may be better to go in for a seperate eclass like dev-
lang/gnat-gcc. Or even better, create a common eclass for all the 3rd
party GCC frontends.
3) There are quite of a few D applications out there that I'd like to
add support for. Examples are DUI (D bindings to Gtk, leds (an IDE)
and Tango (a general purpose library). However, for this to happend,
we need a virtual for the D compiler.
Thoughts, suggestions, comments and criticisms invited :)
Cheers,
--
Anant
--
[email protected] mailing list
