Recherche avancée

Médias (3)

Mot : - Tags -/plugin

Autres articles (1)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

Sur d’autres sites (1286)

  • XCode 5 is not linking Static Library to Cocoa Application

    4 septembre 2014, par aaronljx

    Basically I am building a Cocoa (OSX) application that uses some of the encoding/decoding libraries from ffmpeg (e.g. libavcodec.a, libavformat.a). For these libraries, I have explicitly configured it to be compiled as static library.. there were no dylibs created when I ran the make after configuring the package. Hence I am quite certain that these libraries would work as a static library.

    As usual I added these libraries to my xcode project via the Build Phases and Framework section. The .a files are there and when I build my project, there were no linking errors. Everything is fine and dandy until I run otool against the executable file of my application and realised that it needs the ffmpeg library dylibs to run. An attempt to run the application would fail since there is no dylib installed on my machine. If I run it on another machine that has ffmpeg installed (compiled with dynamic library) the application would work.

    Therefore, my question is, am I missing out on any of the configuration on the xcode part to instruct the linker to statically link those libraries that are used in my application ? (I remember when I develop C/C++ applications in Microsoft Visual Studio, all I need to do is to just add the static libraries (*.lib) files to my project’s linker settings and it will be automatically linked to my final assembly.)

    Thanks.

  • Revision 30966 : eviter le moche ’doctype_ecrire’ lors de l’upgrade

    17 août 2009, par fil@… — Log

    eviter le moche ’doctype_ecrire’ lors de l’upgrade

Navigation