Android Studio compiled run fresco Sample. Android Cache New Realm. (a problem occurred start process ' command ' ndk-build ')

Wandering around today, ran into an "Android application development difficulties", as an Android program ape, instinctively point in, want to see what the difficulties they do not know (portentous. Wall).

Plug-in, H5 container optimization, network, picture caching. Feel all right. Until you see "fresco out, do you think the picture cache is over?" ”

Fresco what is the Divine!!

Inquiry degree Niang know, 2015.3.27 before the day has been released (degree Niang results earliest is 3.27). By viewing GitHub:

Version 0.1.0

Tyronen released this + days ago Commits to master since this release

Initial release.

The original was released 16 days ago. Deeply worshipped.

Sample Run ~ can't wait to show it.

By looking at the introduction, fresco put the picture into a special memory area, progressive display, GIF support, image pipeline and so on, completely solve the puzzle of optimization for many years.

The specific logic and usage of fresco, to be further studied, will be analyzed and then written out. First record the mood and the process of the first compilation run.

1. Download

Download is simple, github download zip, unzip, OK. Https://github.com/facebook/fresco

2. Import

Source code is Android Studio project. Fortunately, the early turn to as, but also the use of Eclipse students seize the ~

Open As,import, select the root directory to extract fresco, next ..... Smooth OK.

3. View

The structure is really good. It's an organizational structure, and it's estimated to be kneeling for three days and three nights.

4. Operation

Can't wait.

5. Error

Sure enough, compile error. A problem occurred start process ' command ' ndk-build '

6. Solve

Home machine, has not been equipped with the NDK environment, feel normal. With the .... Ok

Run, still wrong. Error display when compiling imagepipeline, ' command ' ndk-build ' cannot find

Tangled for a long time, look for environment variables and try different configuration methods. cannot be resolved. External causes are excluded, only the error location can be found.

In Module:imagepipeline Build.gradle, the location of the call Ndk-build is as follows:

An estimate is an issue with the Getndkbuildfullpath () return value (the big God code cannot be faulted.) Can only be an environmental problem),

Attempt to change to an absolute path. CommandLine '/users/user1/ndk/ndk-build '

Run, OK.

Looks very high-end appearance.

Although it is not clear the specific logic, but still very excited. The bottleneck of optimization finally has the breakthrough hope!

It will be resumed another other.

Android Studio compiled run fresco Sample. Android Cache New Realm. (a problem occurred start process ' command ' ndk-build ')