[MPlayer-dev-eng] Having MPlayer and Mencoder in a single binary.
Bryan Wilkerson
bryanwilkerson at yahoo.com
Wed Jul 6 19:44:27 CEST 2005
If the goal of having a single binary is to eliminate
the code duplication problem between mplayer.c and
mencoder.c, I think the better solution would be to
push the duplicated code into shared library that both
mplayer.c and mencoder.c would call into.
With this approach, mplayer.c and mencoder.c become
specific to the tasks of dealing with user arguments
and UI and make calls into the library. You would
also still have two separate exes and not have to add
another layer of multiplexing in the argument parser.
-bryan
--- Danny <guru at digitalfantasy.it> wrote:
>
> ...
>
> >>An option is an ugly hack and
> >>not at all user-friendly. Alternatively you can
> make a wrapper that
> >>invokes mplayer.exe with argv[0]=="mencoder"
> >>
> >>
> >
> >That sounds like a good idea.. Does that work in
> windows?..
> >
> >
> >
>
> From a first test (on windows 98), it doesn't
> work.
>
> The best solution is, in my opinion, to use an
> option and make a
> wrapper that add that option to the invocation of
> mplayer.
>
> The user sees a little mencoder.exe that work.
>
> Daniele Forghieri
>
> _______________________________________________
> MPlayer-dev-eng mailing list
> MPlayer-dev-eng at mplayerhq.hu
> http://mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
>
More information about the MPlayer-dev-eng
mailing list