Sur d’autres sites (4783)

• so Confused, why my build of libffmpeg.so > 17M ?

  24 février 2012, par ghost

  I did build ffmpeg for Android in winxp and scientific linux , ffmpeg is in dolphin player — an open source video player (http://code.google.com/p/dolphin-player/), and i just build the ffmpeg, its seems like the same as in rockplayer 1.7.0, they all use build_andriod.sh below， it worked in both winxp and linux,
  and all successfully got bin/ffmpeg (less than 5MB), but libffmpeg.so ( > 17MB)， when put libffmpeg.so in dolphin-player libs , player can't work, the size 17MB is too large, the original libffmpeg.so in olphin-player libs is less than 5MB, please give some advice.

  #!/bin/bash
  
  
  
  ######################################################
  
  # FFmpeg builds script for Android+ARM platform
  
  #
  
  # This script is released under term of 
  
  #   CDDL (http://www.opensource.org/licenses/cddl1) 
  
  # Wrote by pinxue (~@gmail.com) from RockPlayer.com
  
  #                                   2010-8 ~ 2011-4
  
  ######################################################
  
  
  
  ######################################################
  
  # Usage:
  
  #   put this script in top of FFmpeg source tree
  
  #   ./build_android
  
  #
  
  # It generates binary for following architectures:
  
  #     ARMv6 
  
  #     ARMv6+VFP 
  
  #     ARMv7+VFM-ïd16 (Tegra2) 
  
  #     ARMv7+Neon (Cortex-A8)
  
  #
  
  # Customizing:
  
  # 1. Feel free to change ./configure parameters for more features
  
  # 2. To adapt other ARM variants
  
  #       set $CPU and $OPTIMIZE_CFLAGS 
  
  #       call build_one
  
  ######################################################
  
  
  
  export TMPDIR=D:/tmp/android
  
  export NDK=D:/android-ndk-r4
  
  
  
  #PLATFORM=$NDK/build/platforms/android-8/arch-arm/
  
  PLATFORM=$NDK/build/platforms/android-8/arch-arm
  
  #PREBUILT=$NDK/build/prebuilt/darwin-x86/arm-eabi-4.4.0
  
  PREBUILT=$NDK/build/prebuilt/windows/arm-eabi-4.4.0
  
  
  
  function build_one
  
  {
  
  
  
  # -fasm : required. Android header file uses asm keyword instead of __asm__ , but most of c dialect (like ansi,c99,gnu99) implies -fno-asm.
  
  #   ~/android/android-ndk-r4/build/platforms/android-5/arch-arm//usr/include/asm/byteorder.h: In function '___arch__swab32':
  
  #   ~/android/android-ndk-r4/build/platforms/android-5/arch-arm//usr/include/asm/byteorder.h:25: error: expected ')' before ':' token
  
  
  
  # -fno-short-enums : optimized.  Else FFmpeg obj will generate a huge number of warning for variable-size enums, 
  
  #   though we may suppress them by --no-enum-size-warning, it would be better to avoid it.
  
  #   .../ld: warning: cmdutils.o uses variable-size enums yet the output is to use 32-bit enums; use of enum values across objects may fail
  
  
  
  # --extra-libs="-lgcc" : required. Else cannot solve some runtime function symbols
  
  #   ... undefined reference to `__aeabi_f2uiz'
  
  
  
  # --enable-protocols : required. Without this option, the file open always fails mysteriously.
  
  #   FFmpeg's av_open_input_file will invoke file format probing functions, but because most of useful demuxers has flag of zero 
  
  #   which cause them are ignored during file format probling and fall to url stream parsing,
  
  #   if protocols are disabled, the file:// url cannot be opened as well.
  
  
  
  # $PREBUILT/bin/arm-eabi-ar d libavcodec/libavcodec.a inverse.o : required.
  
  #   FFmpeg includes two copies of inverse.c both in libavutil and libavcodec for performance consideration (not sure the benifit yet)
  
  #   Without this step, final ld of generating libffmpeg.so will fail silently, if invoke ld through gcc, gcc will collect more reasonable error message.
  
  
  
  # -llog: debug only, FFmpeg itself doesn't require it at all.
  
  #   With this option, we may simply includes "utils/Log.h" and use LOGx() to observe FFmpeg's behavior
  
  #   PS, it seems the toolchain implies -DNDEBUG somewhere, it would be safer to use following syntax
  
  #    #ifdef NDEBUG
  
  #        #undef NDEBUG
  
  #        #define HAVE_NDEBUG
  
  #    #endif
  
  #    #include "utils/Log.h"
  
  #    #ifdef HAVE_NDEBUG
  
  #        #define NDEBUG
  
  #        #undef HAVE_NDEBUG
  
  #    #endif
  
  
  
  # --whole-archive : required. Else ld generate a small .so file (about 15k)
  
  
  
  # --no-stdlib : required. Android doesn't use standard c runtime but invited its own wheal (bionic libc) because of license consideration.
  
  
  
  # space before \ of configure lines: required for some options. Else next line will be merged into previous lines's content and cause problem.
  
  #   Especially the --extra-cflags, the next line will pass to gcc in this case and configure will say gcc cannot create executable.
  
  
  
  # many options mentioned by articles over internet are implied by -O2 or -O3 already, need not repeat at all.
  
  
  
  # two or three common optimization cflags are omitted because not sure about the trade off yet. invoke NDK build system with V=1 to find them.
  
  
  
  # -Wl,-T,$PREBUILT/arm-eabi/lib/ldscripts/armelf.x mentioned by almost every articles over internet, but it is not required to specify at all.
  
  
  
  # -Dipv6mr_interface=ipv6mr_ifindex : required. Android inet header doesn't use ipv6mr_interface which is required by rfc, seems it generate this user space header file directly from kernel header file, but Linux kernel has decided to keep its own name for ever and ask user space header to use rfc name.
  
  
  
  # HAVE_SYS_UIO_H : required. Else:
  
  # In file included from ~/android/android-ndk-r4/build/platforms/android-5/arch-arm//usr/include/linux/socket.h:29,
  
  #                 from ~/android/android-ndk-r4/build/platforms/android-5/arch-arm//usr/include/sys/socket.h:33,
  
  #                 from libavformat/network.h:35,
  
  #                 from libavformat/utils.c:46:
  
  #~/android/android-ndk-r4/build/platforms/android-5/arch-arm//usr/include/linux/uio.h:19: error: redefinition of 'struct iovec'
  
  #
  
  
  
  # --disable-doc : required because of strange bug of toolchain.
  
  #
  
  
  
  #
  
  #--extra-ldflags=-Wl,-T,$PREBUILT/arm-eabi/lib/ldscripts/armelf.x -Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib $PREBUILT/lib/gcc/arm-eabi/4.4.0/crtbegin.o $PREBUILT/lib/gcc/arm-eabi/4.4.0/crtend.o -lc -lm -ldl"
  
  #
  
  
  
  ./configure --target-os=linux \
  
      --prefix=$PREFIX \
  
      --enable-cross-compile \
  
      --extra-libs="-lgcc" \
  
      --arch=arm \
  
      --cc=$PREBUILT/bin/arm-eabi-gcc \
  
      --cross-prefix=$PREBUILT/bin/arm-eabi- \
  
      --nm=$PREBUILT/bin/arm-eabi-nm \
  
      --sysroot=$PLATFORM \
  
     --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums  -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
      --disable-shared \
  
      --enable-static \
  
      --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -nostdlib -lc -lm -ldl -llog" \
  
      --enable-parsers \
  
      --disable-encoders  \
  
      --enable-decoders \
  
      --disable-muxers \
  
      --enable-demuxers \
  
      --enable-swscale  \
  
      --disable-ffplay \
  
      --disable-ffprobe \
  
      --disable-ffserver \
  
      --enable-network \
  
      --enable-indevs \
  
      --disable-bsfs \
  
      --disable-filters \
  
      --enable-protocols  \
  
      --enable-asm \
  
      --disable-doc \
  
      $ADDITIONAL_CONFIGURE_FLAG
  
  
  
  ##make clean
  
  make  -j4 install
  
  
  
  
  
  $PREBUILT/bin/arm-eabi-ar d libavcodec/libavcodec.a inverse.o
  
  
  
  $PREBUILT/bin/arm-eabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a  -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-eabi/4.4.0/libgcc.a
  
  
  
  }
  
  
  
  
  
  #arm v6
  
  CPU=armv6
  
  OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  PREFIX=./android/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7vfpv3
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  PREFIX=./android/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7vfp
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU "
  
  PREFIX=./android/$CPU-vfp
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7n
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=neon -marm -march=$CPU -mtune=cortex-a8"
  
  PREFIX=./android/$CPU-neon 
  
  ADDITIONAL_CONFIGURE_FLAG=--enable-neon
  
  build_one
  
  
  
  #arm v6+vfp
  
  CPU=armv6
  
  OPTIMIZE_CFLAGS="-DCMP_HAVE_VFP -mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU"
  
  PREFIX=./android/${CPU}_vfp 
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one

• Implemented improvements and fixes suggested by Claudio Rumolo :

  28 février 2012, par Sebastian Tschan

  m server/php/upload.class.php Implemented improvements and fixes suggested by Claudio Rumolo : * If scaling factor is >= 1, don’t do any image processing. * Add JPEG/PNG quality parameter option. * Recalculate the file size if the original file has been replaced by a scaled (...)

• Nexus One

  19 mars 2010, par Mans — Uncategorized

  I have had a Nexus One for about a week (thanks Google), and naturally I have an opinion or two about it.
  

  Hardware

  With the front side dominated by a touch-screen and a lone, round button, the Nexus One appearance is similar to that of most contemporary smartphones. The reverse sports a 5 megapixel camera with LED flash, a Google logo, and a smaller HTC logo. Power button, volume control, and headphone and micro-USB sockets are found along the edges. It is with appreciation I note the lack of a front-facing camera ; the silly idea of video calls is finally put to rest.

  Powering up the phone (I’m beginning to question the applicability of that word), I am immediately enamoured with the display. At 800×480 pixels, the AMOLED display is crystal-clear and easily viewable even in bright light. In a darker environment, the display automatically dims. The display does have one quirk in that the subpixel pattern doesn’t actually have a full RGB triplet for each pixel. The close-up photo below shows the pattern seen when displaying a solid white colour.

  

  The result of this is that fine vertical lines, particularly red or blue ones, look a bit jagged. Most of the time this is not much of a problem, and I find it an acceptable compromise for the higher effective resolution it provides.

  Basic interaction

  The Android system is by now familiar, and the Nexus offers no surprises in basic usage. All the usual applications come pre-installed : browser, email, calendar, contacts, maps, and even voice calls. Many of the applications integrate with a Google account, which is nice. Calendar entries, map placemarks, etc. are automatically shared between desktop and mobile. Gone is the need for the bug-ridden custom synchronisation software with which mobile phones of the past were plagued.

  Launching applications is mostly speedy, and recently used apps are kept loaded as long as memory needs allow. Although this garbage-collection-style of application management, where you are never quite sure whether an app is still running, takes a few moments of acclimatisation, it works reasonably well in day to day use. Most of the applications are well-behaved and save their data before terminating.

  Email

  Two email applications are included out of the box : one generic and one Gmail-only. As I do not use Gmail, I cannot comment on this application. The generic email client supports IMAP, but is rather limited in functionality. Fortunately, a much-enhanced version, K-9, is available for download. The main feature I find lacking here is threaded message view.

  The features, or lack thereof, in the email applications is not, however, of huge importance, as composing email, or any longer piece of text, is something one rather avoids on a system like this. The on-screen keyboard, while falling among the better of its kind, is still slow to use. Lack of tactile feedback means accidentally tapping the wrong key is easily done, and entering numbers or punctuation is an outright chore.

  Browser

  Whatever the Nexus lacks in email abilities, it makes up for with the browser. Surfing the web on a phone has never been this pleasant. Page rendering is quick, and zooming is fast and simple. Even pages not designed for mobile viewing are easy to read with smart reformatting almost entirely eliminating the sideways scrolling which hampered many a mobile browser of old.

  Calls and messaging

  Being a phone, the Nexus One is obviously able to make and receive calls, and it does so with ease. Entering a number or locating a stored contact are both straight-forward operations. During a call, audio is clear and of adequate loudness, although I have yet to use the phone in really noisy surroundings.

  The other traditional task of a mobile phone, messaging, is also well-supported. There isn’t really much to say about this.

  Multimedia

  Having a bit of an interest in most things multimedia, I obviously tested the capabilities of the Nexus by throwing some assorted samples at it, revealing ample space for improvement. With video limited to H.264 and MPEG4, and the only supported audio codecs being AAC, MP3, Vorbis, and AMR, there are many files which will not play.

  To make matters worse, only selected combinations of audio and video will play together. Several video files I tested played without sound, yet when presented with the very same audio data alone, it was correctly decoded. As for container formats, it appears restricted to MP4/MOV, and Ogg (for Vorbis). AVI files are recognised as media files, but I was unable to find an AVI file which would play.

  With a device clearly capable of so much more, the poor multimedia support is nothing short of embarrassing.

  The Market

  Much of the hype surrounding Android revolves around the Market, Google’s virtual marketplace for app authors to sell or give away their creations. The thousands of available applications are broadly categorised, and a search function is available.

  The categorised lists are divided into free and paid sections, while search results, disappointingly, are not. To aid the decision, ratings and comments are displayed alongside the summary and screenshots of each application. Overall, the process of finding and installing an application is mostly painless. While it could certainly be improved, it could also have been much worse.

  The applications themselves are, as hinted above, beyond numerous. Sadly, quality does not quite match up to quantity. The vast majority of the apps are pointless, though occasionally mildly amusing, gimmicks of no practical value. The really good ones, and they do exist, are very hard to find unless one knows precisely what to look for.

  Battery

  Packing great performance into a pocket-size device comes with a price in battery life. The battery in the Nexus lasts considerably shorter time than that in my older, less feature-packed Nokia phone. To some extent this is probably a result of me actually using it a lot more, yet the end result is the same : more frequent recharging. I should probably get used to the idea of recharging the phone every other night.

  Verdict

  The Nexus One is a capable hardware platform running an OS with plenty of potential. The applications are still somewhat lacking (or very hard to find), although the basic features work reasonably well. Hopefully future Android updates will see more and better core applications integrated, and I imagine that over time, I will find third-party apps to solve my problems in a way I like. I am not putting this phone on the shelf just yet.