Enabled outdevs:
oss
License: nonfree and unredistributable
Creating config.mak and config.h...
config.h is unchanged
libavutil/avconfig.h is unchanged
./config.sh: line 8: --disable-ffmpeg：找不到命令
wangrl@wangrl-desktop:~/android_develop/ffmpeg/lib/jni/ffmpeg6$ ./config.sh
Unknown C compiler /home/wangrl/android_develop/ndk/android-ndk-r8/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-gcc
/home/wangrl/android_develop/ndk/android-ndk-r8/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-gcc is unable to create an executable file.
C compiler test failed.
If you think configure made a mistake, make sure you are using the latest
version from SVN. If the latest version fails, report the problem to the
ffmpeg-user@mplayerhq.hu mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "config.err" produced by configure as this will help
solving the problem.
透过 mac os x 中的“服务”选单，您在执行某个应用程序时，也可以使用另一个应用程序的功能。snow leopard 中的服务更加简便实用。它只显示和当前使用程序或浏览内容相关的服务项目，而不是所有服务项目。只要按鼠标右键或按住 control 并按下触控板按钮即可使用服务功能。您可以自行设定选单，让它只显示您想要的服务选项，或使用 automator 建立您自己的服务。以下就教您如何灵活运用automator来製作方便好用的』服务』选单。此篇示范的为重新命名大量的图片文件名称。
步骤如下：
1. 从应用程序资料夹底下将automator打开。
2. 打开之后，选择『服务』选项。
3. 将「服务接受所选的」选单指定为「影像文件」，并将「在任何应用程序」选择为「finder」
4.从左侧边的程序库类型栏位选择「文件和文件夹」选项，右侧边动作选择「重新命名finder项目」。
5.将此动作拉到左侧边，此时会出现一个对话框，选择「不要加入」，「加入」的意思是将所要更改的文件复制一份到别的位置。
6.更改名称的方式有很多，选项如下图所示，可以选择一种您比较喜欢的方式当作日后的预设值。这边示范的为「使连续」
7. 最后就是将您设定好的服务储存，并且命名好一个方便好用的名称。就可以先关闭automator了。
8. 那么您会在哪边使用这项新增好的「服务」呢？如下图所示，会有三个地方让您选择。1. 分别是屏幕上方finder选单底下的「服务」、2. finder视窗的动作按钮以及 3.针对要修改的文件的右键选单都会出现您刚才新增的「服务」功能。
9.当您日后针对要修改的文件按下设定好的「服务」功能后，会跳出设定好的服务对话框来供您修改。
您看！是不是很简单？瞬间就帮您把大量的图片文件改好序列的文件名称了！
这边我只是做个简单的示范而已，automator的服务应用还有很多，例如：旋转影像文件、更改文件类型或者是缩放影像…等等，这些过去要自己一个一个慢慢来修改的枯燥乏味动作，都可以利用「automator」搭配「服务」在瞬间就完成！
转载自：http://www.macx.cn/thread-1176966-1-1.html
Android NDK, Revision 8 (May 2012)
This release of the NDK includes support for MIPS ABI and a few additional fixes.
New features:- Added support for the MIPS ABI, which allows you to generate machine code that runs on compatible MIPS-based Android devices. Major features for MIPS include MIPS-specific toolchains, system headers, libraries and debugging support. For more details regarding MIPS support, see docs/CPU-MIPS.html in the NDK package.
By default, code is generated for ARM-based devices. You can add mips to your APP_ABI definition in your Application.mk file to build for MIPS platforms. For example, the following line instructs ndk-build to build your code for three distinct ABIs:
APP_ABI := armeabi armeabi-v7a mips
Unless you rely on architecture-specific assembly sources, such as ARM assembly code, you should not need to touch your Android.mk files to build MIPS machine code.
- You can build a standalone MIPS toolchain using the --arch=mips option when calling make-standalone-toolchain.sh. See docs/STANDALONE-TOOLCHAIN.html for more details.
Note: To ensure that your applications are available to users only if their devices are capable of running them, Google Play filters applications based on the instruction set information included in your application — no action is needed on your part to enable the filtering. Additionally, the Android system itself also checks your application at install time and allows the installation to continue only if the application provides a library that is compiled for the device's CPU architecture.
Important bug fixes:- Fixed a typo in GAbi++ implementation where the result of dynamic_cast<D>(b) of base class object b to derived class D is incorrectly adjusted in the opposite direction from the base class. (Issue 28721)
- Fixed an issue in which make-standalone-toolchain.sh fails to copy libsupc++.*.
- Fixed ndk-build.cmd to ensure that ndk-build.cmd works correctly even if the user has redefined the SHELL environment variable, which may be changed when installing a variety of development tools in Windows environments
APP_ABI := armeabi armeabi-v7a mips
APP_ABI := armeabi armeabi-v7a mips x86