Reinhard Tartler wrote:
> Ludovico Cavedon <email address hidden> writes:
>> Applications built against the stripped version should be able to run
>> against the unstripped version without recompilation (and in fact
>> qutecom/wengophone is able to); the application should just have fewer
>> or more codecs available (are there other differences btw?).
>
> check debian/strip.sh in the ffmpeg-debian package
Looks like there are no other differences
>> I want to be able to build the official package using the stripped-dev
>> libs and run it against the unstripped runtime.
>
> well, that's how all packages in debian and ubuntu are currently
> built. I fail to see the problem here?
That was in answer to bojo42, who was proposing unstripped-dev packages.
>> Yes I could work in a chroot, but sometimes it is annoying....
>
> I can only recommend building packages in clean chroots...
I agree, but sometimes for development and testing it is convenient to
work outside.
> The only valid use case for this request I could imagine would be if
> there was some packages that really requires the
> libavcodec-unstripped-52 installed and does not work with libavcodec52
> at all. I haven't seen such a package so far, though...
I am not referring to this case.
My use case is: qutecom/wengophone video support is disabled at runtime
if ffmpeg is stripped. Currently I am not able to compile and run it and
test the video, without keeping on switching between -dev packages and
unstripped packages,
Reinhard Tartler wrote:
> Ludovico Cavedon <email address hidden> writes:
>> Applications built against the stripped version should be able to run
>> against the unstripped version without recompilation (and in fact
>> qutecom/wengophone is able to); the application should just have fewer
>> or more codecs available (are there other differences btw?).
>
> check debian/strip.sh in the ffmpeg-debian package
Looks like there are no other differences
>> I want to be able to build the official package using the stripped-dev
>> libs and run it against the unstripped runtime.
>
> well, that's how all packages in debian and ubuntu are currently
> built. I fail to see the problem here?
That was in answer to bojo42, who was proposing unstripped-dev packages.
>> Yes I could work in a chroot, but sometimes it is annoying....
>
> I can only recommend building packages in clean chroots...
I agree, but sometimes for development and testing it is convenient to
work outside.
> The only valid use case for this request I could imagine would be if unstripped- 52 installed and does not work with libavcodec52
> there was some packages that really requires the
> libavcodec-
> at all. I haven't seen such a package so far, though...
I am not referring to this case.
My use case is: qutecom/wengophone video support is disabled at runtime
if ffmpeg is stripped. Currently I am not able to compile and run it and
test the video, without keeping on switching between -dev packages and
unstripped packages,