From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Multimedia Libs
Date: Thu, 02 Apr 2020 19:07:04 +0200 [thread overview]
Message-ID: <af7a1c67-d5e7-cac8-3e2f-6f4f0ddbc063@ipfire.org> (raw)
In-Reply-To: <ac3f57d0-b44e-52ff-7de8-4a6a7ecf3700@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2948 bytes --]
Hi,
On 25.03.2020 21:55, Matthias Fischer wrote:
> Hi,
>
> On 27.02.2020 12:27, Michael Tremer wrote:
>>
>> [...could you look for some multimedia libs...?]>
>
> Ok. I'm nice. I did. ;-)
>
>> ...
[cut: Lots of updates, lots of links]
I got them building without errors - based on current 'next' (2f8a33e).
All of them and some more.
Overview:
***SNIP***
root(a)Devel: /home/matz/ipfire-2.x # git status
On branch multimedia_libs
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
deleted: config/netpbm/Makefile.config
modified: config/netpbm/config.mk
modified: config/rootfiles/common/cmake
modified: config/rootfiles/common/libjpeg
modified: config/rootfiles/common/libpng
modified: config/rootfiles/packages/faad2
modified: config/rootfiles/packages/ffmpeg
modified: config/rootfiles/packages/lame
modified: config/rootfiles/packages/libogg
modified: config/rootfiles/packages/libshout
modified: config/rootfiles/packages/libtiff
modified: config/rootfiles/packages/libvorbis
modified: config/rootfiles/packages/motion
modified: config/rootfiles/packages/netpbm
modified: config/rootfiles/packages/opus
modified: config/rootfiles/packages/sox
modified: config/rootfiles/packages/taglib
modified: config/rootfiles/packages/xvid
modified: lfs/cmake
modified: lfs/faad2
modified: lfs/ffmpeg
modified: lfs/lame
modified: lfs/libjpeg
modified: lfs/libmpeg2
modified: lfs/libogg
modified: lfs/libpng
modified: lfs/libshout
modified: lfs/libtiff
modified: lfs/libvorbis
modified: lfs/motion
modified: lfs/netpbm
modified: lfs/opus
modified: lfs/sox
modified: lfs/taglib
modified: lfs/xvid
modified: make.sh
Untracked files:
(use "git add <file>..." to include in what will be committed)
config/rootfiles/packages/libmicrohttpd
lfs/libmicrohttpd
***SNAP***
I'd like to push this branch as a whole so "someone" can take a look.
My problem:
Its a bit difficult to push them as individual patches, because there
are a lot of dependencies between the single "modules". And right now,
I'm not in the state to figure out which works with which, who I can and
cannot upload as a patch collection. And I can't test any of these here.
Thats my biggest problem. Building is OK - but will they work as intended?
So I'd like to push them all at once so "someone" can take a look and
test (- perhaps). Some lfs-options and some rootfiles might need
"finetuning" and I'm not really able to decide what to keep and what not.
Opinions?
Best,
Matthias
next prev parent reply other threads:[~2020-04-02 17:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5C7D0AAC-730A-40BA-B398-8AED49A4867D@ipfire.org>
2020-03-25 20:55 ` Matthias Fischer
2020-03-25 21:11 ` Stephan Mending
2020-03-26 7:24 ` Matthias Fischer
2020-03-26 9:10 ` Michael Tremer
2020-03-26 9:30 ` Matthias Fischer
2020-03-28 4:54 ` Matthias Fischer
2020-03-28 7:41 ` Michael Tremer
2020-03-26 9:47 ` Stephan Mending
2020-03-30 5:08 ` Matthias Fischer
2020-03-30 5:17 ` Matthias Fischer
2020-03-30 9:10 ` Matthias Fischer
2020-03-30 9:31 ` Michael Tremer
2020-04-02 17:07 ` Matthias Fischer [this message]
2020-04-03 10:22 ` Michael Tremer
2020-05-23 10:08 ` Matthias Fischer
2020-05-25 9:29 ` Michael Tremer
2020-05-25 11:05 ` Matthias Fischer
2020-05-26 10:15 ` Michael Tremer
2020-05-26 17:13 ` Matthias Fischer
2020-05-28 11:54 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af7a1c67-d5e7-cac8-3e2f-6f4f0ddbc063@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox