Re: [anjuta-devel] Some problems

[Sébastien Granjoux <seb sfo free fr>]

Hi John,


It seems that I'm the most active developer on Anjuta at the moment and 
I spend almost no time on it, just doing a few releases and committing 
obvious patches. So I thank you for reporting these issues but I'm 
afraid I will not fix them at least in a near future.


Le 16/06/2015 17:44, John Coppens a écrit :
> - I just tried a minimal, generic C project, and wanted to add the gtk3 library
>    but could not (I needed a gtk3 project without all the extra, automatically
>    provided code):

I have just tried and it seems to work here. The issue is perhaps that 
you have missed one step. You need two step to do that: create a new 
modules (added in the configure.ac) and them add it to you target (in 
Makefile.am).

So
1. Click on Project->New Library in main menu by example
2. You get a dialog with a list of modules, normally empty, click on New 
library
3. You get a list of packet now, that should include gtk3 if it's 
installed correctly
4. Check gtk3, it propose automatically a module name GTK_ not very good 
but ok.
5. Click on Add to create a module
6. Now in the previous dialog you should have a new module GTK_ 
containing the gtk3 library
7. Select this module GTK_, check that you have the right target 
selected above (foobar_sample)
8. Then click on Add again to add this module to this target

You should have GTK__CFLAGS added to AM_CPPFLAGS and GTK__LIBS added to
foobar_sample_LDADD in the Makefile.am


> - There seem to be two syntaxes for AM_CPPFLAGS and LDFLAGS:
>    $(SOMEPKG_CFLAGS) and @SOMEPKG_CFLAGS@

It's quite different. $(SOMEPKG_CFLAGS) is a make variable, while 
@SOMEPKG_CFLAGS@ is a configure variable in Makefile.am.in file which is 
replaced to create the Makefile.am file by example.


>    Anjuta seems to get completely confused about these and starts inserting
>    $(SOMEPKG_CFLAGS) into other strings (like -DPACKAGE_DATA_DIR=\""$(pkgdatadir)"\")
>    rendering the Makefile.in useless, and I have to edit it by hand.

Yes, I just see in the generic C project that $(SOMEPKG_CFLAGS) is not 
written correctly. I think Anjuta is confused by the escape on double 
quote. Could you add a bug report about this, if it's not already done?


>    Note that this happens with a clean project from Anjuta, without any
>    manual editing of the Makefile.am.

The project created by the project wizard have nothing special for 
Anjuta as it's supposed to read any project. But obviously as the syntax 
is quite difficult there are some errors. I think the easiest solution 
is probably to modify the generic C project template to avoid using a 
syntax which confuse Anjuta.


> - I try to recommend Anjuta to my students (and usually succeed :)
>    When I receive their submissions, I generally want to open them in Anjuta
>    again - not just compile. Importing rarely works without doing some
>    combination of autoreconf/automake/aclocal/autoconf. Is there any workflow
>    to smoothen this process?

Opening the project and seeing the source files normally don't need to 
use autoreconf/automake/aclocal/autoconf.


> - For some reason I have not been able to pinpoint, a manual autoreconf in
>    a terminal window is necessary ('Reconfigure project' checkbutton doesn't
>    do the same).

Reconfigure project is normally calling autogen.sh, it should be 
equivalent to using autoreconf.


> I really appreciate Anjuta, and try to advocate its use... Just
> sometimes, these little annoyances get in the way of the 'user
> experience'.

Yes, thank, I know but the amount of development is really low at the 
moment.


Regards,

Sébastien