|
Compile
#How to compile and install Vala Toys for GEdit PrerequisitesLast released version:
CompilingHaving installed the required dependecies, you can compile Vtg with this command if you downloaded the source tarball: ./configure --prefix="your home dir"/.gnome2/gedit/plugins --datadir="your home dir"/.gnome2/gedit/plugins make or with this if you checked out vtg from the svn repository: ./autogen.sh --prefix="your home dir"/.gnome2/gedit/plugins --datadir="your home dir"/.gnome2/gedit/plugins make InstallingTo install for the current user, from the root folder of the Vtg distribution, do: mkdir ~/.gnome2/gedit/plugins/vtg cp -r images/ ~/.gnome2/gedit/plugins/vtg/ mkdir ~/.gnome2/gedit/plugins/vtg/ui cp ui/vtg.ui ~/.gnome2/gedit/plugins/vtg/ui/ cp vtg/vtg.gedit-plugin ~/.gnome2/gedit/plugins/ cp vtg/.libs/libvtg.so ~/.gnome2/gedit/plugins/ |
Sign in to add a comment
It should read "make", not "./make". Works fine otherwise, thank you. :-)
"./autogen.sh --prefix="your home dir"/.gnome2/gedit/plugins --datadir="your home dir"/.gnome2/gedit/plugins", not "./configure --prefix="your home dir"/.gnome2/gedit/plugins --datadir="your home dir"/.gnome2/gedit/plugins". Works fine otherwise, thank you. :-)
Just notice your comments after one month! I've updated the documentation.
Thanks to both of you. Andrea
At the compilation of vsc-shell was an error, readline.h not found. I have installed readline from here http://tiswww.case.edu/php/chet/readline/rltop.html and the library has many errors of sintax. I have fixed the problem comment in vsccompletionshell.c the include and the lines 81 to 96, that containts two calls to this library(readline and add_history)
To clarify the above, if you downloaded a tarball, you need to run "./configure --prefix=..." since autogen.sh will not exist. If you synced from Subversion, you need to run "./autogen.sh --prefix=..." since configure will not exist. (This is typical for any package following the GNU Coding Standards.)
Downloaded from svn on Ubuntu-8.10 x86-64. Followed instructions but vtg/.libs/libvtg.so was never built. There weren't any build errors or make error either. It just simply didn't build it. Any ideas?
Vtg build is disabled because you missed some required dependency. You can see it at the end of the autogen/configure step.
This thread may helps you: http://groups.google.com/group/vtg-dev/browse_thread/thread/d3cd81f9dd317fc5
Hi, I successfully built vtg but after I installed it, the entry in the gedit plugins list is grayed out. I cannot seem to enable the plugin. I'm probably missing something simple...
Thanks for your help.
I had to: $ mkdir ~/.gnome2/gedit/plugins/vtg/ui and $ cp ui/vtg.ui ~/.gnome2/gedit/plugins/vtg/ui/ in order for the configure plugin dialog to be displayed.
@ajselvig I had the same problem with enabling the plugin in gedit.
When I ran gedit from the terminal I saw the following message despite the fact that I had installed libgtksourcecompletion1.0-0_0.5.2-0~vala1_amd64.deb from the vala team PPA in Ubuntu:
Turns out there was no library inside the .deb file just some docs so I found another version inside a fedora rpm here: http://rpm.pbone.net/index.php3/stat/4/idpl/11898432/com/gtksourcecompletion-0.5.2-1.fc11.x86_64.rpm.html#content
(Note this is the 64bit version google for 32bit version I think fedora is i586)
I converted this to .deb using alien:
sudo alien gtksourcecompletion-0.5.2-1.fc11.x86_64.rpm
Then I could just install the deb with a double click and the gedit plugin worked flawlessly
First time I did this I accidently used "sudo make install" so all the files whered own by root == didn't work well (the guide above is strange because it mentions "installs VTG for all users" so clearly it's meant to be possible to run it as root but the "make install" doesn't seem to chown the files?)
Second time I followed the instructions but the plugin didn't show up in gedit preferences dialog. When I looked in ~/.gnome2/gedit the makefile had put the files in:
This doesn't work because gedit doesn't traverse the subdirs (I think). When I copied the stuff in the plugins subdir up to the parent "plugins" dir then everything worked.
Okay, so I got the release version (0.4.1) running on a fresh install of Ubuntu 9.04. The one little hickup I had was that GEdit wasn't finding vala-gen-project (wasn't in the path), so I made a little startup script that has this before calling gedit:
PATH=$PATH:/home/andy/.gnome2/gedit/plugins/bin/
So, this seems to work and I can create a new project.
checking for readline/readline.h... yes checking for VTGPLUGIN... no configure: error: vtg-plugin dependencies
The same situation:
checking for VTGPLUGIN... no configure: error: vtg-plugin dependencies
Make crashes at vscsymbolcompletion.c There are lot of mistakes such as "variable tmp1 is undefined" How can I solve the problem?
@vperetokin I had the same problem, but I solved it by following the thread http://groups.google.com/group/vtg-dev/browse_thread/thread/d3cd81f9dd317fc5
Also, I checked out the latest version of vala and vtg (not source tar balls) and installed these packages: libgbf-1-dev, libgnomeui-dev, gnome-common
Finally, there were some errors in vtg-plugin compilation. Since I only wanted vala-gen-project so I disabled vtg-plugin: ./autogen.sh --prefix=/home/kari/.gnome2/gedit/plugins --datadir=/home/kari/.gnome2/gedit/plugins --disable-vtg-plugin
Hope this help!
I'm trying to install When I try and make vtg it automakes itself happily with very positive comments at the end of the configure: ---{ vtg 0.5.0 }--- prefix: /home/drop/.gnome2/gedit/plugins sysconfdir: ${prefix}/etc localstatedir: ${prefix}/var C Compiler: gcc CFLAGS: -g -O2 Vala Vapidir: /usr/share/vala/vapi Enable gen-project: yes Enable vsc library: yes Enable vtg: yes Enable vsc-shell: yes
, but when I make the thing, it ends with these errors: vtgoutputview.c: In function ‘vtg_output_view_on_textview_key_press’: vtgoutputview.c:250: error: ‘buffer_length1’ undeclared (first use in this function) vtgoutputview.c:250: error: (Each undeclared identifier is reported only once vtgoutputview.c:250: error: for each function it appears in.)
does anyone have any ideas what may be causing this?