After compile finished without error, used only the default qt interface, cli from the build directory.Ģ) viceo displays fine in default gui, used several different *.avi files.ģ) enabling fullscreen (button or doubleclick on vout), a second window appears, measured 800圆24 pixels, no borders, no titlebar, playing video. On 26 March 2009, 01:29 by what is exactly your issue? 15.ĭid the whole process over again today: clean jaunty-a6 install, then ran your command set.
#X11 video output xcb download skin
Have also an "arch-install" running "git" which plays nicely in default but won't take skins.RATS! You can prolly guess am doing this for skin development, and having a working vlc-1.0 version would be sweet, as skins work well in "9.8a", and a leg up for the near future would require "1.0x". Some other issues noted but insignificant at this point.
Fullscreen displays an seperate "X11" (I think) window only, from the default/skins interface, never goes fullscreen, and "zoom" feature appears faulty. Never compiled vlc for 'nix before and had many failed compiles in "xp", way back when, so figured doing it on 'nix would be a bad joke, but.as "make" took 14 minutes (no errors, pre-make took at least twice that), so, your method cranked and the finished product accepted skins.YEOW!!!ĭiscovered that the default qt4 and skin interface won't display fullscreen, tho initial embedded displays work fine in both. Just discovered this page yesterday, ran the above instructions on a fresh "jaunty-alpha6 install, and to my surprise all went very well. On 16 March 2009, 00:24 by done as you wished. Sure if this is necessary, but well, just in case. Installing, I removed any other VLC version from the system. PS: Oh, one thing I forgot to mention : before Hope that helps anyone who doesn't like having to keep a ~400MB directory in his $HOME just to be able to run the latest version of VLC. I assume that only one of the two additional options might be necessary, but as building takes too damn long, I'm not gonna test that now. This has to be put there manually, if desired. VLC installation will not put a VLC entry to the Gnome application menu. There's still one feature missing, though: When run from the build directory before installing, it always took some seconds for VLC to start up, at least on my machine. Anyway, I didn't do too extensive testing so far.Īlso, VLC now starts much faster, almost instantly. VLC seems to run fine now and also appears to find everything it needs to run and work, as opposed to installing it without those extra options, where normally VLC wouldn't even start right afterwards. vlc from the build directory, and actually, the bloated 400MB git-directory can be removed. configure -disable-nls -enable-qt4 -prefix=/opt/vlc -exec-prefix=/usrĪfterwards 'sudo make install' should finish fine and VLC will be startable from any directory by just typing 'vlc' into the terminal. I compiled VLC-git with the following additional configure options (add the two additional options to the second-to-last command from the HowTo above):
#X11 video output xcb download install
You don't need to install VLC for it to work. Make install does a lot of stuff but doesn't install the new version. My current (8.10 Ubuntu) vlc version stays at 0.94 while in the build/bin dir the new 1.00 vls exists. How should i get 0.9.8a version of vlc from git repository? 9. Is there an equivalent "make install" for this. But if you want latest FFmpeg and latest x264, follow the old posts. On 10 March 2009, 08:56 by thanks, we all know you are kind of right, but this was more to be funny than to be accurate good catch, this howto is way more simple than the usual one (with x264) but is enough for most people. If make build is successfull, then execute:Īfter that, if cd build is successfull, execute:Īnd so on. The & actualy separate commands, and are interpreted as "if" statements. I think he was refering to all the commands. Otherwise, it wouldn't install, at least it didn't for me. Sudo apt-get build-dep vlc & apt-get install libtool build-essential automake1.10 git-core The first command seems to need another sudo for the second part of the command, like this: Thank you very much for this HowTo! It was very helpful.
I haven't done the x264 bit yet - am I going to miss much? Where should the x264 repo end up? as a separate dir or in the same folder as vlc? X264 question: the prev build instructions on your blog Particularly the use of the build dir? But no matter I finally seem to have recovered (after deleting everything thinking I had screwed the git repo - twice). I got a question though What is the use of bootstrap ? 2.īootstrap is necessary to create the configure.
0 kommentar(er)
