Re: [Anjuta-list] Project Import Problems....
- From: Sébastien Granjoux <seb sfo free fr>
- To: Rob Frohne <Rob Frohne wallawalla edu>
- Cc: anjuta-list lists sourceforge net
- Subject: Re: [Anjuta-list] Project Import Problems....
- Date: Tue, 08 Dec 2009 19:57:50 +0100
Hi Rob,
Rob Frohne a écrit :
Gnuradio is an autotools based project and is open source. A possible
difficulty for Anjuta is that it uses both python and C++. I suggest
you "git" it and see for yourself. Here are two links that will help
you understand the project architecture and how to git it, etc.
I have take a look at it. The problem is not the mix of C++ and python
which shouldn't be really an issue.
The problem is that the configure.ac script is written in a smart way
while the Anjuta parser is not so smart.
Basically, Anjuta parser finds directories where are the sources files
looking for AC_OUTPUT or AC_CONFIG_FILES in the configure.ac file and
SUBDIRS variables in Makefile.am. Then it looks *_SOURCES in all
Makefile.am found in these directories.
In gnuradio, all these directories are given dynamically, parsing custom
functions defined in config/*.m4.
The current parser in Anjuta doesn't expand functions and so see only
the few files declared in the configure.ac file which doesn't correspond
to directory containing source files.
The new parser doesn't expand functions neither at the moment. It could
be done in the future but I have more stuff to handle first like
include. Anyway, I will check again when the project parser will be more
advanced.
Honestly, I will be surprise than an IDE can parse such project. A work
around could be to check in every directory looking for files with know
source extension, like .c, .cxx, .h, .cpp, .py... It is something that I
have planned to do when the new project manager will be ready for
supporting even smarter project using plain Makefile.
Regards,
Sébastien
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]