#368 closed defect (invalid)
change README: you need to configure --with-win32libdir
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Component: | DOCS |
| Version: | 1.0pre7 | Severity: | normal |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Reproduced by developer: | no | Analyzed by developer: | no |
Description
from your all-codecs-package-README:
Put the files contained in this archive in a directory where MPlayer will find
them. The default directory is /usr/local/lib/codecs/ ($prefix/lib/codecs/) if
you are compiling from source, but you can change that value by passing the
'--with-codecsdir' option to './configure'.
not true. I did compile mplayer with ./configure, then put the codecs
to /usr/local/lib/codecs. No effect. Then, I recompiled with explicitely giving
the standard location:
./configure --with-win32libdir=/usr/local/lib/codecs
and it worked. Although there should be no difference. Please change the
README.
Attachments (1)
Change History (7)
comment:1 by , 19 years ago
comment:3 by , 19 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The README explains it correctly, the order of things is important.
comment:4 by , 19 years ago
This change makes the formulation correct. Please remember, the expression
"codecs" sounds like they will be dynamically linked. Thanks.
comment:5 by , 19 years ago
They are not dynamically linked (if they were, they definitly would have to be
available before compiling), they are mmaped.
But MPlayer configure uses the existence of the /usr/local/lib/codecs directory
to decide whether to compile in the interface code for them or not.
So just creating the directory or using the --with-win32libdir option would work
too.
comment:6 by , 19 years ago
--with-win32libdir is not enough, you would need --with-codecsdir in any case...
Because you have to install the codecs before doing ./configure!
If the readme doesn't explain this it should probably be changed.