Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (63)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

Sur d’autres sites (12626)

  • 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'&#xA;<outputpath>bin/Build/</outputpath>.
    2. &#xA;

    3. 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).
    4. &#xA;

    5. Building with different configuration and platforms.
    6. &#xA;

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

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

    11. Setting the configuration and platform manually in the Configuration Manager GUI in&#xA;Visual Studio.
    12. &#xA;

    &#xA;

    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.

    &#xA;

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

    &#xA;

  • Setup FFMpegCore in Visual Studio 2019

    27 juillet 2022, par DsiakMondala

    I am confused on the basics of using a library. I understand that there is a library called FFMpeg and a wrapper called FFMpegCore so we can use FFMpeg with C#, correct ? I downloaded both FFMpeg and FFMpegCore and I have them in my project's folder. Although I didn't perceive any class named FFMpegOptions in either of the file's folders.&#xA;I am stuck on how to actually set it up so I can use it in my little project, I never downloaded someone's library before. Can somebody please walk me though the motions of connecting the three of them together ?

    &#xA;

    So far I experimented with :

    &#xA;

      &#xA;
    • Add a reference to my project, but there doesn't seem to be any .dll, .tlb, .olb, .ocx or .exe files to add
    • &#xA;

    • Add an existing project to my solution. There is a project called FFMpegCore.csproj but adding it raises a missing SDK error. Weirdly enough, opening the same project as a standalone doesn't raise any issues which makes me thing the operation I am trying is inadequate.
    • &#xA;

    &#xA;

    I am sure this is a silly and easy setup to perform but I just don't know enough to find a solution.

    &#xA;

  • Can't link FFMPEG dynamically to VS 2019 project

    10 février 2021, par Maya Sela

    I downloaded the source code of FFMPEG 3.4.8 and built with MSVC as such :
    &#xA;After unzipping, open x86_x64 Cross Tools Command Prompt for VS 2019 and run msys2_shell.cmd. From there, run
    &#xA;./configure --toolchain=msvc --arch=x86_64 --enable-yasm --enable-asm --enable-shared --disable-static&#xA;and&#xA;make&#xA;
    &#xA;I then created a new project in VS 2019.
    &#xA;In Properties > C/C++ > General > Additional Include Directories :
    &#xA;(Where all the headers are)

    &#xA;

    E:\ffmpeg-3.4.8\libavutil&#xA;E:\ffmpeg-3.4.8\libavcodec&#xA;E:\ffmpeg-3.4.8\libavdevice&#xA;E:\ffmpeg-3.4.8\libavfilter&#xA;E:\ffmpeg-3.4.8\libavresample&#xA;E:\ffmpeg-3.4.8\libpostproc&#xA;E:\ffmpeg-3.4.8\libswscale&#xA;E:\ffmpeg-3.4.8\libswresample&#xA;E:\ffmpeg-3.4.8\libavformat&#xA;

    &#xA;

    In Properties > Linker > General > Additional Library Directories :
    &#xA;(Where the .lib files are)

    &#xA;

    E:\ffmpeg-3.4.8\libavutil&#xA;E:\ffmpeg-3.4.8\libavcodec&#xA;E:\ffmpeg-3.4.8\libavdevice&#xA;E:\ffmpeg-3.4.8\libavfilter&#xA;E:\ffmpeg-3.4.8\libavresample&#xA;E:\ffmpeg-3.4.8\libpostproc&#xA;E:\ffmpeg-3.4.8\libswscale&#xA;E:\ffmpeg-3.4.8\libswresample&#xA;E:\ffmpeg-3.4.8\libavformat&#xA;

    &#xA;

    In Properties > Linker > Input > Additional Dependencies :

    &#xA;

    avcodec.lib&#xA;avdevice.lib&#xA;avfilter.lib&#xA;avformat.lib&#xA;swresample.lib&#xA;swscale.lib&#xA;

    &#xA;

    For good measure, I copied the .dll files of each library to the Release folder of the project. There is one source file I am trying to build and run :

    &#xA;

    &#xA;extern "C" {&#xA;#include <libavformat></libavformat>avformat.h>&#xA;}&#xA;&#xA;int main() {&#xA;    AVFormatContext* pFormatContext = avformat_alloc_context();&#xA;}&#xA;

    &#xA;

    The result is as follows :

    &#xA;

    1>------ Build started: Project: FFMPEG_example, Configuration: Release x64 ------&#xA;1>Source.cpp&#xA;1>Source.obj : error LNK2001: unresolved external symbol avformat_alloc_context&#xA;1>C:\Users\maya.s\source\repos\FFMPEG_example\x64\Release\FFMPEG_example.exe : fatal error LNK1120: 1 unresolved externals&#xA;1>Done building project "FFMPEG_example.vcxproj" -- FAILED.&#xA;========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========&#xA;

    &#xA;

    Does anyone have an idea ?
    &#xA;Thanks !

    &#xA;