Recherche avancée

Sur d’autres sites (6570)

• Command build failed ndk

  1er janvier 2021, par ALI RAZA

  I want to integrate ffmpeg lib in my android app . So i am using ndk ,but i am stuck on this issue,I dont know why the error is appearing ,Thanks in advance ;

  


  It is the gradle code that i am using in my app and also the ffmpeg-android-maker path is provided

  


  plugins {
id 'com.android.application'


  


  


  android 
compileSdkVersion 30
buildToolsVersion "30.0.3"

  


  defaultConfig {
    applicationId "com.reactive.myapplication"
    minSdkVersion 16
    targetSdkVersion 30
    versionCode 1
    versionName "1.0"

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    externalNativeBuild {
        cmake {
            cppFlags ""
        }
    }
}
flavorDimensions "market"
productFlavors {
    google {
        dimension "market"
        ndk {
            // Since the App Bundle is used, there is no problem in packaging all these ABIs
            abiFilters 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a'
        }
    }
    amazon {
        dimension "market"
        applicationIdSuffix ".amzn"
        ndk {
            // Amazon Appstore doesn't support multiple APKs for non-Amazon devices.
            // There is no point in x86 support here, as the majority of devices with the
            // Amazon Appstore are ARM-based. And it seems to be a common practice for other
            // apps in this market.
            abiFilters 'armeabi-v7a'
        }
    }
    huawei {
        dimension "market"
        applicationIdSuffix ".huawei"
        ndk {
            // Huawei App Gallery supports App Bundle format
            abiFilters 'x86', 'x86_64', 'armeabi-v7a', 'arm64-v8a'
        }
    }
}
sourceSets {
    main {
        // let gradle pack the shared library into the apk
        jniLibs.srcDirs = ['../ffmpeg-android-maker/output/lib']
    }
}

bundle {
    language {
        enableSplit = true
    }
    density {
        enableSplit = true
    }
    abi {
        enableSplit = true
    }
}

buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}
externalNativeBuild {
    cmake {
        path "src/main/cpp/CMakeLists.txt"
        version "3.10.2"
    }
}
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8

    targetCompatibility JavaVersion.VERSION_1_8
}


  


  


  dependencies

  


  implementation 'androidx.appcompat:appcompat:1.1.0'
implementation 'com.google.android.material:material:1.1.0'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.+'
androidTestImplementation 'androidx.test.ext:junit:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'


  


  


  And It is cmake ,


  


  And this is error i am facing :
Build command failed.
Error while executing process /home/ali/Android/Sdk/cmake/3.10.2.4988404/bin/ninja with arguments -C /home/ali/AndroidStudioProjects/FfmpegApp/app/.cxx/cmake/amazonDebug/armeabi-v7a native-lib
ninja : Entering directory `/home/ali/AndroidStudioProjects/FfmpegApp/app/.cxx/cmake/amazonDebug/armeabi-v7a'

  


  ninja : error : '/home/ali/AndroidStudioProjects/FfmpegApp/app/src/main/ffmpeg-android-maker/output/lib/armeabi-v7a/libavutil.so', needed by '/home/ali/AndroidStudioProjects/FfmpegApp/app/build/intermediates/cmake/amazonDebug/obj/armeabi-v7a/libnative-lib.so', missing and no known rule to make it

  


• Recapping WebM’s First Week

  25 mai 2010, par noreply@blogger.com (John Luther) — webm, vp8, vorbis

  The WebM project launched last Wednesday with broad industry backing (watch video of the announcement). The list of supporters keeps growing with new additions such as the popular VLC media player, Miro Video Converter, HeyWatch cloud encoding platform, and videantis programmable processor platform. We’re also happy to see that future versions of IE will support playback of VP8 when the user has installed the codec.

  Our announcement sparked discussions in the community around the design and quality of our developer release. We’ve done extensive testing of VP8 and know that the codec can match or exceed the quality of other leading codecs. Starting this week, the engineers behind WebM will post frequently to this blog with details on how to make optimal use of its VP8 video codec and Vorbis audio codec. We are confident that the open development model will bring additional improvements that will further optimize WebM. In fact, the power of open development is already visible, with developers submitting patches and the folks at Flumotion enabling live streaming support in their product just three days after the project was launched.

  Keep an eye on this blog for regular updates on the adoption and development of WebM. To participate in the conversation or to ask questions of the WebM team, please join our discussion group.

  John Luther
  Product Manager, Google

  

• Recapping WebM’s First Week

  25 mai 2010, par noreply@blogger.com (John Luther) — webm, vp8, vorbis

  The WebM project launched last Wednesday with broad industry backing (watch video of the announcement). The list of supporters keeps growing with new additions such as the popular VLC media player, Miro Video Converter, HeyWatch cloud encoding platform, and videantis programmable processor platform. We’re also happy to see that future versions of IE will support playback of VP8 when the user has installed the codec.

  Our announcement sparked discussions in the community around the design and quality of our developer release. We’ve done extensive testing of VP8 and know that the codec can match or exceed the quality of other leading codecs. Starting this week, the engineers behind WebM will post frequently to this blog with details on how to make optimal use of its VP8 video codec and Vorbis audio codec. We are confident that the open development model will bring additional improvements that will further optimize WebM. In fact, the power of open development is already visible, with developers submitting patches and the folks at Flumotion enabling live streaming support in their product just three days after the project was launched.

  Keep an eye on this blog for regular updates on the adoption and development of WebM. To participate in the conversation or to ask questions of the WebM team, please join our discussion group.

  John Luther
  Product Manager, Google