WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: get_mplayer.tcz  (Read 395 times)

Offline nitram

  • Hero Member
  • *****
  • Posts: 1052
get_mplayer.tcz
« on: December 18, 2016, 11:48:18 AM »
New  get_mplayer.tcz  extension for TC7 x86.

As MPlayer ./configure uses hardware autodetect, compile natively on target system for best performance.

Run 'get_mplayer.sh' to wget and compile MPlayer with FFmpeg to create an mplayer_custom.tcz extension. Automatically takes care of all default helper and dependency extensions.

User able to customize build and add additional ./configure options, prompted to manually add these extra helpers and dependencies prior to running ./configure. Makes compiling mplayer very simple with best performance for the system. Good experience for users unfamiliar with the ./configure, make, make install process.

CLI, OSD and gmplayer (graphic) MPlayer compile options, see info file for more details.

Screens:
Code: [Select]
get_mplayer (v201612)
 
* Downloads MPlayer (movie player) source (MPlayer-1.3.0.tar.xz with FFmpeg).
* Compiles source to create mplayer_custom.tcz, dep and md5sum files.
* As MPlayer uses hardware autodetect, best to compile on target system.
* Includes libXv support for good performance on most systems.
* Choose from CLI mplayer, OSD mplayer or gmplayer options.
* Prompted for additional configure options before compile.
* Prompted to add mplayer_custom.tcz to onboot.lst or OnDemand.
* Prompted to create config and copy example config files.
* Prompted to install default skin if compiling gmplayer.
* Default build options compile and run well in TC7.
* User must ensure:
  - Working network connection.
  - Adequate RAM (uses /tmp/), possibly swap.
  - Adequate drivespace (compiletc, dev and dep files).
* Build time 2.25 hrs on single core 800MHz, 512MB RAM.
* Re-run script as needed, such as failed custom configuration.
* Press Ctrl-C at any time to break out of script.
 
Press Enter to wget, md5sum check and extract MPlayer source:

Code: [Select]
* Run /tmp/MPlayer-1.3.0/./configure --help in other terminal for more options.
* Enabling more means more functionality with extra bloat and dependencies.
* Enable/disable options as desired to mix and match desired mplayer.
 
Choose one of the primary build options below, this will load the required
development packages and modify the resulting dependency file.
 
1. CLI mplayer only:
     ./configure
2. CLI mplayer with OSD (on screen display):
     ./configure --enable-menu --enable-freetype
3. Graphic mplayer (gmplayer using GTK2, default skin option):
     ./configure --enable-gui
4. Graphic mplayer with OSD (full meal deal):
     ./configure --enable-menu --enable-freetype --enable-gui
 
Enter package 1, 2, 3 or 4: 4

Append any space separated configure options or just Enter to continue.
If not needed, --disable-mencoder cuts the final TCZ size in half:
./configure --enable-menu --enable-freetype --enable-gui --disable-mencoder

In Apps or another terminal load additional *-dev extensions required for any
optional ./configure options manually entered above. When done press Enter
to load the following compile helper extensions: compiletc squashfs-tools
alsa-dev yasm libXext-dev xorg-proto libXv-dev freetype-dev gtk2-dev

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2341
Re: get_mplayer.tcz
« Reply #1 on: January 01, 2017, 12:47:59 AM »
Interesting, thanks nitram.

seems like there are many configure options which will take some figuring out


Offline nitram

  • Hero Member
  • *****
  • Posts: 1052
Re: get_mplayer.tcz
« Reply #2 on: January 06, 2017, 03:09:09 PM »
Hope you got a successful build coreplayer2.

Recommend a vanilla compile first (eg. CLI, CLI with OSD, GMPlayer) without extra config options. As MPlayer auto-detects most everything and the script was primarily set up for users running Xorg and Alsa (most common setup), recommend a relatively lean boot containing the following before running the script:
Xorg*
xf86-video-*
alsa-modules-*
alsa
alsa-config

Ensure Pulse or OSS is not intentionally or dependency loaded for first compile test. The script should take care of the rest. After an initial success, attempt custom configuration compile as desired. Most test builds also custom added  --disable-mencoder  . On test hardware all 4 vanilla options compiled successfully, only tested on one system thus far, hopefully works for others.