How about a VideoLan DotPup?
- Bancobusto
- Posts: 168
- Joined: Mon 13 Jun 2005, 20:52
- Location: Vancouver Island
How about a VideoLan DotPup?
I don't know if this is possible due to dependency problems etc (?) but would it be possible to make a VLC dot pup?
The reason I'm wondering, is I had SimplyMepis installed on my machine last month (lasted about 5 days, I really don't like KDE) and I noticed that despite the super-poor performance of Mplayer and Realplayer, once I apt-get'd vlc I could watch movies full-screen no problem.
I noticed this with Windows 2000 as well... VLC could just play things that everything else couldn't. Maybe just my machine? I don't know...
I would be willing to give it a whirl, I just am really new to the concept of compiling. I downloaded the vlc source and tried ./configure, but it said that a suitable c compiler wasn't found. Any suggestions for the the best C complier for Puppy? I'm sure that there will be other libraries etc. that I'll need for vlc, but it would give me something to work with.
Anyway, have to stop rambling on as though I know what I'm talking about (but I'm getting there, damn it!)...
Wish me luck, but in the meantime does anyone else feel up to the challenge?
The reason I'm wondering, is I had SimplyMepis installed on my machine last month (lasted about 5 days, I really don't like KDE) and I noticed that despite the super-poor performance of Mplayer and Realplayer, once I apt-get'd vlc I could watch movies full-screen no problem.
I noticed this with Windows 2000 as well... VLC could just play things that everything else couldn't. Maybe just my machine? I don't know...
I would be willing to give it a whirl, I just am really new to the concept of compiling. I downloaded the vlc source and tried ./configure, but it said that a suitable c compiler wasn't found. Any suggestions for the the best C complier for Puppy? I'm sure that there will be other libraries etc. that I'll need for vlc, but it would give me something to work with.
Anyway, have to stop rambling on as though I know what I'm talking about (but I'm getting there, damn it!)...
Wish me luck, but in the meantime does anyone else feel up to the challenge?
Freedom isn't just a Puppy-Linux forum member!
tcc is a pupget but from what i hear, i there aren't any GUI-based libraries available for puppy to use.
which leads me to believe that most (if not all) development for puppy has to happen in another OS... someone please prove me wrong, because that just sounds so wrong to me =P
which leads me to believe that most (if not all) development for puppy has to happen in another OS... someone please prove me wrong, because that just sounds so wrong to me =P
omg i wish i were more of a nerd... =[
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
zenkalia wrote: which leads me to believe that most (if not all) development for puppy has to happen in another OS... someone please prove me wrong, because that just sounds so wrong to me =P
It is pragmatic
Most users of Puppy are not developers. To include ALL development tools would make Puppy too large or take much required space.
A dotpup of a C GNU environment is not yet available. Tinycc is available. Gambas (Basic) is a pupget. Nasm (an assembler) is a dot pup. Tcl and bash programming is built in. You can develop in XUL or javascript and XHTML is quite a powerful potential . . . and download java as a dotpup and perhaps create a dotpup for this . . .
http://snapplatform.org/
Lua is available. Open Office I believe has a macro programming environment. So whilst you are awaiting development you have loads of development tools . . .
Hope some of that sounds right up your street . . .
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
zenkalia wrote: which leads me to believe that most (if not all) development for puppy has to happen in another OS... someone please prove me wrong, because that just sounds so wrong to me =P
It is pragmatic
Most users of Puppy are not developers. To include ALL development tools would make Puppy too large or take much required space.
A dotpup of a C GNU environment is not yet available. Tinycc is available. Gambas (Basic) is a pupget. Nasm (an assembler) is a dot pup. Tcl and bash programming is built in. You can develop in XUL or javascript and XHTML is quite a powerful potential . . . and download java as a dotpup and perhaps create a dotpup for this . . .
http://snapplatform.org/
Lua is available. Open Office I believe has a macro programming environment. So whilst you are awaiting development you have loads of development tools . . .
Hope some of that sounds right up your street . . .
Sadly Linux does not have the tools (Actionscript) to write an OS like this . . .
http://hackersplayground.org/humor/windows.swf
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
There is another tool worth pointing out, that being Bladehunter's opttools development package, found here-
http://www.murga.org/~puppy/viewtopic.php?t=1167
Although this is NOT for the faint of heart. Up until now most development for Puppy has taken place in Mandrake and more recently in Vector Linux. That is only now beginning to change.
Another possibility is to find an already compiled binary and use that instead. Binary rpm's for Mandrake work quite well, as do some Slackware tarballs. I've had good luck using packages designed for DSL, which you can find at ibiblio. I've actually gotten some really complex software to work this way. I think the first thing that you should try if you just want the program is search for a Mandrake rpm to use. Here's my favorite search-
http://rpm.pbone.net/index.php3/stat/2/simple/2
You will need the unrpm/undeb dotpup from on the wikka to extract the files. Hope you can get it going.
Nathan
PS-not that I want you to stop using Puppy, but you can use icewm with Mepis. I don't really like KDE either. Here's a thread that is very interesting.
http://www.mepis.org/node/599
http://www.murga.org/~puppy/viewtopic.php?t=1167
Although this is NOT for the faint of heart. Up until now most development for Puppy has taken place in Mandrake and more recently in Vector Linux. That is only now beginning to change.
Another possibility is to find an already compiled binary and use that instead. Binary rpm's for Mandrake work quite well, as do some Slackware tarballs. I've had good luck using packages designed for DSL, which you can find at ibiblio. I've actually gotten some really complex software to work this way. I think the first thing that you should try if you just want the program is search for a Mandrake rpm to use. Here's my favorite search-
http://rpm.pbone.net/index.php3/stat/2/simple/2
You will need the unrpm/undeb dotpup from on the wikka to extract the files. Hope you can get it going.
Nathan
PS-not that I want you to stop using Puppy, but you can use icewm with Mepis. I don't really like KDE either. Here's a thread that is very interesting.
http://www.mepis.org/node/599
- Bancobusto
- Posts: 168
- Joined: Mon 13 Jun 2005, 20:52
- Location: Vancouver Island
Thanks for the links, and for the responses.
I was kind of wondering that myself, the rpm's, hmmm...
Well, gotta get cracking, I guesse....
(computer's ears perk up at the sound of danger, dread broiling around on the inside.... OH...... N O O O ! >>>)
Wish me luck, and thanks for all the ideas. Cheers.
I was kind of wondering that myself, the rpm's, hmmm...
Well, gotta get cracking, I guesse....
(computer's ears perk up at the sound of danger, dread broiling around on the inside.... OH...... N O O O ! >>>)
Wish me luck, and thanks for all the ideas. Cheers.
Freedom isn't just a Puppy-Linux forum member!
VLC is the greatest
I know the thread's been around for a while but VLC really is the greatest.
I will give it a go myself when I have the time, although I am also new to Linux and compiling. I've being trying to compile HPLIP for my printer, but got lost most of the way there, and then discovered I didn't need it (HPIJS works).
I think for the compiling you want to get user_devx.sfs
I will give it a go myself when I have the time, although I am also new to Linux and compiling. I've being trying to compile HPLIP for my printer, but got lost most of the way there, and then discovered I didn't need it (HPIJS works).
I think for the compiling you want to get user_devx.sfs
Last edited by disciple on Wed 14 Jun 2006, 07:30, edited 1 time in total.
if you don't want to compile, both hplip & vlc are available at linuxpackages.net . you might have to play around with symlinking & checking for missing library files.
http://www.linuxpackages.net/pkg_details.php?id=8727
http://www.linuxpackages.net/pkg_details.php?id=8727
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
If you have a VIA Unichrome, Intel i810, or nVidia AGP graphics card, try Xine with XvMC hardware acceleration -Bancobusto wrote:I noticed that despite the super-poor performance of Mplayer and Realplayer, once I apt-get'd vlc I could watch movies full-screen no problem.
http://www.murga.org/~puppy/viewtopic.php?t=5701
It first requires the appropriate 3D driver for your card - from http://dotpups.de/tests/3D-DRI-wizard.pup
With graphics acceleration, the minimum processor requirement for fullscreen DVD playback is just 333MHz (Pentium2/K6-2).
Without graphics acceleration, the minimum processor required is approx 800MHz.
i downloaded vlc-0.8.4a-i486-4cl.tgz from linuxpackages.net &, when expanded, it's a whopping 12Mbytes. the output from "ldd vlc" is:
librt.so.1 => /lib/librt.so.1 (0x40017000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4002a000)
libdl.so.2 => /lib/libdl.so.2 (0x4007d000)
libdvbpsi.so.4 => not found
libz.so.1 => /lib/libz.so.1 (0x40092000)
libmatroska.so.0 => /usr/lib/libmatroska.so.0 (0x400a0000)
libebml.so.0 => /usr/lib/libebml.so.0 (0x40133000)
libavformat.so => /usr/lib/libavformat.so (0x40154000)
libavcodec.so => /usr/lib/libavcodec.so (0x401c9000)
libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0x40590000)
libfaad.so.0 => /usr/lib/libfaad.so.0 (0x40625000)
libfaac.so.0 => /usr/lib/libfaac.so.0 (0x40661000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x40671000)
libavutil.so => not found
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x40770000)
libm.so.6 => /lib/libm.so.6 (0x40797000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x407ba000)
libtheora.so.0 => /usr/lib/libtheora.so.0 (0x407be000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x407de000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x40895000)
libc.so.6 => /lib/libc.so.6 (0x4089e000)
/lib/ld-linux.so.2 (0x40000000)
libxvidcore.so.4 => /usr/lib/libxvidcore.so.4 (0x409bb000)
librt.so.1 => /lib/librt.so.1 (0x40017000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4002a000)
libdl.so.2 => /lib/libdl.so.2 (0x4007d000)
libdvbpsi.so.4 => not found
libz.so.1 => /lib/libz.so.1 (0x40092000)
libmatroska.so.0 => /usr/lib/libmatroska.so.0 (0x400a0000)
libebml.so.0 => /usr/lib/libebml.so.0 (0x40133000)
libavformat.so => /usr/lib/libavformat.so (0x40154000)
libavcodec.so => /usr/lib/libavcodec.so (0x401c9000)
libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0x40590000)
libfaad.so.0 => /usr/lib/libfaad.so.0 (0x40625000)
libfaac.so.0 => /usr/lib/libfaac.so.0 (0x40661000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x40671000)
libavutil.so => not found
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x40770000)
libm.so.6 => /lib/libm.so.6 (0x40797000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x407ba000)
libtheora.so.0 => /usr/lib/libtheora.so.0 (0x407be000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x407de000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x40895000)
libc.so.6 => /lib/libc.so.6 (0x4089e000)
/lib/ld-linux.so.2 (0x40000000)
libxvidcore.so.4 => /usr/lib/libxvidcore.so.4 (0x409bb000)
go here:
http://www.debian.org/distrib/packages
In the bottom entry, enter
libavutil.so
Choose "testing".
Proceed and download the deb.
Use undeb or the debian-installer.
Undeb is in the Dotpupdownloader, the debian-installer in Puppy2 (start it with pb-debianinstaller in a console).
Other puppys: http://www.murga.org/~puppy/viewtopic.php?t=6743
Mark
http://www.debian.org/distrib/packages
In the bottom entry, enter
libavutil.so
Choose "testing".
Proceed and download the deb.
Use undeb or the debian-installer.
Undeb is in the Dotpupdownloader, the debian-installer in Puppy2 (start it with pb-debianinstaller in a console).
Other puppys: http://www.murga.org/~puppy/viewtopic.php?t=6743
Mark
i downloaded the required libs, and when i ran ./vlc got some sort of display problem. searching on the videolan forum i came across this link:
http://pallansson.homeip.net/vlc/index.html
where he's compiled videolan, with all required libs, for slackware. it's
9.1Mbyte download, which expands to 26Mbytes on hard disk,(too big for this dialup-pup to do anything with!).
but if you download & extract, run the doinst,sh script, then just symlink "ln -s whatever_directory_you_extract_to/opt /root/.opt" ,
then the binary, vlc, in "../opt/vlc/bin" works straight away.
http://pallansson.homeip.net/vlc/index.html
where he's compiled videolan, with all required libs, for slackware. it's
9.1Mbyte download, which expands to 26Mbytes on hard disk,(too big for this dialup-pup to do anything with!).
but if you download & extract, run the doinst,sh script, then just symlink "ln -s whatever_directory_you_extract_to/opt /root/.opt" ,
then the binary, vlc, in "../opt/vlc/bin" works straight away.
disciple,
doinst.sh is just a script file to associate various library files by symlinking them. you can open it with a text editor to see what it's meant to do, although if you're not familiar with bash script it will just look like gibberish!
just change to the directory it's in, copy it one directory up, make it executable, then run it. in a console window do this by:
cp doinst.sh .. <enter>
chmod +x doinst.sh <enter>
./doinst.sh <enter>
then symlink the videolan opt directory to /root/.opt . this depends upon where you've extracted it to. Say you've done this to a directory /vlc, then you would do:
ln -s /vlc/opt /root/.opt <enter> NB it's to /root/.opt, not /root/opt
let us know if this works, or not.
doinst.sh is just a script file to associate various library files by symlinking them. you can open it with a text editor to see what it's meant to do, although if you're not familiar with bash script it will just look like gibberish!
just change to the directory it's in, copy it one directory up, make it executable, then run it. in a console window do this by:
cp doinst.sh .. <enter>
chmod +x doinst.sh <enter>
./doinst.sh <enter>
then symlink the videolan opt directory to /root/.opt . this depends upon where you've extracted it to. Say you've done this to a directory /vlc, then you would do:
ln -s /vlc/opt /root/.opt <enter> NB it's to /root/.opt, not /root/opt
let us know if this works, or not.
i'm using 1.08 at present. how are you running puppy? as bootable cd, option1 harddisk install or option2?
because if you were running option2, you would do:
ln -s /vlc/opt/vlc /root/.opt, whereas with CDpup it would be
ln -s /mnt/home/vlc/opt/vlc /root/.opt
also if you change to the directory /vlc/opt/vlc/bin & run following, what do you get?
ldd vlc to see what dependencies are missing, if any &:
./vlc to try & run it & see what errors you get.
because if you were running option2, you would do:
ln -s /vlc/opt/vlc /root/.opt, whereas with CDpup it would be
ln -s /mnt/home/vlc/opt/vlc /root/.opt
also if you change to the directory /vlc/opt/vlc/bin & run following, what do you get?
ldd vlc to see what dependencies are missing, if any &:
./vlc to try & run it & see what errors you get.
Here are some good links I ran across that might help those of you doing this:
http://www.tldp.org/guides.html
Last three on the very bottom of the page.
VideoLAN Quickstart
VLC (VideoLAN Client) User Guide
VLS (VideoLAN Server) User Guide
http://www.tldp.org/guides.html
Last three on the very bottom of the page.
VideoLAN Quickstart
VLC (VideoLAN Client) User Guide
VLS (VideoLAN Server) User Guide
Like I say, I'll have a decent try at getting it working in a week or so, after exams, but at the moment I'm missing eight dependencies (can't show you them now - I'm not there) - did you install a whole lot of these separately, or what? - maybe you have them from installing something else, or maybe its the puppy version? - I'll give it a go in 1.08 as well.
How to install vlc in Puppy
OK this is very easy.
I'm starting with a clean install of Puppy 1.08 - I think they call it a frugal install - with image.gz, vmlinuz and usr_cram.fs on a windows disk. (-this works on at least Puppy 1.08, 1.09, 2, I think in any form of install)
I put the Slackware package mentioned above (http://www.videolan.org/vlc/download-slackware.html) in this folder: /vlc -you can put it anywhere, but will have to modify all the things you do after this to take this into account. [I think with a live CD or frugal install of Puppy 1.x this will disappear when you reboot, as various parts of the filesystem are read-only - you can change them when they are in RAM, but not keep the changes - a save place to put it is /root/vlc]
I opened a terminal in /vlc and expanded the package with: tar -xvzf vlc-0.8.5-i686-3.gz
I opened a terminal in /vlc/install and did: cp doinst.sh ..
In the first terminal I did: chmod +x doinst.sh
then: ./doinst.sh
then ln -s /vlc/opt/vlc /opt/vlc -if you have no /opt directory, you will need to create one first.
(Now if I run ldd vlc all that it says I need is libvorbisenc.so.2)
We are making progress.
!!HOORAY!! - thanks to MU's thread on the SWEEP audio editor, I downloaded and installed this dotpup: http://dotpups.de/dotpups/Multimedia/li ... c.so.2.pup
VLC now works wonderfully - you can run it by clicking on /vlc/opt/vlc/bin/vlc
---
If you want a shortcut to VLC on your desktop, open /vlc/opt/vlc/bin and drag vlc onto the desktop. If you want to have an icon for it, they are in /vlc/opt/vlc/share/vlc - choose one an appropriate size.
---
BTW sorry I forgot to say before, but my main install is a full hard drive install of Puppy 1.09CE. I will test this in Chubby Puppy sometime (wish me luck).
---
I recommend moving the files in the vlc/opt/vlc/lib folder (the files, not the vlc folder that's in there) to /usr/lib, so that they are available to other programs, and you don't end up having two copies of half of them on your machine.
---
To make it so you can type vlc into a console to run it, put a link to /vlc/opt/vlc/bin/vlc in /usr/local/bin
To add VLC to the right click>open with menu, right click>open with>customise and put a link in the folder that opens
I'm starting with a clean install of Puppy 1.08 - I think they call it a frugal install - with image.gz, vmlinuz and usr_cram.fs on a windows disk. (-this works on at least Puppy 1.08, 1.09, 2, I think in any form of install)
I put the Slackware package mentioned above (http://www.videolan.org/vlc/download-slackware.html) in this folder: /vlc -you can put it anywhere, but will have to modify all the things you do after this to take this into account. [I think with a live CD or frugal install of Puppy 1.x this will disappear when you reboot, as various parts of the filesystem are read-only - you can change them when they are in RAM, but not keep the changes - a save place to put it is /root/vlc]
I opened a terminal in /vlc and expanded the package with: tar -xvzf vlc-0.8.5-i686-3.gz
I opened a terminal in /vlc/install and did: cp doinst.sh ..
In the first terminal I did: chmod +x doinst.sh
then: ./doinst.sh
then ln -s /vlc/opt/vlc /opt/vlc -if you have no /opt directory, you will need to create one first.
(Now if I run ldd vlc all that it says I need is libvorbisenc.so.2)
We are making progress.
!!HOORAY!! - thanks to MU's thread on the SWEEP audio editor, I downloaded and installed this dotpup: http://dotpups.de/dotpups/Multimedia/li ... c.so.2.pup
VLC now works wonderfully - you can run it by clicking on /vlc/opt/vlc/bin/vlc
---
If you want a shortcut to VLC on your desktop, open /vlc/opt/vlc/bin and drag vlc onto the desktop. If you want to have an icon for it, they are in /vlc/opt/vlc/share/vlc - choose one an appropriate size.
---
BTW sorry I forgot to say before, but my main install is a full hard drive install of Puppy 1.09CE. I will test this in Chubby Puppy sometime (wish me luck).
---
I recommend moving the files in the vlc/opt/vlc/lib folder (the files, not the vlc folder that's in there) to /usr/lib, so that they are available to other programs, and you don't end up having two copies of half of them on your machine.
---
To make it so you can type vlc into a console to run it, put a link to /vlc/opt/vlc/bin/vlc in /usr/local/bin
To add VLC to the right click>open with menu, right click>open with>customise and put a link in the folder that opens
Last edited by disciple on Wed 25 Oct 2006, 21:03, edited 5 times in total.