Re: [Anjuta-list] Tools editor

[Erwan BECQUET <becquet cnam fr>]

Hi,

I just downloaded the last cvs-1.0.0 snapshot and tried to compile it,
what I must say is that I downloaded the two hours before snapshot and
everything went well :

I now have at least two errors :

1) First is in tagmanager so I don't know if it's related to Tool
editor, see output :

***********************************************************************
make[1]: Entre dans le répertoire `/tmp/anjuta/tagmanager'
source='args.c' object='args.o' libtool=no \
depfile='.deps/args.Po' tmpdepfile='.deps/args.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./include -I/usr/include/glib-1.2
-I/usr/lib/glib/include  -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2
-I/usr/lib/glib/include -I/usr/X11R6/include  -g -O2 -c `test -f args.c
|| echo './'`args.c
In file included from args.c:16:
/usr/include/stdio.h:80: warning: empty declaration
In file included from args.c:22:
main.h:77: parse error before `__extension__'
make[1]: *** [args.o] Erreur 1
make[1]: Quitte le répertoire `/tmp/anjuta/tagmanager'
make: *** [all-recursive] Erreur 1
***********************************************************************

2) Second is in src, on a file called anjuta-tools.c so I guess it's
related to tool-editor ;-) see output :

***********************************************************************
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../intl -I/usr/include/gnome-1.0
-DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/orbit-1.0
-I/usr/include/gtk-1.2 -I/usr/X11R6/include -I/usr/include/gnome-vfs-1.0
-I/usr/lib/gnome-vfs-1.0/include -I/usr/include/gnome-xml
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/orbit-1.0
-I/usr/include/gconf/1 -I/usr/include/gtk-1.2 -I/usr/X11R6/include
-D_REENTRANT -I/usr/include/gnome-1.0 -I/usr/include/freetype2
-DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include
-I/usr/include/gdk-pixbuf-1.0 -I/usr/include/libglade-1.0 
-I./../scintilla/include -I./../tagmanager/include -I./../widgets
-I./../pixmaps -I./../printing -I.. -I.
-DPACKAGE_BIN_DIR=\"/usr/local/bin\"  -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include  -g
-O2 -c `test -f anjuta-tools.c || echo './'`anjuta-tools.c
anjuta-tools.c: In function `anjuta_tools_load':
anjuta-tools.c:497: `PACKAGE_DATA_DIR' undeclared (first use in this
function)
anjuta-tools.c:497: (Each undeclared identifier is reported only once
anjuta-tools.c:497: for each function it appears in.)
anjuta-tools.c: In function `anjuta_tools_edit':
anjuta-tools.c:621: `PACKAGE_DATA_DIR' undeclared (first use in this
function)
anjuta-tools.c: In function `show_tool_editor':
anjuta-tools.c:815: `PACKAGE_DATA_DIR' undeclared (first use in this
function)
make: *** [anjuta-tools.o] Erreur 1
***********************************************************************

if you could help, I'm dyning to use the tool-editor feature :-)
And btw, thanks all for the work on anjuta which I and my team use
everyday at work and which I use personally at home too !

Erwan.


Le mer 11/12/2002 à 12:28, Biswapesh Chattopadhyay a écrit :
> Guys:
> 
> I've checked in the tools editor GUI which I feel is currently
> sufficiently feature-rich for most simple tools applications. Some of
> the (more esoteric) features do not work currently - however, that can
> probably wait while we stabilize the basic tools framework. 
> 
> Currently, you can define tools with variable arguments, menu locations,
> working directories and output/error redirection. The GUI (IMO) is
> reasonably intuitive (though I'd like to add a list of variables you can
> use), so adding new tools should be easy for most users. You can use all
> the variables you use in Settings->Commands and other properties files.
> 
> It would be nice if people could test it (It's under Settings->Tools
> Editor) before we release 1.0.1. Hopefully, we'll be able to use the
> tools framework to satisfy lots of 'local' requirements.
> 
> Oh yes, and another thing - I've used Glade/Libglade for the GUI -
> Ithough it was high time we started some decent segregation of the code
> from the GUI. This, off course, adds a new dependency libglade (and
> libglade-devel if you want to compile from sources/SRPMs) but they are
> fairly small and I guess most people would have them anyway.
> 
> Next in the pipeline are Python scripting Support and Automake manager,
> but I guess they will have to wait for 1.0.2.
> 
> Thanks and regards,
> Biswa.
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Anjuta-list mailing list
> Anjuta-list lists sourceforge net
> https://lists.sourceforge.net/lists/listinfo/anjuta-list
-- 
 ("`-''-/").___..--''"`-._          Erwan Becquet
  `6_ 6  )   `-.  (    ).`-.__.`)   http://cedric.cnam.fr/~becquet/
  (_Y_.)'  ._   )  `._ `.``-..-'    -
(il),-''  (li),'  ((!.-'            becquet cnam fr