Recherche avancée

Médias (0)

Mot : - Tags -/presse-papier

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

Autres articles (66)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (13756)

  • ffmpeg configure always returns "not found" when using sysroot and cross-prefix options - how to use them correctly ?

    5 août 2014, par user2212461

    I try to build ffmpeg with a cross-compiler. When setting the configure flags I am getting the following errors :

    WARNING: Compiler does not indicate floating-point ABI, guessing soft.
    build_it.sh: 29: build_it.sh: --sysroot=/home/android/android-ndk-r9/platforms/
       android-9/arch-arm/: not found
    build_it.sh: 32: build_it.sh.sh: --cross-prefix=/home/android/android-ndk-r9/
       toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-and
       roideabi-: not found

    The error message "not found" sounds like the paths dont exist but they are all correct and existing. How can I resolve this error ?

    build_it.sh :

    NDK=/home/android/android-ndk-r9
    SYSROOT=$NDK/platforms/android-9/arch-arm/
    TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86
    CPU=arm
    PREFIX=test
    ADDI_CFLAGS="-marm"
    platform="android-9"

    ./configure \
       --disable-asm \
       --enable-shared \
       --target-os=linux \
       --arch=arm \
       --enable-cross-compile \
       --disable-static \
       --sysroot=$SYSROOT \
       --extra-cflags="-Os -fpic $ADDI_CFLAGS" \
       --extra-ldflags="$ADDI_LDFLAGS"
       --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
       --prefix=$PREFIX \

    ##configure fails here
    ...
  • Use Google Analytics and risk fines, after CJEU ruling on Privacy Shield

    27 août 2020, par Joselyn Khor — Privacy

    EU websites using Google Analytics and Facebook are being targeted by European privacy group noyb after the invalidation of the Privacy Shield. They filed a complaint against 101 websites for continuing to send data to the US. 

    “A quick analysis of the HTML source code of major EU webpages shows that many companies still use Google Analytics or Facebook Connect one month after a major judgment by the Court of Justice of the European Union (CJEU) - despite both companies clearly falling under US surveillance laws, such as FISA 702. Neither Facebook nor Google seem to have a legal basis for the data transfers.”

    noyb website
    CJEU invalidates the Google Privacy Shield

    The Privacy Shield previously allowed for EU data to be transferred to the US. However, this was invalidated by the Court of Justice of the European Union (CJEU) on July 16, 2020. The CJEU deemed it illegal for any websites to transfer the personal data of European citizens to the US. 

    They also made it clear in a press release that “data subjects can claim compensation for inadmissible data exports (marginal no. 143 of the judgment). This should in particular include non-material damage (“compensation for pain and suffering”) and must be of a deterrent amount under European law.” Which puts extra financial pressure on websites to take the new ruling seriously.

    Immediate action is required after Google Privacy Shield invalidation

    The Berlin Commissioner for Data Protection and Freedom of Information therefore calls on all those responsible under its supervision to observe the decision of the ECJ [CJEU]. Those responsible who transfer personal data to the USA - especially when using cloud services - are now required to immediately switch to service providers in the European Union or in a country with an adequate level of data protection.

    The Berlin Commissioner for Data Protection and Freedom of Information

    As the ruling is effective immediately, there’s a pressing need for websites using Google Analytics to act, or face getting fined.

    What does this mean for you ?

    If you’re using Google Analytics the safest bet is to stop using it immediately

    "Neither Google Analytics nor Facebook Connect are necessary for the operation of these websites and could therefore have been replaced or at least deactivated in the meantime."

    Max Schrems, Honorary Chairman of noyb 

    If you still need to use it, then you’ll need to inform your visitors via a clear consent screen. This banner needs to make clear their personal data will be sent to the US, and to educate them about any potential risk related to this. They will then need to explicitly agree to this. 

    Another downside of cookie consent screens is that you may also suffer a damaging loss of visitors. After implementing cookie consent best practices, the UK’s data regulator the Information Commissioner’s Office (ICO) found a 90% drop in traffic, “implying a ninety percent drop in opt-in rates.”

    With an acceptance rate for such consent screens being lower than 10% your analytics becomes guesswork rather than science. 

    Looking for a privacy-respecting alternative to Google Analytics ?

    Privacy compliant Matomo Analytics is one of the best Google Analytics alternatives availalble. 

    With Matomo you’re able to continue using analytics without facing the wrath of both the GDPR and the CJEU. Matomo On-Premise lets you choose where your data is stored, so you can ensure no data is processed in the US. 

    Matomo is privacy-friendly and can be tweaked to comply with all privacy laws. Including the GDPR, HIPAA, CCPA and PECR. The benefits of this include : not needing to use tracking or cookie consent screens (like with GA) ; and avoiding fines because no personal data is collected. You also get 100% accurate data and the ability to protect your user’s privacy.

    Matomo is the privacy-respecting Google Analytics alternative

    Is your EU business at risk of being fined for using Google Analytics ?

  • how to call a c function in the C++ function with the same name ?

    25 juillet 2013, par wolfz

    how to call a c function in the C++ function with the same name ?
    calling 'extern "c"' to use c header and ": :"operation to use the c function,
    but the link error occur.

    my code :

    extern "C" {
    #include <libavcodec></libavcodec>avcodec.h>
    }
    ...
    class DllAvCodec
    {
     public:
     ...
     virtual void av_free_packet(AVPacket *pkt) { ::av_free_packet(pkt); }
     ...
    }

    the error :

    D:/player/jni/lib/DllAvCodec.h:143: error: undefined reference to &#39;av_free_packet(AVPacket*)&#39;

    why the code "::av_free_packet(pkt)" invoke undefined ?

    my Android.mk is :

    LOCAL_PATH := $(call my-dir)
    DEFINES += \
              -DTARGET_POSIX \
              -DTARGET_LINUX \
              -D_LINUX \
              -DTARGET_ANDROID \
              -D__STDC_CONSTANT_MACROS

    ######################################
    #build ffmpeg prebuilt lib
    ######################################
    include $(CLEAR_VARS)  
    LOCAL_MODULE := libavcodec
    LOCAL_SRC_FILES := lib/lib/libavcodec.a
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libavfilter  
    LOCAL_SRC_FILES := lib/lib/libavfilter.a
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libavformat  
    LOCAL_SRC_FILES := lib/lib/libavformat.a  
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libavutil  
    LOCAL_SRC_FILES := lib/lib/libavutil.a  
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libpostproc  
    LOCAL_SRC_FILES := lib/lib/libpostproc.a  
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libswresample  
    LOCAL_SRC_FILES := lib/lib/libswresample.a  
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)

    include $(CLEAR_VARS)  
    LOCAL_MODULE := libswscale  
    LOCAL_SRC_FILES := lib/lib/libswscale.a
    LOCAL_EXPORT_C_INCLUDES +=$(LOCAL_PATH)/lib/include
    include $(PREBUILT_STATIC_LIBRARY)


    ######################################
    #build lib
    ######################################
    include $(CLEAR_VARS)
    LOCAL_MODULE:= player
    base := $(LOCAL_PATH)

    LOCAL_SRC_FILES += ......

    LOCAL_CPPFLAGS += -Wall -fexceptions $(DEFINES)  
    LOCAL_LDLIBS += -llog -lz
    LOCAL_LDFLAGS += -L../jni/lib/lib  -lavcodec -lavformat  -lavutil -lavfilter -lpostproc  -lswscale -lswresample

    LOCAL_STATIC_LIBRARIES := libavcodec \
                             libavformat \
                             libavutil \
                             libavfilter \
                             libpostproc \
                             libswscale \
                             libswresample

    include $(BUILD_SHARED_LIBRARY)