Recherche avancée

Sur d’autres sites (7939)

• cygwin make errors : ffmpeg compile with ndk

  1er mars 2013, par Bryce

  Recently I'm compiling ffmpeg for android with ndk and I do this as this article(http://vec.io/posts/how-to-build-ffmpeg-with-android-ndk ). configure is right,
  but when I begin to make, it makes errors.
  configure shell :

  export TMPDIR=D:/temp/android
  
  export NDK=/cygdrive/D/DevelopKit/android-ndk-r8d
  
  export PATH=/cygdrive/C/cygwin/tmp/ffmpeg/bin:$PATH
  
  export CC=arm-linux-androideabi-gcc
  
  export LD=arm-linux-androideabi-ld
  
  export AR=arm-linux-androideabi-ar
  
  export C_INCLUDE_PATH=/cygdrive/C/cygwin/tmp/ffmpeg/sysroot/usr/include
  
  export LIBRARY_PATH=/cygdrive/C/cygwin/tmp/ffmpeg/sysroot/usr/lib
  
  CFLAGS="-O3 -Wall -mthumb -pipe -fpic -fasm \
  
    -finline-limit=300 -ffast-math \
  
    -fstrict-aliasing -Werror=strict-aliasing \
  
    -fmodulo-sched -fmodulo-sched-allow-regmoves \
  
    -Wno-psabi -Wa,--noexecstack \
  
    -D__ARM_ARCH_5__ -D__ARM_ARCH_5E__ \
  
    -D__ARM_ARCH_5T__ -D__ARM_ARCH_5TE__ \
  
    -DANDROID -DNDEBUG"
  
  
  
  EXTRA_CFLAGS="-march=armv7-a -mfpu=neon -mfloat-abi=softfp -mvectorize-with-neon-quad"
  
  EXTRA_LDFLAGS="-Wl,--fix-cortex-a8"
  
  
  
  FFMPEG_FLAGS="--prefix=/tmp/ffmpeg/build \
  
    --target-os=linux \
  
    --arch=arm \
  
    --enable-cross-compile \
  
    --cross-prefix=arm-linux-androideabi- \
  
    --enable-shared \
  
    --disable-symver \
  
    --disable-doc \
  
    --disable-ffplay \
  
    --disable-ffmpeg \
  
    --disable-ffprobe \
  
    --disable-ffserver \
  
    --disable-avdevice \
  
    --disable-avfilter \
  
    --disable-encoders  \
  
    --disable-muxers \
  
    --disable-filters \
  
    --disable-devices \
  
    --disable-everything \
  
    --enable-protocols  \
  
    --enable-parsers \
  
    --enable-demuxers \
  
    --disable-demuxer=sbg \
  
    --enable-decoders \
  
    --enable-bsfs \
  
    --enable-network \
  
    --enable-swscale  \
  
    --enable-asm \
  
    --enable-version3"
  
  
  
  ./configure $FFMPEG_FLAGS --extra-cflags="$CFLAGS $EXTRA_CFLAGS" --extra-ldflags="$EXTRA_LDFLAGS"

  Configure Result(Part of config.mak) :

  ifndef FFMPEG_CONFIG_MAK
  
  FFMPEG_CONFIG_MAK=1
  
  FFMPEG_CONFIGURATION=--prefix=/tmp/ffmpeg/build --target-os=linux --arch=arm --enable-cross-compile --cross-prefix=arm-linux-androideabi- --enable-shared --disable-symver --disable-doc --disable-ffplay --disable-ffmpeg --disable-ffprobe --disable-ffserver --disable-avdevice --disable-avfilter --disable-encoders --disable-muxers --disable-filters --disable-devices --disable-everything --enable-protocols --enable-parsers --enable-demuxers --disable-demuxer=sbg --enable-decoders --enable-bsfs --enable-network --enable-swscale --enable-asm --enable-version3 --extra-cflags='-O3 -Wall -mthumb -pipe -fpic -fasm   -finline-limit=300 -ffast-math   -fstrict-aliasing -Werror=strict-aliasing   -fmodulo-sched -fmodulo-sched-allow-regmoves   -Wno-psabi -Wa,--noexecstack   -D__ARM_ARCH_5__ -D__ARM_ARCH_5E__   -D__ARM_ARCH_5T__ -D__ARM_ARCH_5TE__   -DANDROID -DNDEBUG -march=armv7-a -mfpu=neon -mfloat-abi=softfp -mvectorize-with-neon-quad' --extra-ldflags='-Wl,--fix-cortex-a8'
  
  prefix=/tmp/ffmpeg/build
  
  LIBDIR=$(DESTDIR)${prefix}/lib
  
  SHLIBDIR=$(DESTDIR)${prefix}/lib
  
  INCDIR=$(DESTDIR)${prefix}/include
  
  BINDIR=$(DESTDIR)${prefix}/bin
  
  DATADIR=$(DESTDIR)${prefix}/share/ffmpeg
  
  MANDIR=$(DESTDIR)${prefix}/share/man
  
  SRC_PATH=.
  
  ifndef MAIN_MAKEFILE
  
  SRC_PATH:=$(SRC_PATH:.%=..%)
  
  endif
  
  CC_IDENT=gcc 4.6
  
   (GCC)
  
  ARCH=arm
  
  CC=arm-linux-androideabi-gcc
  
  CXX=arm-linux-androideabi-g++
  
  AS=arm-linux-androideabi-gcc
  
  LD=arm-linux-androideabi-gcc
  
  DEPCC=arm-linux-androideabi-gcc
  
  DEPCCFLAGS= $(CPPFLAGS)
  
  DEPAS=arm-linux-androideabi-gcc
  
  DEPASFLAGS= $(CPPFLAGS)
  
  YASM=yasm
  
  DEPYASM=yasm
  
  AR=arm-linux-androideabi-ar
  
  ARFLAGS=rc
  
  AR_O=$@

  But when I make it

  CC  libavformat/4xm.o
  
  In file included from ./libavutil/bswap.h:35:0,
  
                   from ./libavutil/intreadwrite.h:25,
  
                   from libavformat/4xm.c:30:
  
  ./config.h:8:18: warning: missing terminating " character [enabled by default]
  
  In file included from ./libavutil/bswap.h:35:0,
  
                   from ./libavutil/intreadwrite.h:25,
  
                   from libavformat/4xm.c:30:
  
  ./config.h:9:7: warning: missing terminating " character [enabled by default]
  
  ./config.h:9:2: error: missing terminating " character
  
  In file included from ./libavutil/intreadwrite.h:25:0,
  
                   from libavformat/4xm.c:30:
  
  ./libavutil/bswap.h:58:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'static'
  
  common.mak:48: recipe for target `libavformat/4xm.o' failed
  
  make: *** [libavformat/4xm.o] Error 1

  It is the character error and I guess it is the windows character(I'm using cygwin), I tried dos2unix but it didn't work. Please help me and thanks for advising.

• ffmpeg user agent not working

  19 janvier 2017, par mattauckland

  I’ve installed ffmpeg on CentOS and it has been happily encoding files audio files for the last year, no problem.

  However, I would like to use it to access an audio stream now, to replace a clunky bit of php code I currently use, but I would like to apply a custom User Agent so my clients recognise the incoming connection.

  I’ve tried -user-agent, -user_agent, and -headers but all three are returning "Unrecognized option".

  The code I’m using, excluding the user agent, is :

  ffmpeg -t 3600 -i http://my.radio.com:8000/1 -vn -ar 44100 -ac 2 -ab 128k -f mp3 /var/www/vhosts/mywebsite.com/httpdocs/test.mp3

  And that works no problem, but when I try to add either -user_agent, -user-agent, or -headers it fails with the above error.

  If it helps, the version info is :

  FFmpeg version 0.6.5, Copyright (c) 2000-2010 the FFmpeg developers
  
    built on Jan 29 2012 17:52:15 with gcc 4.4.5 20110214 (Red Hat 4.4.5-6)
  
    configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --incdir=/usr/include --disable-avisynth --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC' --enable-avfilter --enable-avfilter-lavf --enable-libdc1394 --enable-libdirac --enable-libfaac --enable-libfaad --enable-libfaadbin --enable-libgsm --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libx264 --enable-gpl --enable-nonfree --enable-postproc --enable-pthreads --enable-shared --enable-swscale --enable-vdpau --enable-version3 --enable-x11grab
  
    libavutil     50.15. 1 / 50.15. 1
  
    libavcodec    52.72. 2 / 52.72. 2
  
    libavformat   52.64. 2 / 52.64. 2
  
    libavdevice   52. 2. 0 / 52. 2. 0
  
    libavfilter    1.19. 0 /  1.19. 0
  
    libswscale     0.11. 0 /  0.11. 0
  
    libpostproc   51. 2. 0 / 51. 2. 0
  
  FFmpeg 0.6.5
  
  libavutil     50.15. 1 / 50.15. 1
  
  libavcodec    52.72. 2 / 52.72. 2
  
  libavformat   52.64. 2 / 52.64. 2
  
  libavdevice   52. 2. 0 / 52. 2. 0
  
  libavfilter    1.19. 0 /  1.19. 0
  
  libswscale     0.11. 0 /  0.11. 0
  
  libpostproc   51. 2. 0 / 51. 2. 0

  Thanks in advance !

• Piwik SSO options and why is it useful ?

  8 novembre 2017, par Piwik Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Piwik at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Piwik has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Piwik features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Piwik plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Piwik. It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://piwik.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Piwik account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Piwik can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Piwik with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Piwik for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Piwik core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Piwik is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Piwik.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.piwik.org/guides/getting-started-part-1.