[mythtv-users] compiling trunk on f20/qt4

[John Pilkington]

On 11/09/14 11:00, Jean-Yves Avenard wrote:
> On 10 September 2014 05:52, brad dreisbach <bradd at ameri.ca> wrote:
>
>> i saw some chatter about the ffmpeg resync breaking the qt5 build,
>> but nothing about the qt4 build. is --enable-pthreads no longer
>> a recommended config option(i notice its not even listed in configure's
>> --help output)?
>
> it never has been.
>
> configure detects what's there, and what should be used. Passing some
> flags override the auto-detection that would otherwise have failed and
> be normally disabled.
>
> The only configure options that make sense is enabling features that
> are disabled by default (and marked as such):
> - mp3 encoder
> - h264 encoder
> - aac encoder
> - divx encoder
> - vpx encoder
> - SDL (compiles ffplay)
>
> Optional:
> - prefix
> - compile-type
> - qmake version (useful when you have both qt5 and qt4 installed)
>
> that's it.
>
> e.g, if you want it all:
> ./configure --prefix=/usr/local/mythtv-trunk --compile-type=debug
> --qmake=qmake-qt4 --disable-mythlogserver --enable-libx264
> --enable-libmp3lame --enable-libfaac --enable-libxvid --enable-libvpx
> --enable-sdl --enable-nonfree
>
> Anything else is useless.

I just added a reference to JYA's comment here to another thread on the 
dev list about building rpms, but I suspect another comment _is_ 
appropriate.  configure will only detect the capabilities of the 
processor if it's running on the target machine.  Otherwise, as in the 
case when a specfile is used to build packages for a repo, assumptions 
will have to be made.  mock may manage this.  Perhaps one size doesn't 
always fit?