Eric <keller.e...@gmail.com> wrote: > consider the following host structure: > > application/services/makerules/check.rule: [...] > include ./instrdeps.rule > [...]
./ means your current directory, that is supposed to be the directory which you have done cd to. > application/services/makerules/instrdeps.rule [...] > > application/models/BD/Makefile: > [...] > include ../../services/makerules/check.rule [...] check.rule is said to be in another directory as the complete path is given to check.rule. > The following error is then showing up: > ../../services/makerules/check.rule:2: instrdep.rule: No such file or > directory That is because instrdep.rule is not in your current directory, as you have shown above it is in the same directory as check.rule and should be located with the same path. > I was awaiting that the include directive first seeks for the file to > include in the same directory where the file originally exists. What I > mean, is that the file check.rule "include ./instrdeps.rule" should look > for the instrdeps.rule in the same directory as where the check.rule is > located. No, ./ means your current directory, not the directory of your last included file. > Now that I witnessed this strange include methods, does someone have an > idea how I could solve my problem? You could move instrdeps.rule to your current directory which probably is application/models/BD or you could give the relative path to ../../services/makerules/instrdeps.rule > Note: I have to use relative paths That is usually a good idea as it makes your source tree relocatable. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: r...@localhost postmas...@localhost
