Re: [anjuta-devel] symbol-db progress



Hi all,

                 في ن، 31-01-2011 عند 11:55 +0100 ، كتب Johannes Schmid:
I've just committed my changes on system-db-refactor.
I saw that you put a package-scanner on language-support-cpp-java
plugin. I was planning to add that code on symbol-db side, avoiding the
other  plugins to provide the list of files to scan and add them to db.
Would it be possible to move that CppPackageScanner at anjuta-pkg-config
 side so that it's usable from symbol-db?

Yes, I guess it would be better to move CppPackageScanner to libanjuta as
AnjutaPackageScanner. However, I would still like to provide the list of
files from language-support-cpp-java plugin because I might want to allow
the creating of custom packages and also some predefined
non-pkg-config ones (like libc).
If I understand correctly, this would also allow other language support
plugins to specify the files they want scanned, right? This would be
interesting for vala to parse vapis and maybe for javascript to parse
the girs that are used in that file/target. If this is correct, how
should I do to implement this?

btw, vala does also use pkg-config but the user doesn't need to see C
symbol names, so I think separating how pkg-config packages are handled
and determining which files are in a given package would be best. This
is probably also related to the project manager (which does show
packages and files in them).

Hope this makes sense,
Abderrahim





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]