Most usage of OpenCV is fairly simple (like face recognision or image loading)
so we don't have to force users to compile CUDA-enabled OpenCV for those.
openblas is used since it's propagated from OpenCV and ATLAS compiled without
architecture-specific optimizations is generally slower than OpenBLAS as I
heard.
The version of VTE that uses GTK2 is not maintained, so using lxterminal
with GTK2 means dealing with a lot of bugs that have already been fixed
in newer VTE versions. I actually meant to set up lxterminal to use GTK3
in the first place, but didn't realize that wasn't the default until
now.
This drastically reduces the complexity of the `avidemux` derivation
and adds QT5 support (see #33248).
Rather than invoking `cmake` over preconfigured hooks, it's much easier
to use the `bootStrap.bash` script provided by the developers to do the
installation tasks. Furthermore this script makes it way easier to
configure which parts of `avidemux` should be used (e.g. CLI-only) or
without the plugins.
In order to create a CLI-only instance you can simply override the
derivation:
```
avidemux.override {
withQT = false;
}
```
It's possible to set the default executable as well (`avidemux` creates
a `avidemux_qt5` and `avidemux_cli` executable by default):
```
avidemux.override {
default = "cli"; # default is `qt5`
}
```
The GTK support has been dropped entirely since it was originally broken
in our system and can't be built ATM. Other distros such as ArchLinux
don't support GTK anymore (see https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/avidemux#n64)
The icu4c cross-build process requires access to a full buildRoot of a
native build, so we add a variant of the build that just does the
buildPhase and copies the buildRoot to $out for access by the cross
compile.
