Recherche avancée

Médias (91)

Autres articles (69)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11647)

  • Android-NDK building using the Bambuser source

    13 juillet 2015, par Kenny910

    I am trying to use the FFmpeg source provided by the Bambuser.

    However, I am fail to build the files

    I get the following error :

    arm-linux-androideabi-gcc is unable to create an executable file.
    C compiler test failed.

    I have already set the NDK path to /home/android-ndk but still get this error

    And I am using Android-NDK-r5b

    can anyone help ? THX

    Here is my build.sh

    #!/bin/bash

    if [ "$NDK" = "" ]; then
       echo NDK variable not set, assuming ${HOME}/android-ndk
       export NDK=${HOME}/android-ndk
    fi

    SYSROOT=$NDK/platforms/android-3/arch-arm
    # Expand the prebuilt/* path into the correct one
    TOOLCHAIN=`echo $NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows`
    export PATH=$TOOLCHAIN/bin:$PATH

    rm -rf build/ffmpeg
    mkdir -p build/ffmpeg
    cd ffmpeg

    # Don't build any neon version for now
    for version in armv5te armv7a; do

       DEST=../build/ffmpeg
       FLAGS="--target-os=linux --cross-prefix=arm-linux-androideabi- --arch=arm"
       FLAGS="$FLAGS --sysroot=$SYSROOT"
       FLAGS="$FLAGS --soname-prefix=/data/data/com.streaming.realive/lib/"
       FLAGS="$FLAGS --enable-shared --disable-symver"
       FLAGS="$FLAGS --enable-small --optimization-flags=-O2"
       FLAGS="$FLAGS --enable-encoder=mpeg4 --enable-decoder=mpeg4"
       FLAGS="$FLAGS --enable-encoder=mpeg2video --enable-encoder=nellymoser"
       FLAGS="$FLAGS --enable-protocol=rtp --enable-protocol=rtmp"
       FLAGS="$FLAGS --enable-protocol=http --enable-protocol=tcp --enable-protocol=udp"
       FLAGS="$FLAGS --enable-protocol=file"

       case "$version" in
           neon)
               EXTRA_CFLAGS="-march=armv7-a -mfloat-abi=softfp -mfpu=neon"
               EXTRA_LDFLAGS="-Wl,--fix-cortex-a8"
               # Runtime choosing neon vs non-neon requires
               # renamed files
               ABI="armeabi-v7a"
               ;;
           armv7a)
               EXTRA_CFLAGS="-march=armv7-a -mfloat-abi=softfp"
               EXTRA_LDFLAGS=""
               ABI="armeabi-v7a"
               ;;
           *)
               EXTRA_CFLAGS=""
               EXTRA_LDFLAGS=""
               ABI="armeabi"
               ;;
       esac
       DEST="$DEST/$ABI"
       FLAGS="$FLAGS --prefix=$DEST"

       mkdir -p $DEST
       echo $FLAGS --extra-cflags="$EXTRA_CFLAGS" --extra-ldflags="$EXTRA_LDFLAGS" > $DEST/info.txt
       ./configure $FLAGS --extra-cflags="$EXTRA_CFLAGS" --extra-ldflags="$EXTRA_LDFLAGS" | tee $DEST/configuration.txt
       [ $PIPESTATUS == 0 ] || exit 1
       make clean
       make -j4 || exit 1
       make install || exit 1

    done
  • App Store Submission Fails Due to Unsupported Architectures and Invalid Segment Alignment [closed]

    2 juin, par Ahsanur Rahman

    I’m using ffmpegkit in my iOS app, but when I submit the app to the App Store, I get these errors :

    


    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/ffmpegkit.framework contains unsupported architectures '[x86_64]'. (ID : 3e35bca7-7b8f-4c2b-bfb2-a27c8ad70c45)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libavcodec.framework contains unsupported architectures '[x86_64]'. (ID : fd864260-dae3-4816-bdf3-ca7389374242)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libavdevice.framework contains unsupported architectures '[x86_64]'. (ID : fd743847-5d46-4679-8193-51db9445fde1)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libavfilter.framework contains unsupported architectures '[x86_64]'. (ID : 54492aff-601e-471a-aef7-25f0549a6364)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libavformat.framework contains unsupported architectures '[x86_64]'. (ID : 37bcd80d-7b17-4f95-a20f-577dbb29fc36)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libavutil.framework contains unsupported architectures '[x86_64]'. (ID : ead0bd08-84e6-475e-9ce3-9e1c012bafa5)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libswresample.framework contains unsupported architectures '[x86_64]'. (ID : fe647420-760c-4404-a039-30c102d7d313)

    


    Validation failed
    
Unsupported Architectures. The executable for MyApp.app/Frameworks/libswscale.framework contains unsupported architectures '[x86_64]'. (ID : 7c8946d8-d75f-455c-b6fd-1bd555abb99f)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/ffmpegkit.framework/ffmpegkit' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 8603e3f0-0235-4f3c-a87f-c263945a11d9)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libavcodec.framework/libavcodec' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : f10b4561-0a9c-4aa6-969a-9d3a892be9ec)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libavdevice.framework/libavdevice' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 2e6d495a-9131-43da-b6a8-8c23b8d10415)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libavfilter.framework/libavfilter' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 40016424-045d-470f-b40a-fba391de2c98)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libavformat.framework/libavformat' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : f8cc4367-25bb-4932-bd03-af6729fe7587)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libavutil.framework/libavutil' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 495572f9-2dcb-472b-97ea-d16ba6e239a9)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libswresample.framework/libswresample' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 5722d5f0-0f81-422f-8389-e744c73cfd67)

    


    Validation failed
    
Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libswscale.framework/libswscale' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (ID : 1e4bf706-5e56-423d-b600-a8298eff698f)

    


    Validation failed
    
The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's linker. (ID : 8695bbb6-991f-46cd-9b70-bd86dcef4212)

    


    


    I add the below code in a runscript :

    


    APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"

find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
do
FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)"

EXTRACT_ARCHS=$(lipo -info "$FRAMEWORK_EXECUTABLE_PATH" | rev | cut -d ':' -f1 | rev)
ARCHS_TO_REMOVE=""

for ARCH in $EXTRACT_ARCHS; do
    if [ "$ARCH" != "arm64" ]; then
        ARCHS_TO_REMOVE="$ARCHS_TO_REMOVE -remove $ARCH"
    fi
done

if [ ! -z "$ARCHS_TO_REMOVE" ]; then
    lipo $ARCHS_TO_REMOVE "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH" || exit 1
fi
done


    


    I have already tried some suggestion from online but nothing worked.

    


  • FFMPEG error showing while complile for android

    15 mars 2020, par Vijay

    I am trying to add ffmpeg into my android project. I am using ubuntu 14.04 OS.

    I am following this link. Link

    But I am getting error while executing this line.

    $ANDROID_NDK/build/tools/make-standalone-toolchain.sh --toolchain=x86-4.8 --arch=x86 --system=linux-x86_64 --platform=android-14 --install-dir=/tmp/vplayer

    I am getting this following error.

    HOST_OS=linux
    HOST_EXE=
    HOST_ARCH=x86_64
    HOST_TAG=linux-x86_64
    HOST_NUM_CPUS=1
    BUILD_NUM_CPUS=2
    ERROR: Unknown option '--system'. See --help for usage.

    Please help me how to solve this issue and add ffmpeg into my project.