Discussion:
parser does not exclude build directory
Yavuz Mert
2016-04-22 11:15:41 UTC
Permalink
Hi all,
I have a problem in kdevelop5 beta 2,
I occasionally use "make package_source" to prepare a source package (tgz) in
cmake build directory, which copies the source files in a "_CPack_Packages"
directory inside the build directory. After that kdevelop parser use those
files also. And then "Code browser", "Show Uses" etc. navigate to those files,
which are actually duplicates of the original sources.

Maybe the best option would be to exclude the build directory totally for the
parser automatically. But then, parser may not work for the cmake-generated,
configured files which are intentionally put in build directory.

Is there a manual method to set exclude directories for the parser -similar to
that used for 'find in files'
Or should I file a bug report.

Thanks,

yavuz
Matthew Woehlke
2016-04-22 14:41:20 UTC
Permalink
Post by Yavuz Mert
I occasionally use "make package_source" to prepare a source package (tgz) in
cmake build directory, which copies the source files in a "_CPack_Packages"
directory inside the build directory. After that kdevelop parser use those
files also. And then "Code browser", "Show Uses" etc. navigate to those files,
which are actually duplicates of the original sources.
Maybe the best option would be to exclude the build directory totally for the
parser automatically. But then, parser may not work for the cmake-generated,
configured files which are intentionally put in build directory.
As you note, this is somewhat a feature. It would be nice if KDevelop
were smart enough to ignore duplicates, though. I think it could do that
by default, without needing an option.
--
Matthew
Milian Wolff
2016-04-24 12:58:50 UTC
Permalink
Post by Yavuz Mert
Hi all,
I have a problem in kdevelop5 beta 2,
I occasionally use "make package_source" to prepare a source package (tgz)
in cmake build directory, which copies the source files in a
"_CPack_Packages" directory inside the build directory. After that kdevelop
parser use those files also. And then "Code browser", "Show Uses" etc.
navigate to those files, which are actually duplicates of the original
sources.
Maybe the best option would be to exclude the build directory totally for
the parser automatically. But then, parser may not work for the
cmake-generated, configured files which are intentionally put in build
directory.
Is there a manual method to set exclude directories for the parser -similar
to that used for 'find in files'
Or should I file a bug report.
Please file a bug report and also give us more information on how to
reproduce. Best is to attach a CMake project that exhibits this issue.

One assumption I have is that you have a structure like:

foo/
foo/sources...
foo/build/...

correct? If so, you can right-click on the build folder and "exclude it from
project".

HTH
--
Milian Wolff
***@milianw.de
http://milianw.de
Loading...