| automake 1.9 troubling code assist (discovery) [message #175342] |
Wed, 23 August 2006 17:34  |
Eclipse User |
|
|
|
Originally posted by: fraco.nospaam_yahoo.com
Hi,
I had trouble with content assist not working for a standard Makefile
project with autotools makefiles.
Apparantly the automake 1.9 generates Makefiles that come up with
following type of build output:
<snippet>
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtkmm-2.4
-I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4
-I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4
-I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4
-I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0
-I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo
-I/usr/include/atk-1.0 -g -O2 -MT pictureTag.o -MD -MP -MF
".deps/pictureTag.Tpo" -c -o pictureTag.o pictureTag.cpp; \
then mv -f ".deps/pictureTag.Tpo" ".deps/pictureTag.Po"; else rm -f
".deps/pictureTag.Tpo"; exit 1; fi
</snippet>
notice the if...then construct
The code assist features would not work for most of those external
libraries and the discovery paths didn't show any of those on the path.
After downgrading to automake-1.4 the conditional stuff disappeared
from the build output and suddenly the discovery and code assist worked
(no more if....then, just plain compile statements)
so, in short:
* the conditional stuff in the build output when using automake 1.9
gives the discovery feature trouble discovering any of the paths -> is
this a cdt bug? *
workaround: automake 1.4
at least, that is my understanding of the problem.
Tim
|
|
|
| Re: automake 1.9 troubling code assist (discovery) [message #175649 is a reply to message #175342] |
Wed, 30 August 2006 06:17  |
| Eclipse User |
|
|
|
Originally posted by: jamesblackburn+ngnospam.gmail.com
This is a bug in the Build Output parser. Please file a bug report at
bugs.eclipse.org. Also state whether you were using the per file
scanner profile or per project.
Cheers,
James
Tim Froidcoeur wrote:
> Hi,
>
> I had trouble with content assist not working for a standard Makefile
> project with autotools makefiles.
> Apparantly the automake 1.9 generates Makefiles that come up with
> following type of build output:
>
> <snippet>
> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtkmm-2.4
> -I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4
> -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4
> -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4
> -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0
> -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo
> -I/usr/include/atk-1.0 -g -O2 -MT pictureTag.o -MD -MP -MF
> ".deps/pictureTag.Tpo" -c -o pictureTag.o pictureTag.cpp; \
> then mv -f ".deps/pictureTag.Tpo" ".deps/pictureTag.Po"; else rm -f
> ".deps/pictureTag.Tpo"; exit 1; fi
> </snippet>
>
> notice the if...then construct
>
> The code assist features would not work for most of those external
> libraries and the discovery paths didn't show any of those on the path.
> After downgrading to automake-1.4 the conditional stuff disappeared from
> the build output and suddenly the discovery and code assist worked (no
> more if....then, just plain compile statements)
>
> so, in short:
>
> * the conditional stuff in the build output when using automake 1.9
> gives the discovery feature trouble discovering any of the paths -> is
> this a cdt bug? *
>
> workaround: automake 1.4
>
> at least, that is my understanding of the problem.
>
> Tim
|
|
|
Powered by
FUDForum. Page generated in 0.05791 seconds
Home