Am 19.08.2012 12:08, schrieb 1100110:
The problem is that rdmd will create temporary files within the same
directory as the .d file it compiles. On a *nix system, where vibe.d
might be installed in a read-only directory, this would cause rdmd to
fail. rdmd is also the reason why it currencly always compiles the
application - rdmd (or rather dmd -deps=...) does not detect function
local imports and string imports as dependencies. So the alternative
to spend some seconds vs. missing changes was considered the
preferable one. (The bug is partially mentioned in
Workaround is to run "vibe build" and then only the generated
Because of these issues and also to improve compatibility with gdc
and ldc, I'm thinking about implementing a build script that does not
rely on rdmd.
Really? rdmd creates files in /tmp on my Arch machine...
I'll look into it.
I have a version that outputs the applicationName upon vibe build.
Needs cleaning, then I'll pull.$VIBEPATH <- why is that there?
Looking at the source for rdmd, I see:
private @property string myOwnTmpDir()
auto tmpRoot = format("/tmp/.rdmd-%d", getuid());
which is used literally everywhere that the tmpfile is mentioned.
userid is literally hardcoded into rdmd.
I've been tracing rdmd for a few minutes, and it appears that the
version on github
does write anything to the current directory unless you specifically ask
it to(deps, etc).
I can submit a pull request for rdmd to check the current directory and
default to myOwnTmpDir if it is readonly.
Or we could always fork rdmd. It should be using the boost license and
it'd be an excellent starting point.
The executable and the object are both written to myOwnTmpDir afaict.
I just tested and you are right. The version that ships with DMD 2.060
keeps the source directory clean if it has to (unfortunately in that
case dependency tracking seems to get disabled but that's acceptable).
ignoring the error when failing to create the deps file:
But since 2.059 still has the full issue, that copy logic probably has
to stay for a bit longer to not throw someone off who is not living on
the cutting edge.
I do not know if it is still true, but since rdmd claims that it 'may
get folded into dmd',
It might be a good idea to support it 'officially' as long as it does
what is needed...
But that is your call to make.
I was about to write a reasoning why rdmd is bad right now.. but rdmd
was improved recently and now compiles only once instead of making a
separate compile just to get the dependencies, reducing the arguments
against it to one ;)
So the only issue remaining is that local/string imports are not
tracked. In this case, if there is time, a hybrid solution may work to
improve the situation. A possible approach could be to collect the time
stamps of all .dt files and only when one of them changes is rdmd
invoked with --force.
rdmd also supports the --compiler=[anything] and gdc builds and installs
gdmd by default.
my version of ldc also includes a ldmd2 wrapper by default, although I
do not know if it is built with ldc like gdc.
It looks like everything includes a "map dmd opts to our opts" mode, so
that's a very good thing for us at least.
This would just still mean that rdmd has to be distributed or at least
needs some instructions for gdc/ldc - but maybe thats OK for someone who
is probably used to such customizations. A setting for the compiler in
/etc/vibe/vibe.conf, defaulting to 'dmd', would be a good idea anyways.