Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (100)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (8563)

  • GDPR Compliance and Personal Data : The Ultimate Guide

    22 septembre 2023, par Erin — GDPR

    According to the International Data Corporation (IDC), the world generated 109 zettabytes of data in 2022 alone, and that number is on track to nearly triple to 291 zettabytes in 2027. For scale, that’s one trillion gigs or one followed by 21 zeros in bytes.

    A major portion of that data is generated online, and the conditions for securing that digital data can have major real-world consequences. For example, online identifiers that fall into the wrong hands can be used nefariously for cybercrime, identity theft or unwanted targeting. Users also want control over how their actions are tracked online and transparency into how their information is used.

    Therefore, regional and international regulations are necessary to set the terms for respecting users’ privacy and control over personal information. Perhaps the most widely known of these laws is the European Union’s General Data Protection Regulation (GDPR).

    What is personal data under GDPR ?

    Under the General Data Protection Regulation (GDPR), “personal data” refers to information linked to an identifiable natural person. An “identifiable natural person” is someone directly or indirectly recognisable via individually specific descriptors such as physical, genetic, economic, cultural, employment and social details.

    It’s important to note that under GDPR, the definition of personal data is very broad, and it encompasses both information that is commonly considered personal (e.g., names and addresses) and more technical or specialised data (e.g., IP addresses or device IDs) that can be used to identify individuals indirectly.

    Organisations that handle personal data must adhere to strict rules and principles regarding the processing and protection of this data to ensure individuals’ privacy rights are respected and upheld.

    Personal data can include, but is not limited to, the following :

    1. Basic Identity Information : This includes a person’s name, government-issued ID number, social address, phone number, email address or other similar identifiers.
    2. Biographical Information : Details such as date of birth, place of birth, nationality and gender.
    3. Contact Information : Information that allows communication with the individual, such as phone numbers, email addresses or mailing addresses.
    4. Financial Information : Data related to a person’s finances, including credit card numbers, bank account numbers, income records or financial transactions.
    5. Health and Medical Information : Information about a person’s health, medical history or healthcare treatments.
    6. Location Data : Data that can pinpoint a person’s geographical location, such as GPS coordinates or information derived from mobile devices.
    7. Online Identifiers : Information like IP addresses, cookies or other online tracking mechanisms that can be used to identify or track individuals online.
    8. Biometric Data : Unique physical or behavioural characteristics used for identification, such as fingerprints, facial recognition data or voiceprints.

    Sensitive Data

    Sensitive data is a special category of personal data prohibited from processing unless specific conditions are met, including users giving explicit consent. The data must also be necessary to fulfil one or more of a limited set of allowed purposes, such as reasons related to employment, social protections or legal claims.

    Sensitive information includes details about a person’s racial or ethnic origin, sexual orientation, political opinions, religion, trade union membership, biometric data or genetic data.

    What are the 7 main principles of GDPR ?

    The 7 principles of GDPR guide companies in how to properly handle personal data gathered from their users.

    A list of the main principles to follow for GDPR personal data handling

    The seven principles of GDPR are :

    1. Lawfulness, fairness and transparency

    Lawfulness means having legal grounds for data processing, such as consent, legitimate interests, contract and legal obligation. If you can achieve your objective without processing personal data, the basis is no longer lawful.

    Fairness means you’re processing data reasonably and in line with users’ best interests, and they wouldn’t be shocked if they find out what you’re using it for.

    Transparency means being open regarding when you’re processing user data, what you’re using it for and who you’re collecting it from.

    To get started with this, use our guide on creating a GDPR-compliant privacy policy.

    2. Purpose limitation

    You should only process user data for the original purposes you communicated to users when requesting their explicit consent. If you aim to undertake a new purpose, it must be compatible with the original stated purpose. Otherwise, you’ll need to ask for consent again.

    3. Data minimisation

    You should only collect as much data as you need to accomplish compliant objectives and nothing more, especially not other personally identifiable information (PII).

    Matomo provides several features for extensive data minimisation, including the ability to anonymize IP addresses.

    Data minimisation is well-liked by users. Around 70% of people have taken active steps towards protecting their identity online, so they’ll likely appreciate any principles that help them in this effort.

    4. Accuracy

    The user data you process should be accurate and up-to-date where necessary. You should have reasonable systems to catch inaccurate data and correct or delete it. If there are mistakes that you need to store, then you need to label them clearly as mistakes to keep them from being processed as accurate.

    5. Storage limitation

    This principle requires you to eliminate data you’re no longer using for the original purposes. You must implement time limits, after which you’ll delete or anonymize any user data on record. Matomo allows you to configure your system such that logs are automatically deleted after some time.

    6. Integrity and confidentiality

    This requires that data processors have security measures in place to protect data from threats such as hackers, loss and damage. As an open-source web analytics solution, Matomo enables you to verify its security first-hand.

    7. Accountability

    Accountability means you’re responsible for what you do with the data you collect. It’s your duty to maintain compliance and document everything for audits. Matomo tracks a lot of the data you’d need for this, including activity, task and application logs.

    Who does GDPR apply to ?

    The GDPR applies to any company that processes the personal data of EU citizens and residents (regardless of the location of the company). 

    If this is the first time you’ve heard about this, don’t worry ! Matomo provides tools that allow you to determine exactly what kinds of data you’re collecting and how they must be handled for full compliance. 

    Best practices for processing personal data under GDPR

    Companies subject to the GDPR need to be aware of several key principles and best practices to ensure they process personal data in a lawful and responsible manner.

    Here are some essential practices to implement :

    1. Lawful basis for processing : Organisations must have a lawful basis for processing personal data. Common lawful bases include the necessity of processing for compliance with a legal obligation, the performance of a contract, the protection of vital interests and tasks carried out in the public interest. Your organisation’s legitimate interests for processing must not override the individual’s legal rights. 
    2. Data minimisation : Collect and process only the personal data that is necessary for the specific purpose for which it was collected. Matomo’s anonymisation capabilities help you avoid collecting excessive or irrelevant data.
    3. Transparency : Provide clear and concise information to individuals about how their data will be processed. Privacy statements should be clear and accessible to users to allow them to easily understand how their data is used.
    4. Consent : If you are relying on consent as a lawful basis, make sure you design your privacy statements and consent forms to be usable. This lets you ensure that consent is freely given, specific, informed and unambiguous. Also, individuals must be able to withdraw their consent at any time.
    5. Data subject rights : You must have mechanisms in place to uphold the data subject’s individual rights, such as the rights to access, erase, rectify errors and restrict processing. Establish internal processes for handling such requests.
    6. Data protection impact assessments (DPIAs) : Conduct DPIAs for high-risk processing activities, especially when introducing new technologies or processing sensitive data.
    7. Security measures : You must implement appropriate technical security measures to maintain the safety of personal data. This can include ‌security tools such as encryption, firewalls and limited access controls, as well as organisational practices like regular security assessments. 
    8. Data breach response : Develop and maintain a data breach response plan. Notify relevant authorities and affected individuals of data breaches within the required timeframe.
    9. International data transfers : If transferring personal data outside the EU, ensure that appropriate safeguards are in place and consider GDPR provisions. These provisions allow data transfers from the EU to non-EU countries in three main ways :
      1. When the destination country has been deemed by the European Commission to have adequate data protection, making it similar to transferring data within the EU.
      2. Through the use of safeguards like binding corporate rules, approved contractual clauses or adherence to codes of conduct.
      3. In specific situations when none of the above apply, such as when an individual explicitly consents to the transfer after being informed of the associated risks.
    10. Data protection officers (DPOs) : Appoint a data protection officer if required by GDPR. DPOs are responsible for overseeing data protection compliance within the organisation.
    11. Privacy by design and default : Integrate data protection into the design of systems and processes. Default settings should prioritise user privacy, as is the case with something like Matomo’s first-party cookies.
    12. Documentation : Maintain records of data processing activities, including data protection policies, procedures and agreements. Matomo logs and backs up web server access, activity and more, providing a solid audit trail.
    13. Employee training : Employees who handle personal data must be properly trained to uphold data protection principles and GDPR compliance best practices. 
    14. Third-party contracts : If sharing data with third parties, have data processing agreements in place that outline the responsibilities and obligations of each party regarding data protection.
    15. Regular audits and assessments : Conduct periodic audits and assessments of data processing activities to ensure ongoing compliance. As mentioned previously, Matomo tracks and saves several key statistics and metrics that you’d need for a successful audit.
    16. Accountability : Demonstrate accountability by documenting and regularly reviewing compliance efforts. Be prepared to provide evidence of compliance to data protection authorities.
    17. Data protection impact on data analytics and marketing : Understand how GDPR impacts data analytics and marketing activities, including obtaining valid consent for marketing communications.

    Organisations should be on the lookout for GDPR updates, as the regulations may evolve over time. When in doubt, consult legal and privacy professionals to ensure compliance, as non-compliance could potentially result in significant fines, damage to reputation and legal consequences.

    What constitutes a GDPR breach ?

    Security incidents that compromise the confidentiality, integrity and/or availability of personal data are considered a breach under GDPR. This means a breach is not limited to leaks ; if you accidentally lose or delete personal data, its availability is compromised, which is technically considered a breach.

    What are the penalty fines for GDPR non-compliance ?

    The penalty fines for GDPR non-compliance are up to €20 million or up to 4% of the company’s revenue from the previous fiscal year, whichever is higher. This makes it so that small companies can also get fined, no matter how low-profile the breach is.

    In 2022, for instance, a company found to have mishandled user data was fined €2,000, and the webmaster responsible was personally fined €150.

    Is Matomo GDPR compliant ?

    Matomo is fully GDPR compliant and can ensure you achieve compliance, too. Here’s how :

    • Data anonymization and IP anonymization
    • GDPR Manager that helps you identify gaps in your compliance and address them effectively
    • Users can opt-out of all tracking
    • First-party cookies by default
    • Users can view the data collected
    • Capabilities to delete visitor data when requested
    • You own your data and it is not used for any other purposes (like advertising)
    • Visitor logs and profiles can be disabled
    • Data is stored in the EU (Matomo Cloud) or in any country of your choice (Matomo On-Premise)

    Is there a GDPR in the US ?

    There is no GDPR-equivalent law that covers the US as a whole. That said, US-based companies processing data from persons in the EU still need to adhere to GDPR principles.

    While there isn’t a federal data protection law, several states have enacted their own. One notable example is the California Consumer Privacy Act (CCPA), which Matomo is fully compliant with.

    Ready for GDPR-compliant analytics ?

    The GDPR lays out a set of regulations and penalties that govern the collection and processing of personal data from EU citizens and residents. A breach under GDPR attracts a fine of either up to €20 million or 4% of the company’s revenue, and the penalty applies to companies of all sizes.

    Matomo is fully GDPR compliant and provides several features and advanced privacy settings to ensure you ‌are as well, without sacrificing the resources you need for effective analytics. If you’re ready to get started, sign up for a 21-day free trial of Matomo — no credit card required.

    Disclaimer
    We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to GDPR. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.

  • What flags should enable to get maximum performance using ffpeg ?

    19 octobre 2017, par Sam

    I am using windows, my application is using opencv and for codecs, we have used ffmpeg. We see the performance is very slow, we want to improve it by compiling ffmpeg with all flags which could take hardware and GPU acceleation into consideration.
    I did ./configure --help inside the ffmpeg source, I see below list option, can you please tell which all can really imporve the performance. Note that we would like to take advantage of hardware and gpu capabilities.

    $ ./configure —help
    Usage : configure [options]
    Options : [defaults in brackets after descriptions]

    Help options :
    —help print this message
    —quiet Suppress showing informative output
    —list-decoders show all available decoders
    —list-encoders show all available encoders
    —list-hwaccels show all available hardware accelerators
    —list-demuxers show all available demuxers
    —list-muxers show all available muxers
    —list-parsers show all available parsers
    —list-protocols show all available protocols
    —list-bsfs show all available bitstream filters
    —list-indevs show all available input devices
    —list-outdevs show all available output devices
    —list-filters show all available filters

    Standard options :
    —logfile=FILE log tests and output to FILE [ffbuild/config.log]
    —disable-logging do not log configure debug information
    —fatal-warnings fail if any configure warning is generated
    —prefix=PREFIX install in PREFIX [/usr/local]
    —bindir=DIR install binaries in DIR [PREFIX/bin]
    —datadir=DIR install data files in DIR [PREFIX/share/ffmpeg]
    —docdir=DIR install documentation in DIR [PREFIX/share/doc/ffmpeg ]
    —libdir=DIR install libs in DIR [PREFIX/lib]
    —shlibdir=DIR install shared libs in DIR [LIBDIR]
    —incdir=DIR install includes in DIR [PREFIX/include]
    —mandir=DIR install man page in DIR [PREFIX/share/man]
    —pkgconfigdir=DIR install pkg-config files in DIR [LIBDIR/pkgconfig]
    —enable-rpath use rpath to allow installing libraries in paths
    not part of the dynamic linker search path
    use rpath when linking programs (USE WITH CARE)
    —install-name-dir=DIR Darwin directory name for installed targets

    Licensing options :
    —enable-gpl allow use of GPL code, the resulting libs
    and binaries will be under GPL [no]
    —enable-version3 upgrade (L)GPL to version 3 [no]
    —enable-nonfree allow use of nonfree code, the resulting libs
    and binaries will be unredistributable [no]

    Configuration options :
    —disable-static do not build static libraries [no]
    —enable-shared build shared libraries [no]
    —enable-small optimize for size instead of speed
    —disable-runtime-cpudetect disable detecting CPU capabilities at runtime (sma ller binary)
    —enable-gray enable full grayscale support (slower color)
    —disable-swscale-alpha disable alpha channel support in swscale
    —disable-all disable building components, libraries and programs
    —disable-autodetect disable automatically detected external libraries [no ]

    Program options :
    —disable-programs do not build command line programs
    —disable-ffmpeg disable ffmpeg build
    —disable-ffplay disable ffplay build
    —disable-ffprobe disable ffprobe build
    —disable-ffserver disable ffserver build

    Documentation options :
    —disable-doc do not build documentation
    —disable-htmlpages do not build HTML documentation pages
    —disable-manpages do not build man documentation pages
    —disable-podpages do not build POD documentation pages
    —disable-txtpages do not build text documentation pages

    Component options :
    —disable-avdevice disable libavdevice build
    —disable-avcodec disable libavcodec build
    —disable-avformat disable libavformat build
    —disable-swresample disable libswresample build
    —disable-swscale disable libswscale build
    —disable-postproc disable libpostproc build
    —disable-avfilter disable libavfilter build
    —enable-avresample enable libavresample build [no]
    —disable-pthreads disable pthreads [autodetect]
    —disable-w32threads disable Win32 threads [autodetect]
    —disable-os2threads disable OS/2 threads [autodetect]
    —disable-network disable network support [no]
    —disable-dct disable DCT code
    —disable-dwt disable DWT code
    —disable-error-resilience disable error resilience code
    —disable-lsp disable LSP code
    —disable-lzo disable LZO decoder code
    —disable-mdct disable MDCT code
    —disable-rdft disable RDFT code
    —disable-fft disable FFT code
    —disable-faan disable floating point AAN (I)DCT code
    —disable-pixelutils disable pixel utils in libavutil

    Individual component options :
    —disable-everything disable all components listed below
    —disable-encoder=NAME disable encoder NAME
    —enable-encoder=NAME enable encoder NAME
    —disable-encoders disable all encoders
    —disable-decoder=NAME disable decoder NAME
    —enable-decoder=NAME enable decoder NAME
    —disable-decoders disable all decoders
    —disable-hwaccel=NAME disable hwaccel NAME
    —enable-hwaccel=NAME enable hwaccel NAME
    —disable-hwaccels disable all hwaccels
    —disable-muxer=NAME disable muxer NAME
    —enable-muxer=NAME enable muxer NAME
    —disable-muxers disable all muxers
    —disable-demuxer=NAME disable demuxer NAME
    —enable-demuxer=NAME enable demuxer NAME
    —disable-demuxers disable all demuxers
    —enable-parser=NAME enable parser NAME
    —disable-parser=NAME disable parser NAME
    —disable-parsers disable all parsers
    —enable-bsf=NAME enable bitstream filter NAME
    —disable-bsf=NAME disable bitstream filter NAME
    —disable-bsfs disable all bitstream filters
    —enable-protocol=NAME enable protocol NAME
    —disable-protocol=NAME disable protocol NAME
    —disable-protocols disable all protocols
    —enable-indev=NAME enable input device NAME
    —disable-indev=NAME disable input device NAME
    —disable-indevs disable input devices
    —enable-outdev=NAME enable output device NAME
    —disable-outdev=NAME disable output device NAME
    —disable-outdevs disable output devices
    —disable-devices disable all devices
    —enable-filter=NAME enable filter NAME
    —disable-filter=NAME disable filter NAME
    —disable-filters disable all filters
    —disable-v4l2_m2m disable V4L2 mem2mem code [autodetect]

    External library support :

    Using any of the following switches will allow FFmpeg to link to the
    corresponding external library. All the components depending on that library
    will become enabled, if all their other dependencies are met and they are not
    explicitly disabled. E.g. —enable-libwavpack will enable linking to
    libwavpack and allow the libwavpack encoder to be built, unless it is
    specifically disabled with —disable-encoder=libwavpack.

    Note that only the system libraries are auto-detected. All the other external
    libraries must be explicitly enabled.

    Also note that the following help text describes the purpose of the libraries
    themselves, not all their features will necessarily be usable by FFmpeg.

    —disable-alsa disable ALSA support [autodetect]
    —disable-appkit disable Apple AppKit framework [autodetect]
    —disable-avfoundation disable Apple AVFoundation framework [autodetect]
    —enable-avisynth enable reading of AviSynth script files [no]
    —disable-bzlib disable bzlib [autodetect]
    —disable-coreimage disable Apple CoreImage framework [autodetect]
    —enable-chromaprint enable audio fingerprinting with chromaprint [no]
    —enable-frei0r enable frei0r video filtering [no]
    —enable-gcrypt enable gcrypt, needed for rtmp(t)e support
    if openssl, librtmp or gmp is not used [no]
    —enable-gmp enable gmp, needed for rtmp(t)e support
    if openssl or librtmp is not used [no]
    —enable-gnutls enable gnutls, needed for https support
    if openssl is not used [no]
    —disable-iconv disable iconv [autodetect]
    —disable-jack disable libjack support [autodetect]
    —enable-jni enable JNI support [no]
    —enable-ladspa enable LADSPA audio filtering [no]
    —enable-libass enable libass subtitles rendering,
    needed for subtitles and ass filter [no]
    —enable-libbluray enable BluRay reading using libbluray [no]
    —enable-libbs2b enable bs2b DSP library [no]
    —enable-libcaca enable textual display using libcaca [no]
    —enable-libcelt enable CELT decoding via libcelt [no]
    —enable-libcdio enable audio CD grabbing with libcdio [no]
    —enable-libdc1394 enable IIDC-1394 grabbing using libdc1394
    and libraw1394 [no]
    —enable-libfdk-aac enable AAC de/encoding via libfdk-aac [no]
    —enable-libflite enable flite (voice synthesis) support via libflite [ no]
    —enable-libfontconfig enable libfontconfig, useful for drawtext filter [no]
    —enable-libfreetype enable libfreetype, needed for drawtext filter [no]
    —enable-libfribidi enable libfribidi, improves drawtext filter [no]
    —enable-libgme enable Game Music Emu via libgme [no]
    —enable-libgsm enable GSM de/encoding via libgsm [no]
    —enable-libiec61883 enable iec61883 via libiec61883 [no]
    —enable-libilbc enable iLBC de/encoding via libilbc [no]
    —enable-libkvazaar enable HEVC encoding via libkvazaar [no]
    —enable-libmodplug enable ModPlug via libmodplug [no]
    —enable-libmp3lame enable MP3 encoding via libmp3lame [no]
    —enable-libopencore-amrnb enable AMR-NB de/encoding via libopencore-amrnb [no ]
    —enable-libopencore-amrwb enable AMR-WB decoding via libopencore-amrwb [no]
    —enable-libopencv enable video filtering via libopencv [no]
    —enable-libopenh264 enable H.264 encoding via OpenH264 [no]
    —enable-libopenjpeg enable JPEG 2000 de/encoding via OpenJPEG [no]
    —enable-libopenmpt enable decoding tracked files via libopenmpt [no]
    —enable-libopus enable Opus de/encoding via libopus [no]
    —enable-libpulse enable Pulseaudio input via libpulse [no]
    —enable-librsvg enable SVG rasterization via librsvg [no]
    —enable-librubberband enable rubberband needed for rubberband filter [no]
    —enable-librtmp enable RTMP[E] support via librtmp [no]
    —enable-libshine enable fixed-point MP3 encoding via libshine [no]
    —enable-libsmbclient enable Samba protocol via libsmbclient [no]
    —enable-libsnappy enable Snappy compression, needed for hap encoding [n o]
    —enable-libsoxr enable Include libsoxr resampling [no]
    —enable-libspeex enable Speex de/encoding via libspeex [no]
    —enable-libssh enable SFTP protocol via libssh [no]
    —enable-libtesseract enable Tesseract, needed for ocr filter [no]
    —enable-libtheora enable Theora encoding via libtheora [no]
    —enable-libtwolame enable MP2 encoding via libtwolame [no]
    —enable-libv4l2 enable libv4l2/v4l-utils [no]
    —enable-libvidstab enable video stabilization using vid.stab [no]
    —enable-libvmaf enable vmaf filter via libvmaf [no]
    —enable-libvo-amrwbenc enable AMR-WB encoding via libvo-amrwbenc [no]
    —enable-libvorbis enable Vorbis en/decoding via libvorbis,
    native implementation exists [no]
    —enable-libvpx enable VP8 and VP9 de/encoding via libvpx [no]
    —enable-libwavpack enable wavpack encoding via libwavpack [no]
    —enable-libwebp enable WebP encoding via libwebp [no]
    —enable-libx264 enable H.264 encoding via x264 [no]
    —enable-libx265 enable HEVC encoding via x265 [no]
    —enable-libxavs enable AVS encoding via xavs [no]
    —enable-libxcb enable X11 grabbing using XCB [autodetect]
    —enable-libxcb-shm enable X11 grabbing shm communication [autodetect]
    —enable-libxcb-xfixes enable X11 grabbing mouse rendering [autodetect]
    —enable-libxcb-shape enable X11 grabbing shape rendering [autodetect]
    —enable-libxvid enable Xvid encoding via xvidcore,
    native MPEG-4/Xvid encoder exists [no]
    —enable-libxml2 enable XML parsing using the C library libxml2 [no]
    —enable-libzimg enable z.lib, needed for zscale filter [no]
    —enable-libzmq enable message passing via libzmq [no]
    —enable-libzvbi enable teletext support via libzvbi [no]
    —disable-lzma disable lzma [autodetect]
    —enable-decklink enable Blackmagic DeckLink I/O support [no]
    —enable-libndi_newtek enable Newteck NDI I/O support [no]
    —enable-mediacodec enable Android MediaCodec support [no]
    —enable-libmysofa enable libmysofa, needed for sofalizer filter [no]
    —enable-openal enable OpenAL 1.1 capture support [no]
    —enable-opencl enable OpenCL code
    —enable-opengl enable OpenGL rendering [no]
    —enable-openssl enable openssl, needed for https support
    if gnutls is not used [no]
    —disable-sndio disable sndio support [autodetect]
    —disable-schannel disable SChannel SSP, needed for TLS support on
    Windows if openssl and gnutls are not used [autodetec t]
    —disable-sdl2 disable sdl2 [autodetect]
    —disable-securetransport disable Secure Transport, needed for TLS support
    on OSX if openssl and gnutls are not used [autodetect ]
    —disable-xlib disable xlib [autodetect]
    —disable-zlib disable zlib [autodetect]

    The following libraries provide various hardware acceleration features :
    —disable-audiotoolbox disable Apple AudioToolbox code [autodetect]
    —disable-cuda disable dynamically linked Nvidia CUDA code [autodete ct]
    —enable-cuda-sdk enable CUDA features that require the CUDA SDK [no]
    —disable-cuvid disable Nvidia CUVID support [autodetect]
    —disable-d3d11va disable Microsoft Direct3D 11 video acceleration code [autodetect]
    —disable-dxva2 disable Microsoft DirectX 9 video acceleration code [ autodetect]
    —enable-libdrm enable DRM code (Linux) [no]
    —enable-libmfx enable Intel MediaSDK (AKA Quick Sync Video) code via libmfx [no]
    —enable-libnpp enable Nvidia Performance Primitives-based code [no]
    —enable-mmal enable Broadcom Multi-Media Abstraction Layer (Raspbe rry Pi) via MMAL [no]
    —disable-nvenc disable Nvidia video encoding code [autodetect]
    —enable-omx enable OpenMAX IL code [no]
    —enable-omx-rpi enable OpenMAX IL code for Raspberry Pi [no]
    —enable-rkmpp enable Rockchip Media Process Platform code [no]
    —disable-vaapi disable Video Acceleration API (mainly Unix/Intel) co de [autodetect]
    —disable-vda disable Apple Video Decode Acceleration code [autodet ect]
    —disable-vdpau disable Nvidia Video Decode and Presentation API for Unix code [autodetect]
    —disable-videotoolbox disable VideoToolbox code [autodetect]

    Toolchain options :
    —arch=ARCH select architecture []
    —cpu=CPU select the minimum required CPU (affects
    instruction selection, may crash on older CPUs)
    —cross-prefix=PREFIX use PREFIX for compilation tools []
    —progs-suffix=SUFFIX program name suffix []
    —enable-cross-compile assume a cross-compiler is used
    —sysroot=PATH root of cross-build tree
    —sysinclude=PATH location of cross-build system headers
    —target-os=OS compiler targets OS []
    —target-exec=CMD command to run executables on target
    —target-path=DIR path to view of build directory on target
    —target-samples=DIR path to samples directory on target
    —tempprefix=PATH force fixed dir/prefix instead of mktemp for checks
    —toolchain=NAME set tool defaults according to NAME
    —nm=NM use nm tool NM [nm -g]
    —ar=AR use archive tool AR [ar]
    —as=AS use assembler AS []
    —ln_s=LN_S use symbolic link tool LN_S [ln -s -f]
    —strip=STRIP use strip tool STRIP [strip]
    —windres=WINDRES use windows resource compiler WINDRES [windres]
    —x86asmexe=EXE use nasm-compatible assembler EXE [nasm]
    —cc=CC use C compiler CC [gcc]
    —cxx=CXX use C compiler CXX [g++]
    —objcc=OCC use ObjC compiler OCC [gcc]
    —dep-cc=DEPCC use dependency generator DEPCC [gcc]
    —nvcc=NVCC use Nvidia CUDA compiler NVCC [nvcc]
    —ld=LD use linker LD []
    —pkg-config=PKGCONFIG use pkg-config tool PKGCONFIG [pkg-config]
    —pkg-config-flags=FLAGS pass additional flags to pkgconf []
    —ranlib=RANLIB use ranlib RANLIB [ranlib]
    —doxygen=DOXYGEN use DOXYGEN to generate API doc [doxygen]
    —host-cc=HOSTCC use host C compiler HOSTCC
    —host-cflags=HCFLAGS use HCFLAGS when compiling for host
    —host-cppflags=HCPPFLAGS use HCPPFLAGS when compiling for host
    —host-ld=HOSTLD use host linker HOSTLD
    —host-ldflags=HLDFLAGS use HLDFLAGS when linking for host
    —host-libs=HLIBS use libs HLIBS when linking for host
    —host-os=OS compiler host OS []
    —extra-cflags=ECFLAGS add ECFLAGS to CFLAGS []
    —extra-cxxflags=ECFLAGS add ECFLAGS to CXXFLAGS []
    —extra-objcflags=FLAGS add FLAGS to OBJCFLAGS []
    —extra-ldflags=ELDFLAGS add ELDFLAGS to LDFLAGS []
    —extra-ldexeflags=ELDFLAGS add ELDFLAGS to LDEXEFLAGS []
    —extra-ldlibflags=ELDFLAGS add ELDFLAGS to LDLIBFLAGS []
    —extra-libs=ELIBS add ELIBS []
    —extra-version=STRING version string suffix []
    —optflags=OPTFLAGS override optimization-related compiler flags
    —nvccflags=NVCCFLAGS override nvcc flags [-gencode arch=compute_30,code=sm _30 -O2]
    —build-suffix=SUFFIX library name suffix []
    —enable-pic build position-independent code
    —enable-thumb compile for Thumb instruction set
    —enable-lto use link-time optimization
    —env="ENV=override" override the environment variables

    Advanced options (experts only) :
    —malloc-prefix=PREFIX prefix malloc and related names with PREFIX
    —custom-allocator=NAME use a supported custom allocator
    —disable-symver disable symbol versioning
    —enable-hardcoded-tables use hardcoded tables instead of runtime generation
    —disable-safe-bitstream-reader
    disable buffer boundary checking in bitreaders
    (faster, but may crash)
    —sws-max-filter-size=N the max filter size swscale uses [256]

    Optimization options (experts only) :
    —disable-asm disable all assembly optimizations
    —disable-altivec disable AltiVec optimizations
    —disable-vsx disable VSX optimizations
    —disable-power8 disable POWER8 optimizations
    —disable-amd3dnow disable 3DNow ! optimizations
    —disable-amd3dnowext disable 3DNow ! extended optimizations
    —disable-mmx disable MMX optimizations
    —disable-mmxext disable MMXEXT optimizations
    —disable-sse disable SSE optimizations
    —disable-sse2 disable SSE2 optimizations
    —disable-sse3 disable SSE3 optimizations
    —disable-ssse3 disable SSSE3 optimizations
    —disable-sse4 disable SSE4 optimizations
    —disable-sse42 disable SSE4.2 optimizations
    —disable-avx disable AVX optimizations
    —disable-xop disable XOP optimizations
    —disable-fma3 disable FMA3 optimizations
    —disable-fma4 disable FMA4 optimizations
    —disable-avx2 disable AVX2 optimizations
    —disable-aesni disable AESNI optimizations
    —disable-armv5te disable armv5te optimizations
    —disable-armv6 disable armv6 optimizations
    —disable-armv6t2 disable armv6t2 optimizations
    —disable-vfp disable VFP optimizations
    —disable-neon disable NEON optimizations
    —disable-inline-asm disable use of inline assembly
    —disable-x86asm disable use of standalone x86 assembly
    —disable-mipsdsp disable MIPS DSP ASE R1 optimizations
    —disable-mipsdspr2 disable MIPS DSP ASE R2 optimizations
    —disable-msa disable MSA optimizations
    —disable-mipsfpu disable floating point MIPS optimizations
    —disable-mmi disable Loongson SIMD optimizations
    —disable-fast-unaligned consider unaligned accesses slow

    Developer options (useful when working on FFmpeg itself) :
    —disable-debug disable debugging symbols
    —enable-debug=LEVEL set the debug level []
    —disable-optimizations disable compiler optimizations
    —enable-extra-warnings enable more compiler warnings
    —disable-stripping disable stripping of executables and shared libraries
    —assert-level=level 0(default), 1 or 2, amount of assertion testing,
    2 causes a slowdown at runtime.
    —enable-memory-poisoning fill heap uninitialized allocated space with arbitra ry data
    —valgrind=VALGRIND run "make fate" tests through valgrind to detect memo ry
    leaks and errors, using the specified valgrind binary .
    Cannot be combined with —target-exec
    —enable-ftrapv Trap arithmetic overflows
    —samples=PATH location of test samples for FATE, if not set use
    $FATE_SAMPLES at make invocation time.
    —enable-neon-clobber-test check NEON registers for clobbering (should be
    used only for debugging purposes)
    —enable-xmm-clobber-test check XMM registers for clobbering (Win64-only ;
    should be used only for debugging purposes)
    —enable-random randomly enable/disable components
    —disable-random
    —enable-random=LIST randomly enable/disable specific components or
    —disable-random=LIST component groups. LIST is a comma-separated list
    of NAME[:PROB] entries where NAME is a component
    (group) and PROB the probability associated with
    NAME (default 0.5).
    —random-seed=VALUE seed value for —enable/disable-random
    —disable-valgrind-backtrace do not print a backtrace under Valgrind
    (only applies to —disable-optimizations builds)
    —enable-osfuzz Enable building fuzzer tool
    —libfuzzer=PATH path to libfuzzer
    —ignore-tests=TESTS comma-separated list (without "fate-" prefix
    in the name) of tests whose result is ignored
    —enable-linux-perf enable Linux Performance Monitor API

    NOTE : Object files are built at the place where configure is launched.

  • Revision 32596 : minuscules et fin pour aujourd’hui

    1er novembre 2009, par fil@… — Log

    minuscules et fin pour aujourd’hui