Recherche avancée

Sur d’autres sites (8792)

• Building FFMPEG for Visual Studio development

  28 juillet 2016, par gboy

  I’m trying to use ffmpeg in Visual Studio 2013 C++ software (ultimately as part of an OpenCV project) - but right now I’m just trying to get basic FFMPEG functionality. In general, when building in Visual Studio, I build 64—bit software with Multi-threaded DLL runtime libraries. I have built ffmpeg using the general instructions for ’Native Windows compilation using ... MinGW-w64’ at http://ffmpeg.org/platform.html#Windows (I provide a more detailed set of steps I followed below...).

  After building the ffmpeg software on my system, I tried to create a simple ’hello world’ project in Visual Studio 2013. Specifically, I tried to implement the initial tutorial file presented at http://dranger.com/ffmpeg/tutorial01.html. Upon building the project, I get the error :

  c :\msys64\usr\local\ffmpeg\libavutil\common.h(45) : fatal error C1083 : Cannot
  open include file : ’libavutil/avconfig.h’ : No such file or directory

  The following are the detailed steps I took to build ffmpeg and create my basic Visual Studio project :

  ============ Building ffmpeg ===============

  1. Downloaded and intalled msys2-x86_64-20160205.exe from http://msys2.github.io
  2. Ran update-core to update the Msys2 install
  3. Ran pacman -Suu (twice) to complete the update (following the instructions about updating shortcuts, etc.)
  4. Then I quit out of the MSys2 shell and opened the MinGW-w64 Win64 Shell. In this new shell :
  5. Installed the following packages using pacman -S The list of packages I installed is : make, pkg-config, diffutils, mingw-w64-x86_64-yasm, mingw-w64-x86_64-gcc, mingw-w64-x86_64-SDL, git
  6. Then I cd’d into cd /usr/local
  7. Ran git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
  8. I wanted to build the ffmpeg library ’out-of-tree’ of this MSys64 folder. So, in the regular file system of my Windows machine I created a folder at C :\ffmpeg
  9. Back in the Win64 Shell, I cd’d to this new folder : cd /c/ffmpeg
  10. Then ran /usr/loca/ffmpeg/configure --enable-shared
  11. Then make -r
  12. And, finally make install

  Now, if I had to guess, my ’flaw’ was in the options I used when calling the ’configure’ script of ffmpeg. Do I need to use particular options so that I can take the ffmpeg libraries built here and use them as dynamic (DLL) libraries in Visual Studio ?

  ========== Configuring my Visual Studio Project ============

  Here’s how I created a simple hello world project in Visual Studio to see if ffmpeg is working.

  1. I created a new Visual C++ ’Empty Project’ in Visual Studio 2013

  2. I then configured the project properties as follows :

     a. In C/C++ => General => Additional Include Directories, I put

     C :\msys64\usr\local\ffmpeg

     b. In Linker=>General => Additional Library Directories, I pointed to each of the built library folders (basically I pointed at all of the libraries that were built to ensure I was not inadvertently missing the critical one). The list is as follows :

     • C :\ffmpeg\libavcodec
     • C :\ffmpeg\libavdevice
     • C :\ffmpeg\libavfilter
     • C :\ffmpeg\libavformat
     • C :\ffmpeg\libavutil
     • C :\ffmpeg\libswresample
     • C :\ffmpeg\libswscale
     • C :\ffmpeg

     c. In Linker=> Input => Additional Dependencies, I pointed to the particular libraries (again - I pointed to all of the ones present). The list is :

     • avcodec.lib
     • avdevice.lib
     • avfilter.lib
     • avformat.lib
     • avutil.lib
     • swresample.lib
     • swscale.lib

  3. I then created a new source file called ’tut01.c’ and copied/pasted the code from http://dranger.com/ffmpeg/tutorial01.c

  4. Then hit F7 and got the error specified above about not finding avconfig.h

  The above is my best guess as to the steps I need to follow to get this working in Windows (btw, it’s Windows 10, 64-bit) & Microsoft Visual Studio 2013. What should I change to get this basic program to build and run ?

• Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project

  23 juillet 2022, par mhadi

  In an effort to integrate FFmpeg with Unity, I have been trying to build a solution file in Visual Studio 2019. However, I am currently unable to resolve the following error when I try to build in Visual Studio :

  


  


  The BaseOutputPath/OutputPath property is not set for project
'FFmpegUnityInterop.vcxproj'. Please check to make sure that you have
specified a valid combination of Configuration and Platform for this
project. Configuration='Release' Platform='x64'. This error may
also appear if some other project is trying to follow a
project-to-project reference to this project, this project has been
unloaded or is not included in the solution, and the referencing
project does not build using the same or an equivalent Configuration
or Platform.

  


  


  I have tried a number of solutions, including :

  


  

  1. Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'
<outputpath>bin/Build/</outputpath>.

  


  2. In the FFmpegUnityInterop.vcxproj file, moving the ProjectProperty with my preferred configuration and platform combination to the very top of the list of ProjectProperties (there are 8 of them).

  


  3. Building with different configuration and platforms.

  


  4. Trying to build from VS Dev Command prompt using the following command :
MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64", as well as from the Visual Studio IDE.

  


  5. Tried setting the OutputPath in the command line command
(>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug), only to have
MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one
project can be specified.)

  


  6. Setting the configuration and platform manually in the Configuration Manager GUI in
Visual Studio.

  


  


  I may have missed an attempted solution or two above, but I've tried most of the suggestions I found online, only to get the error pasted above. Part of me suspects that my compilation of FFmpeg libraries didn't execute fully, but I unfortunately do not have enough experience to verify that. Any suggestions to resolve this would be much appreciated.

  


  PS. The project was developed privately by a private entity that is currently unreachable

  


• Fixes for Sun Studio/Forte ; us AC_C_INLINE to detect inline keyword for compiler...

  3 janvier 2009, par jcoalson

  Fixes for Sun Studio/Forte ; us AC_C_INLINE to detect inline keyword for compiler...