[MacPorts] #26528: avidemux 2.5.3 uses ffmpeg port headers instead of its own
MacPorts
noreply at macports.org
Sat Sep 18 16:01:17 PDT 2010
#26528: avidemux 2.5.3 uses ffmpeg port headers instead of its own
-------------------------------+--------------------------------------------
Reporter: ak.ml@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: | Port: avidemux
-------------------------------+--------------------------------------------
Changes (by raimue@…):
* cc: css@… (added)
* keywords: avidemux ffmpeg =>
Comment:
The problem is, cmake always has `-I/opt/local/include` hardcoded and adds
other paths specified with `include_directories(...)` at the end. Of
course, this ends up in the wrong order, with `-I/opt/local/include` at
the front while it should be the last.
I tried to fix this in r71635 by adding this flag to cmake, as
[http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:include_directories
described in their documentation]:
`-DCMAKE_INCLUDE_DIRECTORIES_BEFORE=ON`
For me on Snow Leopard 10.6.4 using cmake @2.8.2_2+gui. ffmpeg @0.6_2 was
active and installed at the same time, the build still was ''okay''. But
this could still mean it is picking up wrong headers :-)
And actually, you are right the order is still wrong even for me while
building plugins:
{{{
...
-I/opt/local/include
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_avidemux/work/avidemux_2.5.3/avidemux/ADM_libraries/ffmpeg
...
}}}
I am adding css@ as cmake maintainer to CC as he might have a hint where
to look at for this problem. I am clueless at the moment...
--
Ticket URL: <https://trac.macports.org/ticket/26528#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list