Recherche avancée

Sur d’autres sites (8556)

• Anomalie #4787 (Nouveau) : Le selecteur d’article ne marche plus.

  20 mai 2021, par Maïeul Rouquette

  Soit un page du privé

  prive/squelettes/contenu/titi.html, appelé via ecrire/?exec=titi.

  En spip 3.2
  

  selecteur/articles,name=toto,rubriques=1,articles=1}/>

  
  permet de selection un article.

  pas en spip 4 (et donc ce n’est pas lié à saisies !)

  J’ai du mal à comprendre exactement le picker, mais en 3.2 pour les rubriques racine j’ai

  <li class="rubrique"> <a href="#"><img class="add" src="http://core.spip.org/projects/prive/themes/spip/images/ajouter-16.png" alt="ajouter" width='16' height='16' /></a>AH
   <a class="ajax bind-ajax" href="http://core.spip.org/projects/spip/?exec=titi&#38;picker=1&#38;id_r=1"><img src="http://core.spip.org/projects/prive/themes/spip/images/fleche-droite-16.png" alt="" class="ouvrir" width='16' height='16' /></a></li>

  alors qu’en 4.0 (commit 604e76ddf) j’ai
  

  <li class="rubrique"> <a href="#"><img class="add" src="http://core.spip.org/projects/prive/themes/spip/images/ajouter-xx.svg?16px" alt="ajouter" width='16' height='16' /></a>blop</li>

  
  il manque le second a en bidn-ajax
  j’ai pas investigué plus que cela, car c’est un domaine obscure pour moi.

• 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.
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 ?

  


  So far I experimented with :

  


  

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

  


  • 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.

  


  


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

  


• 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