Ignore:
Timestamp:
Jan 24, 2017, 12:24:46 PM (9 years ago)
Author:
Silvan Scherrer
Message:

SMPlayer: update vendor to 17.1.0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • smplayer/vendor/current/Install.txt

    r179 r186  
    1 This document explains how to compile and install smplayer.
     1This document explains how to compile and install SMPlayer.
    22
    3 Compiling smplayer should be easy. It only depends on Qt. Since version 0.6.4
    4 it can only be compiled with Qt 4.3 or greater.
     3Compiling SMPlayer should be easy. It only depends on Qt 4.
    54
    65
     
    2524
    2625
    27 2) How to make a rpm package (obsolete)
     262) How to make a rpm package
    2827----------------------------
    29 Run rpmbuild -tb smplayer-0.6.x.tar.bz2
    30 You'll find the rpm package under /usr/src/packages/RPMS/i586/
    31 
    32 Take a look at this document to know how to create a rpm from the SVN sources:
    33 http://smplayer.berlios.de/forums/viewtopic.php?id=188
     28Building a rpm package is not easy. Better get a binary package from
     29this repository:
     30https://software.opensuse.org/download.html?project=home%3Asmplayerdev&package=smplayer
    3431
    3532
    36 3) Generic compilation (obsolete)
     333) Generic compilation
    3734----------------------
    38 You need at least Qt 4.3 to compile smplayer. It won't work with an older
    39 version.
    40 
    41 Be sure you have installed the Qt 4 development package. Its name maybe
    42 qt4-devel, libqt4-dev or similar.
    43 
    44 Uncompress the source code, open a console and enter in the
    45 smplayer-0.6.x directory.
    46 
    47 Type "make".
    48 
    49 If everything is ok now you can install it with "make install".
    50 That will install smplayer in /usr/local.
    51 
    52 If "make" fails, it's probably because the Qt 3 qmake has been used instead of
    53 the Qt 4 one. It seems that some distros have renamed that tool to qmake-qt4.
    54 Others may have installed in another directory.
    55 Look at the contents of the qt4-devel package (or whatever its name is) and
    56 find out where it is.
    57 
    58 Now type something like this (just examples):
    59 make QMAKE=qmake-qt4
    60 or
    61 make QMAKE=/usr/share/qt4/bin/qmake
     35(obsolete)
    6236
    6337
     
    8256
    8357
    84 5) How to compile in Windows (obsolete)
     585) How to compile in Windows
    8559----------------------------
    86 First you need to download and install Qt (OpenSource edition) in your
    87 computer. You can get a package with installer from
    88 http://trolltech.com/developer/downloads/qt/windows
    89 
    90 During the installation it will ask you for a compiler. Simply let the
    91 Qt installer to download and install MinGW.
    92 
    93 Now we're ready to compile smplayer (or any other Qt application).
    94 Download the sources (either the *.tar.gz or from the svn) and
    95 uncompress them for example in C:\smplayer.
    96 
    97 The next step is to open the Qt console: select the option "Qt 4.3.x
    98 Command Prompt" that you'll find under the Qt menu.
    99 
    100 That'll open a DOS-like window. Type the following commands:
    101 
    102 cd c:\smplayer
    103 compile_windows.bat
    104 
    105 Compiling will start. That'll take a few minutes.
    106 
    107 After that you'll get the new compiled smplayer.exe under
    108 c:\smplayer\src\release subdirectory.
    109 
    110 You'll see that if you try to open it by double clicking on it, it won't
    111 work because it can find the Qt dlls. I assume you already have smplayer
    112 properly installed in some place, just copy the new smplayer.exe to that
    113 directory, replacing the old one. Now it will work
    114 
    115 You may also need to copy the updated translation files (*.qm) from the
    116 translations subdirectory.
    117 
    118 Note: please see this document to know how to compile with Qxt support:
    119 http://smplayer.berlios.de/forums/viewtopic.php?pid=1737#p1737
     60(obsolete)
Note: See TracChangeset for help on using the changeset viewer.