Hi Jan, I posted this before but it seems the message was too large for this list.
Here is the original post: I'm not sure how helpful this will be for you since I'm using android's proprietary build system called ndk-build. It handles most of the cpu and machine stuff internally. Plus, I didn't use the configure script. I modified the config.h manually - which I'm sure is not the right way to go. Again, not sure it will help you. It is a bit of a mess. If you can build using configure your life will probably be easier. I'll send the config.h in email. On Thu, Dec 23, 2010 at 9:35 AM, Jan Pěkník <[email protected]> wrote: > Dne 23.12.2010 0:17, Eli Konky napsal(a): > > On Wed, Dec 22, 2010 at 9:18 PM, Benjamin Larsson<[email protected]> >> wrote: >> >> On 12/22/2010 07:53 PM, Jan Pěkník wrote: >>> >>>> Hello, >>>> I need to implement 3GP encoding on embedded ARM based system (with >>>> proprietary OS), after >>>> some research I've decided to try it with ffmpeg. The task is only to >>>> create >>>> .3gp or .mp4 file from input of series of images (raw pixel data) and >>>> audio track (raw 22050hz data also), >>>> no decoding, playback, or any other functionality is needed. Performance >>>> is not an issue, as encoding >>>> will not be performed realtime. The problem is, I probably cannot afford >>>> to build whole ffmpeg and link it, >>>> as there would be too much overhead ( I can probably afford 1MB library >>>> added, but not much more). >>>> Could please someone give me any hints what would be the best approach? >>>> >>>> best regards, >>>> jpeknik >>>> >>> Look what configure has to offer with regard to what features you need >>> to be included in the libs. >>> >>> MvH >>> Benjamin Larsson >>> _______________________________________________ >>> libav-user mailing list >>> [email protected] >>> https://lists.mplayerhq.hu/mailman/listinfo/libav-user >>> >>> FYI, For an android project I'm doing I managed to compile ffmpeg for >> arm >> (neon) with approx what you need and got to 2,558,524. >> It includes avutil, avcodec and avformat. >> It excludes swscale, which you might need - but it is rather lite. >> >> As mentioned above there are corresponding "configure" flags to enable >> disable them but I also carefully removed c files from the make file to >> shorten the build process. I'm not sure if it reduced the size of the >> binary >> though. >> >> > Could you please send configure flags you've used? It would be very > helpful, I'm a bit lost especially on target cpu and whether > to specify --host an use cross compiling, as I'm planning to compile it > with WinARM cross compiler > thath should automatically produce arm libs/binaries. My target is arm9 > CPUs and better. > > thanks > Jan > > _______________________________________________ > libav-user mailing list > [email protected] > https://lists.mplayerhq.hu/mailman/listinfo/libav-user > _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
