[vlc-devel] iOS Build patch
remi at remlab.net
Mon Jul 16 09:08:10 CEST 2012
Le samedi 14 juillet 2012 15:46:36 Rafaël Carré, vous avez écrit :
> I don't say they should be mandatory, but after all why not ?
That does not mean anything really. Without parameters, configure has to
assume the default native toolchain, default import and installation paths,
default compilation parameters, default features, etc are in use. Thus,
practically any VLC build requires custom parameters, even when building
natively, and that's hardly avoidable.
However, if some parameters (typically compiler/toolchain related) is required
for the entire system (e.g. OS distro) or the whole binary VLC package (e.g.
including contrib), then it clearly does not belong in configure. It belongs
in the packaging system that sits on top of it and runs it.
Clearly the MacOS port is abusing the configure script in that respect. And
that causes a lot of avoidable code churn.
Conversely, if some parameter applies only to a one module, or any subset of
the VLC source tree, then it should be set in the Makefiles, as far as
possible. In many such cases but not always, some detection code in configure
is unavoidable (for instance calling pkg-config).
More information about the vlc-devel