[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-patch] Hyperlink Navigation for 2.0
|
cdt-patch-admin@xxxxxxxxxxx wrote on 12/08/2003 06:12:20 PM:
>
> When you say dependencies, do you mean project references? If yes,
> then I'm not sure if this
> is correct. I always thought that Project A referencing Project B
> means that Project B's build output
> is a prerequsite for building Project A...and that's all. Any
> Project B include file paths that are used
> by Project A still need to be entered in Project A.
It would be cool if we also took care of everything needed to use the
build output of project B as well. That would include setting the
appropriate inclusion paths as well as link arguments. I'm not sure we're
in a position to do that, though.
>
> I changed it so that if more than one file is found amongst the
> include paths/project, the user can say which one he really wants. I
> thought that since we're not giving truly accurate results, we might
> as well give them all the results.
That's reasonable. Without an accurate picture of the exact inclusion path
used to parse a file, we're going to have to let the user tell us which
file to open. The only time I've really seen files with the same name are
in multi-target scenarios where you'll have different includes depending
on which target you are building for. Asking the user to choose shouldn't
be unexpected.
D
