sfml-mingw64.nuspec

<?xml version="1.0" encoding="utf-8"?>
<!-- You can embed software files directly into packages, as long as you are not bound by distribution rights. -->
<!-- * If you are an organization making private packages, you probably have no issues here -->
<!-- * If you are releasing to the community feed, you need to consider distribution rights. -->
<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
  <metadata>
    <id>sfml-mingw64</id>
    <version>2.5.1</version>
    <title>SFML (MinGW 64bit)</title>
    <authors>Laurent Gamola</authors>
    <owners>Jean-Michel Boulcourt</owners>
    <projectUrl>https://www.sfml-dev.org/</projectUrl>
    <iconUrl>https://www.sfml-dev.org/download/goodies/sfml-icon-small.png</iconUrl>
	  <packageSourceUrl>https://github.com/jeanmimib/chocolatey-packages/sfml</packageSourceUrl>
    <projectSourceUrl>https://github.com/SFML/SFML</projectSourceUrl>
    <docsUrl>https://www.sfml-dev.org/learn.php</docsUrl>
    <tags>sfml C++ windows mingw64</tags>
    <summary>SFML provides a simple interface to the various components of your PC, to ease the development of games and multimedia applications. 
      It is composed of five modules: system, window, graphics, audio and network.
    </summary>
    <description>With SFML, your application can compile and run out of the box on the most common operating systems: Windows, Linux, Mac OS X and soon Android and iOS.
      SFML has official bindings for the C and .Net languages. And thanks to its active community, it is also available in many other languages such as Java, Ruby, Python, Go, and more.
    </description>
    <releaseNotes>Change log is [here](https://www.sfml-dev.org/changelog.php#sfml-2.5.1).</releaseNotes>
    <dependencies>
      <dependency id="mingw" version="7.3.0" />
      <dependency id="" />
    </dependencies>
  </metadata>
  <files>
    <!-- this section controls what actually gets packaged into the Chocolatey package -->
    <file src="tools\**" target="tools" />
    <!--Building from Linux? You may need this instead: <file src="tools/**" target="tools" />-->
  </files>
</package>