Recherche avancée

Médias (0)

Mot : - Tags -/protocoles

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (67)

  • 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 (...)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

Sur d’autres sites (8850)

  • libx264.so.146 not found while compiling C++ code or x264 itself

    27 février 2017, par Laurent Loots

    I just upgraded my system from Ubuntu 15.10 to Ubuntu 16.04 LTS. Now, for some reason my C++ project won’t compile anymore. CLion keeps saying it’s missing ’libx264.so.146 as you can see in the compile log :

    /home/lorre851/CLion/bin/cmake/bin/cmake --build /home/lorre851/.CLion12/system/cmake/generated/ce7171e4/ce7171e4/Release --target main -- -j 8
    [ 20%] Linking CXX executable build/main
    /usr/bin/ld: warning: libx264.so.146, needed by /usr/local/lib/libavcodec.so.57, not found (try using -rpath or -rpath-link)
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_open_146'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_close'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_bit_depth'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_headers'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_encode'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_reconfig'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_param_parse'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_param_apply_profile'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_param_apply_fastfirstpass'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_levels'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_picture_init'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_param_default'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_param_default_preset'
    /usr/local/lib/libavcodec.so.57: undefined reference to `x264_encoder_delayed_frames'
    collect2: error: ld returned 1 exit status
    CMakeFiles/main.dir/build.make:172: recipe for target 'build/main' failed
    make[3]: *** [build/main] Error 1
    CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/main.dir/all' failed
    make[2]: *** [CMakeFiles/main.dir/all] Error 2
    CMakeFiles/Makefile2:79: recipe for target 'CMakeFiles/main.dir/rule' failed
    make[1]: *** [CMakeFiles/main.dir/rule] Error 2
    Makefile:118: recipe for target 'main' failed
    make: *** [main] Error 2

    Most people seem to give ’reinstalling x264’ as a solution. However, reinstalling x264 with the following commands leads to the same error while compiling x264 itself.

    git clone git://git.videolan.org/x264
    cd x264
    ./configure --enable-static
    make

    /usr/bin/ld: warning: libx264.so.146, needed by /usr/local/lib/libavcodec.so, not found (try using -rpath or -rpath-link)
    /usr/local/lib/libavcodec.so: undefined reference to `x264_encoder_open_146'
    collect2: error: ld returned 1 exit status
    Makefile:202: recipe for target 'x264' failed
    make: *** [x264] Error 1

    Does anyone have an idea how I could get around this ?

  • How to compile FFmpeg with bash on Windows 10 ?

    10 août 2017, par user2980183

    In the Creators Update (1703), the Windows 10 bash linux (WSL) can run native windows tools. So, under Windows 10, you can now compile FFmpeg with Visual Studio and the required linux utilities, natively, without having to install MinGW or other interop crap software.

    Here is how I tried to compile FFmpeg (using MSVC 2017 toolchain) :

    • I started the bash shell from "Developer Command Prompt for VS 2017" to set PATH variable to find the MSVC compiler/linker.

    • I installed the "make" tool with the following command : "sudo apt-get install make".

    • To call Windows program from the bash shell, I have to type the command with its .exe extension. So, I must adapt the "configure" and "compat/windows/makedef" files to add ".exe" at the end of "cl", "link" (no confusion possible with the /usr/bin/link), "dumpbin" and "lib" executables :

    configure

    cl_major_ver=$(cl 2>&1 | sed -n 's/.*Version \([[:digit:]]\{1,\}\)\..*/\1/p')
       if [ -z "$cl_major_ver" ] || [ $cl_major_ver -ge 18 ]; then
           cc_default="cl.exe"
       else
           cc_default="c99wrap cl"
       fi
       ld_default="link.exe"
       nm_default="dumpbin.exe -symbols"
       ar_default="lib.exe"

    compat/windows/makedef

    lib.exe -out:${libname} $@ >/dev/null

    arch=$(dumpbin.exe -headers ${libname} |
      tr '\t' ' ' |
      grep '^ \+.\+machine \+(.\+)' |
      head -1 |
      sed -e 's/^ \{1,\}.\{1,\} \{1,\}machine \{1,\}(\(...\)).*/\1/')

    dump=$(dumpbin.exe -linkermember:1 ${libname})

    I hope the FFmpeg build tool chain will be adapted in the future to support natively compiling on bash on Windows...

    • If you want to set an absolute path for YASM in the "configure", you have to use the following pattern /mnt/[letter_partition]/path/yasm.exe.

    ./configure --toolchain=msvc --yasmexe='/mnt/e/Home/Important/Development/Toolkit/Tools/yasm-1.3.0-win32.exe' [all other settings you need]

    • The make command should generate the lib as expected.

    • I tried to type make install but I get the following error :
      No rule to make the target "libavutil\x86\x86util.asm", needed for "libavutil/x86/cpuid.o".

    I don’t know what is wrong...

    As you can see, building FFmpeg on bash under Windows is not very developer friendly yet. Compiling FFmpeg in Windows should be as easy as Linux. Do you know if there is an easier way to proceed ? Do you know if this compilation scenario will be officially supported in next versions of FFmpeg (I don’t find any roadmap) ?

    Thanks.

  • FFMPEG library Integration unsuccess

    1er septembre 2017, par Alok Kumar Verma

    I’m stuck with the integration of the FFMPEG file. I’m using Android Studio 2.3.3

    I’ve followed this link and hence got to know how to do this but all I’m getting is a failure.

    Links

    1. How to integrate the FFMPEG in your android
    2. Integrating android FFMPEG

    Now I"ve my ndk installed in this path : /Users/alok/Library/Android/sdk/ndk-bundle

    And I’ve downloaded the newest version of the FFMPEG i.e., 3.3.3 unzipped it in the sources folder of ndk-bundle

    Now I’ve followed this and implemented everything as said.

    • Editing the Configure File using TEXTVIEW in my mac
    • Creating a file name build_android.sh and copy pasting the given code. However I’ve changed the NDK path in my case in the code the code is here

      NDK=/Users/alok/Library/Android/sdk/ndk-bundle
      SYSROOT=$NDK/platforms/android-23/arch-arm/
      TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64
    • Now opening the folder through terminal and then typing this command sudo chmod +x build_android.sh followed by this sudo ./build_android.sh

    The result is : No android name folder created inside under the folder FFMPEG 3.3.3 in this root i.e., /ndk-bundle/sources/ffmpeg 3.3.3/

    and the terminal shows this output :

    ./configure: line 3341: syntax error near unexpected token `2'

    ./configure: line 3341:

    DEPCMD='$(DEP$(1)) $(DEP$(1)FLAGS) $($(1)DEP_FLAGS) $< 2>/dev/null | sed -e "/^\#.*/d" -e "s,^[[:space:]]*$(@F),$(@D)/$(@F)," > $(@:.o=.d)''
    Makefile:2: config.mak: No such file or directory
    Makefile:67: /common.mak: No such file or directory
    Makefile:114: /libavutil/Makefile: No such file or directory
    Makefile:114: /library.mak: No such file or directory
    Makefile:116: /doc/Makefile: No such file or directory
    Makefile:206: /tests/Makefile: No such file or directory
    make: *** No rule to make target /tests/Makefile'. Stop.

    Hence I’m not been able to move next due to this which creating a JNI folder and stuff. I’m a beginner with FFMPEG and want to integrate it.

    NOTE : I’ve already used this library in my gradle

    compile ‘com.writingminds:FFmpegAndroid:0.3.2’

    For easy approach and things are working fine too but due to the older version I’m getting wrong outputs, so need to update it and there is one way and this is the way to do it.