how to get xvidcap functioning under porteus

Non release banter
User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

how to get xvidcap functioning under porteus

Post#1 by francois » 01 Dec 2013, 01:50

I have tried to get xvidcap, a video recording capture program, working under porteus. It is available under slackware:
http://slackware.org.uk/slacky/slackwar ... cap/1.1.7/

Just downloading the package and then turning it into a xzm module does not seem enough. Checking with slackyd for dependencies reports no missing dependencies:

Code: Select all

root@porteus:~# slackyd -d xvidcap-1.1.7

Checking xvidcap-1.1.7-i486-1sl: done.

All packages "xvidcap-1.1.7" checked are ok !

root@porteus:~# 
Trying to start it up from command line, I get:

Code: Select all

root@porteus:~# xvidcap
bash: /usr/bin/xvidcap: No such file or directory
root@porteus:~# 
Looking at the /src/slack-required, I get :

Code: Select all

atk >= 1.32.0-i486-1
cairo >= 1.10.2-i486-2
cxxlibs >= 6.0.14-i486-1 | gcc-g++ >= 4.5.2-i486-2
dbus >= 1.4.1-i486-1
dbus-glib >= 0.88-i486-1
expat >= 2.0.1-i486-2
fontconfig >= 2.8.0-i486-1
freetype >= 2.4.4-i486-1
gcc >= 4.5.2-i486-2
gdk-pixbuf2 >= 2.23.3-i486-1
glib2 >= 2.28.6-i486-1
glibc-solibs >= 2.13-i486-4
gtk+2 >= 2.24.4-i486-1
lame >= 3.98.4-i486-3sl
libICE >= 1.0.7-i486-1
libSM >= 1.2.0-i486-1
libX11 >= 1.4.3-i486-2
libXau >= 1.0.6-i486-1
libXcomposite >= 0.4.3-i486-1
libXcursor >= 1.1.11-i486-1
libXdamage >= 1.1.3-i486-1
libXdmcp >= 1.1.0-i486-1
libXext >= 1.2.0-i486-1
libXfixes >= 5.0-i486-1
libXi >= 1.4.2-i486-1
libXinerama >= 1.1.1-i486-1
libXmu >= 1.1.0-i486-1
libXrandr >= 1.3.1-i486-1
libXrender >= 0.9.6-i486-1
libXt >= 1.1.1-i486-1
libglade >= 2.6.4-i486-4
libpng >= 1.4.5-i486-1
libxcb >= 1.7-i486-1
libxml2 >= 2.7.8-i486-3
pango >= 1.28.4-i486-1
pixman >= 0.20.2-i486-1
util-linux >= 2.19-i486-1
yelp >= 2.30.1-i486-5sl
zlib >= 1.2.5-i486-4
I know that these are necessary to build from source, could some of them be important for the functioning of the package?

Or is it simply that this is a gtk2+ application as stipulated in the xvidcap-1.1.7-i486-1sl.txt file:

Code: Select all

xvidcap: Xvidcap (GTK2+ Screen Capture Tool)
xvidcap:
xvidcap: Xvidcap is a screen  capture  enabling  you  to capture  videos off
xvidcap: yourX-Window desktop for illustration or documentation purposes. It
xvidcap: is intended to be a standards-based alternative to tools like Lotus
xvidcap: ScreenCam.
xvidcap:
xvidcap:
xvidcap:
xvidcap:
xvidcap:
Thus maybe running under the gnome enviroment?

Could PPM resolve missing dependencies if instead of using slackware 14.0, it would be using slackware 13.37?

Any clarification or suggestion would be appreciated.
Thanks. :)
Prendre son temps, profiter de celui qui passe.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: how to get xvidcap functioning under porteus

Post#2 by fanthom » 01 Dec 2013, 07:20

a) if you are using 64bit porteus then please download 64bit packages and not 32bit ones
b) you should not use packages from older slackware version as older libs may destroy your current system
c) if you want to use package from older slackware which is not present in current then simply grab a slackbuild for it and compile from sources (sometimes this wont work as code may be simply too old/require additional patches):
http://repository.slacky.eu/slackware64 ... 1.1.7/src/

general slackbuilds HOWTO:
http://slackbuilds.org/howto/
compilation from salckbuilds is very easy (nearly automated).
Please add [Solved] to your thread title if the solution was found.

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: how to get xvidcap functioning under porteus

Post#3 by francois » 01 Dec 2013, 16:29

@fanthom:

I do not get very often to build from source more complicated packages. I need to be more systematic and organized. Your patience is appreciated.

Thanks for the instructions.
Prendre son temps, profiter de celui qui passe.

User avatar
Slaxmax
Contributor
Contributor
Posts: 408
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: how to get xvidcap functioning under porteus

Post#4 by Slaxmax » 16 Dec 2013, 13:37

I tested this package in kde4 works fine. No problems with dependencies.
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#5 by wread » 17 Dec 2013, 00:11

@francois
Try kde4, my xvidcap works flawlessly :D
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#6 by wread » 17 Dec 2013, 00:56

My kde4 is not bloated, my footprint says 379.5 MiB/1.1 GiB, what says yours?
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#7 by wread » 17 Dec 2013, 01:18

Everything is not loaded, otherwise your xvidcap would be functioning ok. Mine does..... 8)
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#8 by wread » 17 Dec 2013, 02:08

Do as I say and you won't miss it! 8)
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#9 by wread » 17 Dec 2013, 11:41

Oh!, I see you can do without xvidcap! :Search:
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: how to get xvidcap functioning under porteus

Post#10 by francois » 17 Dec 2013, 12:06

@slaxmax and wread:
Do you mean that you did not have to add dependencies at all under kde?

@Peter:
Thanks a lot for that package building lesson. It is much appreciated. Really. I used some similar approach but invoked each dependency thru slackyd instead of looking for them in /usr/lib or /usr/lib64. I imagine that the process of deleting each txz and transforming each package to xzm could be automated. Do you have some script at hand?
Prendre son temps, profiter de celui qui passe.

User avatar
Slaxmax
Contributor
Contributor
Posts: 408
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: how to get xvidcap functioning under porteus

Post#11 by Slaxmax » 17 Dec 2013, 19:51

francois wrote:@slaxmax and wread:
Do you mean that you did not have to add dependencies at all under kde?
Exactly :D
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

User avatar
wread
Module Guard
Module Guard
Posts: 1255
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v5.0-kde-64 bits
Location: Santo Domingo
Contact:

Re: how to get xvidcap functioning under porteus

Post#12 by wread » 18 Dec 2013, 01:12

Genau! :D
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Re: how to get xvidcap functioning under porteus

Post#13 by francois » 19 Dec 2013, 02:48

wread wrote:Genau! :D
Ah! Précisément! Je comprends. Merci. :D
Prendre son temps, profiter de celui qui passe.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: how to get xvidcap functioning under porteus

Post#14 by Ahau » 19 Dec 2013, 06:41

Francois,

Did you try re-downloading the package? I just tested it in 2.1 XFCE and it seemed to work fine. I'm wondering if maybe you got a partial download. The error message you got at first, "bash: /usr/bin/xvidcap: No such file or directory" is an odd one, because xvidcap would have to be present in the $PATH before bash would know to call xvidcap from /usr/bin/xvidcap. I've seen this very error when compiling stuff for ARM when I mix binaries compiled for incompatible architectures, which I believe is why fanthom started off his post asking if you were running a 64-bit package on a 32-bit system (or vice versa). This is not a QT dependency issue nor a GTK2 vs 3 issue (xvidcap is a gtk2 program, and gtk2 is included in all editions of porteus).

If re-downloading and installing the package doesn't work, give us the output of the following:

ldd /usr/bin/xvidcap

and

file /usr/bin/xvidcap

ldd is short for "list dynamic dependencies" and will tell us if there are any missing libraries. file will tell us what kind of a file this is, e.g.:
/usr/bin/xvidcap: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped


As fanthom said, it's better to compile from source against the current system to ensure compatibility. Compiling is not as daunting as it seems at first, and won't require the level of depth that phpro explained above, with looking at each library on an individual basis (that will undoubtedly teach you more about your system and allow you to create smaller and more customized modules but it's not necessary to get started with compiling). I wouldn't start with xvidcap as it's old source code, there's no slackbuild on SBo; the one I found was from alienbob in 2008 and would require patching to work with the newer glib. If there's interest in this package, I could put together a patch for it; I think folks have moved more to recordmydesktop or some other software for screen capture.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: how to get xvidcap functioning under porteus

Post#15 by fanthom » 19 Dec 2013, 07:41

Porteus gives you a power to organize your modules as you want. unfortunately this ability is it's curse at the same time (which is proven in this and many other threads) as unexperienced users are mixing ARCHs and REPOs then posting on the forum that something doesn't work.

i have an idea for next release: lets get rid of modules totally and stick to installpkg+save.dat. no activate/deactivate and every installatoion done through PPM. this way users wont be able to mess with xzm's and everything will just work like on every other linux distros.
Please add [Solved] to your thread title if the solution was found.

Post Reply