On Tuesday 17 February 2004 02:29, Ben Burton wrote:
>
> > I'm no expert in makefiles but doesn't the include cause the
> > debian/debiandirs call to be made?
>
> This is the way it has always worked for me.
>
> (i.e., the include calls the file to be made and then included in the
> same "make"
> I'm no expert in makefiles but doesn't the include cause the
> debian/debiandirs call to be made?
This is the way it has always worked for me.
(i.e., the include calls the file to be made and then included in the
same "make" run).
Ben.
n trunk:
> > debiandirs is ...
> > o is not in svn
> > o created and removed by rules
> > o -included'ed in rules file.
This is all true.
> >
> > What confused me is that for the first run -include debian/debiandirs
> > can't succeed becau
oved by rules
> o -included'ed in rules file.
>
> What confused me is that for the first run -include debian/debiandirs
> can't succeed because it not there. The debian/debiandir rule
> that creates the file does not fail (to force another build run).
> Now configur
first run -include debian/debiandirs
can't succeed because it not there. The debian/debiandir rule
that creates the file does not fail (to force another build run).
Now configure would be called with an empty config_kde.
So shouldn't the debiandir rules read:
debian/debiandirs: admin/debianr
5 matches
Mail list logo