RejectedSoftware Forums

Sign up

Dependency tracking

Hi

I have setup a basic project and I try to understand how
dependency tracking works. If I have my app running and I modify
a template file - is vibe supposed to detect that and recompile
the app? Because currently I don't see it happening. In the
examples directory I noticed a file that was commited to the repo:

examples/app_skeleton/source/app.d.deps

It looks like an autogenerated file and when I run my app there
is no dependency file generated. Is that a bug or do I need to
run vibe in a specific way?

Re: Dependency tracking

Am 31.08.2012 18:31, schrieb Eldar Insafutdinov:

Hi

I have setup a basic project and I try to understand how dependency
tracking works. If I have my app running and I modify a template file -
is vibe supposed to detect that and recompile the app? Because currently
I don't see it happening. In the examples directory I noticed a file
that was commited to the repo:

examples/app_skeleton/source/app.d.deps

It looks like an autogenerated file and when I run my app there is no
dependency file generated. Is that a bug or do I need to run vibe in a
specific way?

The automatic rebuild of the application is a feature of vibedist [1]
rather than the vibe.d core package. However, vibedist is not fully in
shape yet - but it should be ready in the next couple of weeks, as soon
as I find some time for it. I'll then also put up some instructions how
to set it up and notes for some features that they are part of vibedist.

The deps file was just checked in accidentially and is only a left-over
of rdmd. I think rdmd in it's current version does not leave the file
there after compilation so it should be normal that you don't see it now.

[1] https://github.com/rejectedsoftware/vibedist

Re: Dependency tracking

On Saturday, 1 September 2012 at 09:31:11 UTC, Sönke Ludwig
wrote:

The automatic rebuild of the application is a feature of
vibedist [1]
rather than the vibe.d core package. However, vibedist is not
fully in
shape yet - but it should be ready in the next couple of weeks,
as soon
as I find some time for it. I'll then also put up some
instructions how
to set it up and notes for some features that they are part of
vibedist.

The deps file was just checked in accidentially and is only a
left-over
of rdmd. I think rdmd in it's current version does not leave
the file
there after compilation so it should be normal that you don't
see it now.

[1] https://github.com/rejectedsoftware/vibedist

Great to hear that. Another suggestion would be to introduce a
comiler flag DEVELOPMENT_MODE. When compiled with this flag
enabled it would read template files from the file system and
interpret them at runtime. It will be more convenient for
developepment process, because changing of a template file won't
lead to recompiling of the whole app.