Thread: Re: [Vimprobable-users] install newbee problem
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
From: Ludo B. <la...@gm...> - 2013-02-24 20:37:33
|
Thanks Hannes, ok, I'm getting closer, but there's no cigar yet ;-) Synaptic didn't find any libgtk+... so I took libgtk-3-dev, which did mention something about "+" in the description. After downloading the other 2 necessary files, here's how far I got: ludo@ludo-IXLs ~/Downloads/tarballs/vimprobable2 $ make cc -MMD -c `pkg-config --cflags gtk+-2.0 webkit-1.0 libsoup-2.4` -D_XOPEN_SOURCE=500 callbacks.c -o callbacks.o perl ./js-merge-helper.pl cc -MMD -c `pkg-config --cflags gtk+-2.0 webkit-1.0 libsoup-2.4` -D_XOPEN_SOURCE=500 main.c -o main.o cc -MMD -c `pkg-config --cflags gtk+-2.0 webkit-1.0 libsoup-2.4` -D_XOPEN_SOURCE=500 utilities.c -o utilities.o utilities.c: In functie ‘complete_list’: utilities.c:567:17: let op: ‘g_strdown’ is deprecated (declared at /usr/include/glib-2.0/glib/gstrfuncs.h:179) [-Wdeprecated-declarations] cc callbacks.o main.o utilities.o `pkg-config --libs gtk+-2.0 webkit-1.0 libsoup-2.4` -lX11 -lXext -o vimprobable2 I guess the "deprecated" mention is still problematic? Ludo |
From: Ludo B. <la...@gm...> - 2013-02-25 17:23:35
|
Hannes, I wasn't attentive enough when I did this and accidentally first did "make install" instead of first clicking the executable. I don't know if it matters? Anyhow, vimprobable is working now! I'm not sure, can I simply move the directory to another place? I thought of making a "bin" directory in home and put it there instead of leaving it in my "Downloads" folder. Like I said, I'm used to install stuff via Synaptic mainly - so sorry for the newbee ignorance and thanks for your patience :-) There were some warning and error messages when starting vimprobable from terminal. I've also included the output of the "make install", just in case it means more: ludo@ludo-IXLs ~/Downloads/tarballs/vimprobable2 $ sudo make install [sudo] password for ludo: [ -e '///usr/local/bin' ] || mkdir -p '///usr/local/bin' && chmod 0755 '///usr/local/bin' cp -f 'vimprobable2' '///usr/local/bin/vimprobable2' strip -s '///usr/local/bin/vimprobable2' chmod 0755 '///usr/local/bin/vimprobable2' [ -e '///usr/local/share/man/man1' ] || mkdir -p '///usr/local/share/man/man1' && chmod 0755 '///usr/local/share/man/man1' cp -f 'vimprobable2.1' '///usr/local/share/man/man1/vimprobable2.1' chmod 0644 '///usr/local/share/man/man1/vimprobable2.1' [ -e '///usr/local/share/man/man5' ] || mkdir -p '///usr/local/share/man/man5' && chmod 0755 '///usr/local/share/man/man5' cp -f 'vimprobablerc.5' '///usr/local/share/man/man5/vimprobablerc.5' chmod 0644 '///usr/local/share/man/man5/vimprobablerc.5' ludo@ludo-IXLs ~/Downloads/tarballs/vimprobable2 $ cd ludo@ludo-IXLs ~ $ vimprobable2 Cannot open /home/ludo/.config//vimprobable/scripts.js: file not found No bp log location saved, using default. [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:000] Using Gtk2 toolkit [000:008] Warning(optionsfile.cc:47): Load: Could not open file, err=2 [000:008] No bp log location saved, using default. [000:008] Browser XEmbed support present: 1 [000:008] Browser toolkit is Gtk2. [000:008] Using Gtk2 toolkit java version "1.7.0_15" OpenJDK Runtime Environment (IcedTea7 2.3.7) (7u15-2.3.7-0ubuntu1~12.04) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) ** Message: console message: undefined @0: ReferenceError: Can't find variable: pageTracker > > Date: Sun, 24 Feb 2013 21:46:34 +0100 > From: Hannes Sch?ller <ha...@yl...> > Subject: Re: [Vimprobable-users] install newbee problem > To: vim...@li... > Message-ID: <20130224214634.7a6a0559@workstation> > Content-Type: text/plain; charset=US-ASCII > > Ludo Beckers <la...@gm...> wrote: > > I guess the "deprecated" mention is still problematic? > > No. You should have a working vimprobable2 binary in your > working directory now. Try running it. If it works, make install. > > The warning comes from building against GTK3 instead of GTK2. > Deprecation simply means that a future version of the library *might* > drop support for the function. > > Hannes > > > |
From: Hannes S. <ha...@yl...> - 2013-02-25 19:05:09
|
Hi Ludo, most of your questions are not really Vimprobable specific. I will try to answer them and I hope the other subscribers won't mind going off-topic a little. Ludo Beckers <la...@gm...> wrote: > I'm not sure, can I simply move the directory to another place? You can move the binary anywhere you like. It would make sense to include the location in your $PATH environment variable, though. That means it can be called from anywhere without specifying the full path. > I've also included the output of the "make install", just in case it > means more: > > ludo@ludo-IXLs ~/Downloads/tarballs/vimprobable2 $ sudo make install > [sudo] password for ludo: > [ -e '///usr/local/bin' ] || mkdir -p '///usr/local/bin' && chmod 0755 > '///usr/local/bin' > cp -f 'vimprobable2' '///usr/local/bin/vimprobable2' > strip -s '///usr/local/bin/vimprobable2' > chmod 0755 '///usr/local/bin/vimprobable2' > [ -e '///usr/local/share/man/man1' ] || mkdir -p > '///usr/local/share/man/man1' && chmod 0755 > '///usr/local/share/man/man1' cp -f 'vimprobable2.1' > '///usr/local/share/man/man1/vimprobable2.1' chmod 0644 > '///usr/local/share/man/man1/vimprobable2.1' [ -e > '///usr/local/share/man/man5' ] || mkdir -p > '///usr/local/share/man/man5' && chmod 0755 > '///usr/local/share/man/man5' cp -f 'vimprobablerc.5' > '///usr/local/share/man/man5/vimprobablerc.5' chmod 0644 > '///usr/local/share/man/man5/vimprobablerc.5' You have to understand what "make install" does. While "make" triggers the actual compilation/building of the application, "make install" is nothing but a copying process: the application itself and the manual are copied to default, system-wide accessible locations. These locations are specified in the Makefile (hence the first step of modifying it as described in the INSTALL file). The default is to put custom applications with the prefix /usr/local, i.e. the binary into /usr/local/bin and the manual in /usr/local/share/man. Those steps are printed for your convenience above. Meaning: By doing "make install", you have already moved the application away from your downloads directory. > ludo@ludo-IXLs > ~/Downloads/tarballs/vimprobable2 $ cd ludo@ludo-IXLs ~ $ > vimprobable2 Cannot open /home/ludo/.config//vimprobable/scripts.js: > file not found This simply means that you do not have custom scripts defined to be run inside the browser. This is just a feature which you don't need to use obviously (personally, I don't use it, either). If you simply want to get rid of this harmless message, I would suggest creating an empty file in the specified location (using the touch command). > No bp log location saved, using default. [000:000] > Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. > [000:000] Using Gtk2 toolkit > [000:008] Warning(optionsfile.cc:47): Load: Could not open file, err=2 > [000:008] No bp log location saved, using default. > [000:008] Browser XEmbed support present: 1 > [000:008] Browser toolkit is > Gtk2. > > [000:008] Using Gtk2 > toolkit > > java version > "1.7.0_15" > > OpenJDK Runtime Environment (IcedTea7 2.3.7) > (7u15-2.3.7-0ubuntu1~12.04) > > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed > mode) All that is printed on your terminal? Are you running some sort of debugger? Is that the original source or some modified version? If so, from where did you download it? Hannes |
From: Ludo B. <la...@gm...> - 2013-02-25 19:53:28
|
Hi Hannes I promise I won't make it a habit to go off topic, thanks for understanding. > It would make sense to include the location in your $PATH environment variable, though. I'll do some searching for How To's on that :-) Thanks also for the make vs makeinstall and the custom scripts explanation; very clear. > All that is printed on your terminal? Are you running some sort of debugger? Is that the original source or some modified version? If so, from where did you download it? I downloaded from https://launchpad.net/~serge-hallyn/+archive/vimprobable I choose "vimprobable2 1.2.0" if I remember correctly (I'm on LinuxMint13 btw). I don't know the first thing about debuggers so I really wouldn't know. Maybe it has to do with the -dev versions of the files mentioned in the INSTALL that you suggested earlier? Ludo |
From: Hannes S. <ha...@yl...> - 2013-02-24 20:46:48
|
Ludo Beckers <la...@gm...> wrote: > I guess the "deprecated" mention is still problematic? No. You should have a working vimprobable2 binary in your working directory now. Try running it. If it works, make install. The warning comes from building against GTK3 instead of GTK2. Deprecation simply means that a future version of the library *might* drop support for the function. Hannes |