http://bugzilla.rpmfusion.org/show_bug.cgi?id=719
Lubos Stanek <lubek(a)users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lubek(a)users.sourceforge.net
--- Comment #1 from Lubos Stanek <lubek(a)users.sourceforge.net> 2009-07-15 15:29:56
---
(In reply to comment #0)
Backgound info: In avidemux 2.5, the main package now provides some
shared
libraries which the plugins link against at compile time. Because of this, the
main package must be compiled & installed first before compiling any plugins.
You can build and install the base avidemux locally and fire the plugins build
with appropriately populated build variables (AVIDEMUX_INSTALL_PREFIX,
AVIDEMUX_SOURCE_DIR, AVIDEMUX_CORECONFIG_DIR), all in one build sequence. It
works in mock as well.
If it is the only reason, I vote against packaging avidemux's own plugins in a
standalone package.
I would have no objections against a code developed outside of the avidemux
tree.
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.