search

sejerpz / vtg

Automatically exported from code.google.com/p/vtg
0 stars 0 forks source link

Can't compile libafrodite alone #135

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
From the compile page wiki comments:

Comment by TwilightInZero, May 31, 2010

How would I go about compiling and installing only libafrodite, so that I can 
use it with monodevelop?

Original issue reported on code.google.com by seje...@gmail.com on 9 Jun 2010 at 4:25

GoogleCodeExporter commented 9 years ago 
Try using the -disable-gen-project and --disable-vtg-plugin in the configure, 
it should work but I never tried it

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:25

GoogleCodeExporter commented 9 years ago 
Comment by TwilightInZero, Jun 01, 2010
That's what I'm doing, but it doesn't work. I get this interesting output:

Making all in gen-project
make[2]: Entering directory 
`/home/trent/Source/afrodite-svn/src/vtg-svn/gen-project'
Making all in libgen-project
make[3]: Entering directory 
`/home/trent/Source/afrodite-svn/src/vtg-svn/gen-project/libgen-project'
make[4]: Entering directory 
`/home/trent/Source/afrodite-svn/src/vtg-svn/gen-project/libgen-project'
  VALAC  libgen_project_la_vala.stamp
  CC     valaprojectgenerator.lo
valaprojectgenerator.c:28:18: fatal error: glib.h: No such file or directory
compilation terminated.
It looks as if it's trying to compile gen-project anyways.

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:26

GoogleCodeExporter commented 9 years ago 
I think that I fixed the configure script: can you retry and verify if it works?

This are the new command switches to use: --disable-gen-project 
--disable-vtg-plugin --enable-afrodite

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:26

GoogleCodeExporter commented 9 years ago 
This time, compilation failed much sooner:

make[2]: Entering directory 
`/home/trent/Source/afrodite-svn/src/vtg-svn/afrodite'
/usr/bin/valac --Xcc "-D G_DISABLE_DEBUG" -C -H afrodite.h --library 
afrodite-1.0 --vapidir ../vapi --pkg gio-2.0 --pkg config --pkg vala-1.0 --pkg 
utils --basedir ../afrodite astmerger.vala astdumper.vala parser.vala 
symbol.vala symbolresolver.vala datatype.vala voidtype.vala 
sourcereference.vala sourcefile.vala ast.vala utils.vala completionengine.vala 
ellipsistype.vala queryoptions.vala queryresult.vala resultitem.vala 
constants.vala sourceitem.vala
/usr/bin/valac --Xcc "-D G_DISABLE_DEBUG" -C --vapidir ../vapi --vapidir ./ 
--pkg afrodite-1.0 --pkg gio-2.0 --pkg config --pkg vala-1.0 --pkg utils 
--basedir ../afrodite afroditetest.vala
error: afrodite-1.0 not found in specified Vala API directories or 
GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)

Comment by TwilightInZero, Today (11 hours ago)
P.S.: Thank you for your efforts. :)

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
can you do a clean compilation? I see no reason why afroditetest doesn't found 
the vapi.

For clean I mean:

1) rerun ./autogen.sh with your options 
2) make clean; rm */*.stamp; make
Thanks

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
Comment by TwilightInZero, Today (5 hours ago)
Okay. After some more testing, I figured out that it's failing when the prefix 
is set. When I remove the --prefix=/usr option, it starts working. I can't make 
an Arch PKGBUILD without this option.

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:27

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I'm sorry but I can't reproduce your bug.

This is waht I've done to try to reproduce it:

1) checkout a fresh copy of vtg from the svn repos (trunk HEAD)
2) ./autogen.sh
3) ./configure --prefix=/usr --disable-vtg-plugin --disable-gen-project 
--enable-afrodite
4) make

Afrodite & afrodite test build fine here.

Original comment by seje...@gmail.com on 9 Jun 2010 at 4:38

GoogleCodeExporter commented 9 years ago 
I don't understand what the problem is here either. Maybe it's something the 
stupid autotools are doing, like discrepancies between different version. I use 
waf for my projects, because I hate the complexity of autotools.

Your configure script (and other stuff made by autogen.sh) is obviously 
working. Maybe you should distribute it (them) along with the source?

Original comment by Twilight...@gmail.com on 9 Jun 2010 at 8:07

GoogleCodeExporter commented 9 years ago 
Can you try if the configure from this tarball works on your system?

Btw now I'm leaving for a quick trip, so I'll be back on next wednesday.

Original comment by seje...@gmail.com on 11 Jun 2010 at 5:42

Attachments:

GoogleCodeExporter commented 9 years ago 
Yeah, the configure from that tarball worked perfectly. You should probably 
include your configure script in SVN so that everyone building from SVN can 
have a consistent compilation experience. Doesn't seem to be possible if we 
just depend on autohell's unpredictable output across different versions.

Original comment by Twilight...@gmail.com on 11 Jun 2010 at 5:54

GoogleCodeExporter commented 9 years ago 
I've included the configure script and some support file in the repository rev. 
599.

Can you check if recompiling vtg as described in the "Alternative method" of 
the compile page works for you?

Original comment by seje...@gmail.com on 19 Jun 2010 at 8:32

GoogleCodeExporter commented 9 years ago

Original comment by seje...@gmail.com on 3 Aug 2010 at 2:16

GoogleCodeExporter commented 9 years ago 
I still get this error with trunk using the suggested compile commands above. I 
am on Ubuntu Lucid x64.

checking pkg-config is at least version 0.9.0... yes
checking for GLIB... yes
checking for AFRODITE... no
afrodite library dependencies not met:
    vala-0.10 >= 0.9.4: not found
configure: error: afrodite library dependencies not met: glib-2.0 >= 2.12.0 
gio-2.0 >= 2.12.0 gobject-2.0 >= 2.12.0 gthread-2.0 >= 2.16.0 vala-0.10 >= 0.9.4

Original comment by chris...@gmail.com on 8 Aug 2010 at 6:51

GoogleCodeExporter commented 9 years ago 
Yes that's true, I'm sorry but to compile vtg trunk you need vala trunk. I know 
that we are near a vala release (it should be released today) so I hope that 
this inconvenience will be valid for just a few days.

Original comment by seje...@gmail.com on 8 Aug 2010 at 10:13

GoogleCodeExporter commented 9 years ago 
I forget to mention that the last revision that should be compilable with vala 
0.9.4 is r687

Original comment by seje...@gmail.com on 8 Aug 2010 at 10:18

GoogleCodeExporter commented 9 years ago 
@sejerpz
Where do you have to put your libafrodite.so file in order to work with 
monodevelop?

I'm getting a "Cannot update Vala parser database because libafrodite (VTG) is 
not installed" error message.

This plugin didn't work (at first) with gedit either. After make install I had 
to manually copy the libafrodite.so files from /usr/local/lib to /usr/lib (+ 
the gedit plugin files too from /usr/local/lib to /usr/lib).

What am I doing wrong?

Original comment by albertma...@gmail.com on 13 Dec 2010 at 10:04

GoogleCodeExporter commented 9 years ago 
same here. who knows where to put the afrodite.so library to make it work with 
monodevelop?

Original comment by julak...@gmail.com on 15 Mar 2011 at 9:26

GoogleCodeExporter commented 9 years ago 
I'm not the mantainer of monodevelop vala plugin, but I will try to put 
libafrodite.so in /usr/lib

Or better compile and install just afrodite:

./configure --prefix=/usr --disable-vtg-plugin --disable-gen-project 
--disable-debug
make
make install

Another note: I don't think monodevelop vala is still compatible with the 
current afrodite library api/abi

Original comment by seje...@gmail.com on 15 Mar 2011 at 9:36