update docs

Author: electronstudio

BUILDING.rst

@@ -4,16 +4,30 @@ Building from source
 Have Pip build from source
 --------------------------
 
-Useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.
+This is useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.
 
-Make sure Raylib is installed and then:
+First make sure Raylib is installed.  On Linux/Mac it must include the pkg-config files.  Best way to ensure this
+is to compile and install Raylib using CMake: https://github.com/raysan5/raylib/wiki/Working-on-GNU-Linux#build-raylib-using-cmake
+
+::
+
+      cd raylib-4.0.0
+      mkdir build
+      cd build
+      cmake  -DWITH_PIC=on -DCMAKE_BUILD_TYPE=Release ..
+      make
+      sudo make install
+
+
+
+Then ask Pip to build from source:
 
 ::
 
    pip3 install --no-binary raylib --upgrade --force-reinstall raylib
 
-Build from source manually
---------------------------
+Or, Build from source manually
+------------------------------
 
 Useful if the Pip build doesn’t work and you want to debug it, or you want to contribute to the
 project.
@@ -22,7 +36,7 @@ project.
    If the Pip build doesn’t work, please submit a bug. (And if you have
    fixed it, a PR.)
 
-Manual instructions follow, but see also how we actually build the wheels
+Manual instructions follow, but may be outdated, so see also how we actually build the wheels
 at https://github.com/electronstudio/raylib-python-cffi/blob/master/.github/workflows/build.yml
 
 Windows manual build
@@ -207,6 +221,10 @@ Build and install module.
 Raspberry Pi
 ~~~~~~~~~~~~
 
+Latest info: https://github.com/electronstudio/raylib-python-cffi/issues/55#issuecomment-1012629701
+
+Old possibly out of date info that was written for RPi3 and Raylib 3 follows.
+
 The integrated GPU hardware in a Raspberry Pi (“VideoCore”) is rather
 idiosyncratic, resulting in a complex set of software options. Probably
 the most interesting two options for Raylib applications are:

README.md

@@ -68,8 +68,11 @@ Use [the C API](https://electronstudio.github.io/raylib-python-cffi/raylib.html)
 
 Use [the Python API](https://electronstudio.github.io/raylib-python-cffi/pyray.html).
 
+# App showcase
 
+[Tanki](https://github.com/pkulev/tanki)
 
+Add your app here!
 
 # RLZero
 

create_stub_pyray.py

@@ -27,6 +27,8 @@ def ctype_to_python_type(t):
         return 'None'
     elif t == "long":
         return "int"
+    elif t == "unsigned long long":
+        return "int"
     elif t == "double":
         return "float"
     elif "char *" in t:

create_stub_static.py

@@ -30,6 +30,8 @@ def ctype_to_python_type(t):
         return 'None'
     elif t == "long":
         return "int"
+    elif t == "unsigned long long":
+        return "int"
     elif t == "double":
         return "float"
     elif "char *" in t:

docs/BUILDING.html

@@ -36,10 +36,11 @@
         </div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
               <p class="caption"><span class="caption-text">Contents:</span></p>
 <ul class="current">
-<li class="toctree-l1"><a class="reference internal" href="README.html">Python Bindings for Raylib 4.0-dev</a></li>
+<li class="toctree-l1"><a class="reference internal" href="README.html">Python Bindings for Raylib 4.0.0</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#quickstart">Quickstart</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#installation">Installation</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#how-to-use">How to use</a></li>
+<li class="toctree-l1"><a class="reference internal" href="README.html#app-showcase">App showcase</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#rlzero">RLZero</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#help-wanted">Help wanted</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#license-updated">License (updated)</a></li>
@@ -51,7 +52,7 @@
 <li class="toctree-l1"><a class="reference internal" href="dynamic.html">Dynamic Bindings</a></li>
 <li class="toctree-l1 current"><a class="current reference internal" href="#">Building from source</a><ul>
 <li class="toctree-l2"><a class="reference internal" href="#have-pip-build-from-source">Have Pip build from source</a></li>
-<li class="toctree-l2"><a class="reference internal" href="#build-from-source-manually">Build from source manually</a><ul>
+<li class="toctree-l2"><a class="reference internal" href="#or-build-from-source-manually">Or, Build from source manually</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#windows-manual-build">Windows manual build</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#linux-manual-build">Linux manual build</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#macos-manual-build">Macos manual build</a></li>
@@ -90,22 +91,32 @@
 <h1>Building from source<a class="headerlink" href="#building-from-source" title="Permalink to this headline"></a></h1>
 <div class="section" id="have-pip-build-from-source">
 <h2>Have Pip build from source<a class="headerlink" href="#have-pip-build-from-source" title="Permalink to this headline"></a></h2>
-<p>Useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.</p>
-<p>Make sure Raylib is installed and then:</p>
+<p>This is useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.</p>
+<p>First make sure Raylib is installed.  On Linux/Mac it must include the pkg-config files.  Best way to ensure this
+is to compile and install Raylib using CMake: <a class="reference external" href="https://github.com/raysan5/raylib/wiki/Working-on-GNU-Linux#build-raylib-using-cmake">https://github.com/raysan5/raylib/wiki/Working-on-GNU-Linux#build-raylib-using-cmake</a></p>
+<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">cd</span> <span class="n">raylib</span><span class="o">-</span><span class="mf">4.0</span><span class="o">.</span><span class="mi">0</span>
+<span class="n">mkdir</span> <span class="n">build</span>
+<span class="n">cd</span> <span class="n">build</span>
+<span class="n">cmake</span>  <span class="o">-</span><span class="n">DWITH_PIC</span><span class="o">=</span><span class="n">on</span> <span class="o">-</span><span class="n">DCMAKE_BUILD_TYPE</span><span class="o">=</span><span class="n">Release</span> <span class="o">..</span>
+<span class="n">make</span>
+<span class="n">sudo</span> <span class="n">make</span> <span class="n">install</span>
+</pre></div>
+</div>
+<p>Then ask Pip to build from source:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip3</span> <span class="n">install</span> <span class="o">--</span><span class="n">no</span><span class="o">-</span><span class="n">binary</span> <span class="n">raylib</span> <span class="o">--</span><span class="n">upgrade</span> <span class="o">--</span><span class="n">force</span><span class="o">-</span><span class="n">reinstall</span> <span class="n">raylib</span>
 </pre></div>
 </div>
 </div>
-<div class="section" id="build-from-source-manually">
-<h2>Build from source manually<a class="headerlink" href="#build-from-source-manually" title="Permalink to this headline"></a></h2>
+<div class="section" id="or-build-from-source-manually">
+<h2>Or, Build from source manually<a class="headerlink" href="#or-build-from-source-manually" title="Permalink to this headline"></a></h2>
 <p>Useful if the Pip build doesn’t work and you want to debug it, or you want to contribute to the
 project.</p>
 <div class="admonition attention">
 <p class="admonition-title">Attention</p>
 <p>If the Pip build doesn’t work, please submit a bug. (And if you have
 fixed it, a PR.)</p>
 </div>
-<p>Manual instructions follow, but see also how we actually build the wheels
+<p>Manual instructions follow, but may be outdated, so see also how we actually build the wheels
 at <a class="reference external" href="https://github.com/electronstudio/raylib-python-cffi/blob/master/.github/workflows/build.yml">https://github.com/electronstudio/raylib-python-cffi/blob/master/.github/workflows/build.yml</a></p>
 <div class="section" id="windows-manual-build">
 <h3>Windows manual build<a class="headerlink" href="#windows-manual-build" title="Permalink to this headline"></a></h3>
@@ -252,6 +263,8 @@ <h3>Macos manual build<a class="headerlink" href="#macos-manual-build" title="Pe
 </div>
 <div class="section" id="raspberry-pi">
 <h3>Raspberry Pi<a class="headerlink" href="#raspberry-pi" title="Permalink to this headline"></a></h3>
+<p>Latest info: <a class="reference external" href="https://github.com/electronstudio/raylib-python-cffi/issues/55#issuecomment-1012629701">https://github.com/electronstudio/raylib-python-cffi/issues/55#issuecomment-1012629701</a></p>
+<p>Old possibly out of date info that was written for RPi3 and Raylib 3 follows.</p>
 <p>The integrated GPU hardware in a Raspberry Pi (“VideoCore”) is rather
 idiosyncratic, resulting in a complex set of software options. Probably
 the most interesting two options for Raylib applications are:</p>

docs/README.html

@@ -3,7 +3,7 @@
 <head>
   <meta charset="utf-8" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Python Bindings for Raylib 4.0-dev &mdash; Raylib Python  documentation</title><link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
+  <title>Python Bindings for Raylib 4.0.0 &mdash; Raylib Python  documentation</title><link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
       <link rel="stylesheet" href="_static/graphviz.css" type="text/css" />
   <!--[if lt IE 9]>
@@ -37,7 +37,7 @@
         </div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
               <p class="caption"><span class="caption-text">Contents:</span></p>
 <ul class="current">
-<li class="toctree-l1 current"><a class="current reference internal" href="#">Python Bindings for Raylib 4.0-dev</a></li>
+<li class="toctree-l1 current"><a class="current reference internal" href="#">Python Bindings for Raylib 4.0.0</a></li>
 <li class="toctree-l1"><a class="reference internal" href="#quickstart">Quickstart</a></li>
 <li class="toctree-l1"><a class="reference internal" href="#installation">Installation</a><ul>
 <li class="toctree-l2"><a class="reference internal" href="#dynamic-binding-version">Dynamic binding version</a></li>
@@ -49,6 +49,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#if-you-prefer-a-slightly-more-pythonistic-api-and-don-t-mind-it-might-be-slightly-slower">If you prefer a slightly more Pythonistic API and don’t mind it might be slightly slower</a></li>
 </ul>
 </li>
+<li class="toctree-l1"><a class="reference internal" href="#app-showcase">App showcase</a></li>
 <li class="toctree-l1"><a class="reference internal" href="#rlzero">RLZero</a></li>
 <li class="toctree-l1"><a class="reference internal" href="#help-wanted">Help wanted</a></li>
 <li class="toctree-l1"><a class="reference internal" href="#license-updated">License (updated)</a></li>
@@ -78,7 +79,7 @@
           <div role="navigation" aria-label="Page navigation">
   <ul class="wy-breadcrumbs">
       <li><a href="index.html" class="icon icon-home"></a> &raquo;</li>
-      <li>Python Bindings for Raylib 4.0-dev</li>
+      <li>Python Bindings for Raylib 4.0.0</li>
       <li class="wy-breadcrumbs-aside">
             <a href="_sources/README.md.txt" rel="nofollow"> View page source</a>
       </li>
@@ -88,8 +89,8 @@
           <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
            <div itemprop="articleBody">
 
-  <div class="tex2jax_ignore mathjax_ignore section" id="python-bindings-for-raylib-4-0-dev">
-<h1>Python Bindings for Raylib 4.0-dev<a class="headerlink" href="#python-bindings-for-raylib-4-0-dev" title="Permalink to this headline"></a></h1>
+  <div class="tex2jax_ignore mathjax_ignore section" id="python-bindings-for-raylib-4-0-0">
+<h1>Python Bindings for Raylib 4.0.0<a class="headerlink" href="#python-bindings-for-raylib-4-0-0" title="Permalink to this headline"></a></h1>
 <p>New CFFI API static bindings.</p>
 <ul class="simple">
 <li><p>Automatically generated to be as close as possible to
@@ -139,7 +140,7 @@ <h2>Dynamic binding version<a class="headerlink" href="#dynamic-binding-version"
 </div>
 <div class="section" id="beta-testing">
 <h2>Beta testing<a class="headerlink" href="#beta-testing" title="Permalink to this headline"></a></h2>
-<p>You can install an alpha or beta version by specifying the version number like this:</p>
+<p>You can install an alpha or beta version by specifying the exact version number like this:</p>
 <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>python3 -m pip install raylib==4.0a6
 </pre></div>
 </div>
@@ -157,6 +158,11 @@ <h2>If you prefer a slightly more Pythonistic API and don’t mind it might be s
 <p>Use <a class="reference external" href="https://electronstudio.github.io/raylib-python-cffi/pyray.html">the Python API</a>.</p>
 </div>
 </div>
+<div class="tex2jax_ignore mathjax_ignore section" id="app-showcase">
+<h1>App showcase<a class="headerlink" href="#app-showcase" title="Permalink to this headline"></a></h1>
+<p><a class="reference external" href="https://github.com/pkulev/tanki">Tanki</a></p>
+<p>Add your app here!</p>
+</div>
 <div class="tex2jax_ignore mathjax_ignore section" id="rlzero">
 <h1>RLZero<a class="headerlink" href="#rlzero" title="Permalink to this headline"></a></h1>
 <p>A related library (that is a work in progress!):</p>

docs/_sources/BUILDING.rst.txt

@@ -4,16 +4,30 @@ Building from source
 Have Pip build from source
 --------------------------
 
-Useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.
+This is useful if the binaries don’t work on your system, or you want to use a newer version of Raylib.
 
-Make sure Raylib is installed and then:
+First make sure Raylib is installed.  On Linux/Mac it must include the pkg-config files.  Best way to ensure this
+is to compile and install Raylib using CMake: https://github.com/raysan5/raylib/wiki/Working-on-GNU-Linux#build-raylib-using-cmake
+
+::
+
+      cd raylib-4.0.0
+      mkdir build
+      cd build
+      cmake  -DWITH_PIC=on -DCMAKE_BUILD_TYPE=Release ..
+      make
+      sudo make install
+
+
+
+Then ask Pip to build from source:
 
 ::
 
    pip3 install --no-binary raylib --upgrade --force-reinstall raylib
 
-Build from source manually
---------------------------
+Or, Build from source manually
+------------------------------
 
 Useful if the Pip build doesn’t work and you want to debug it, or you want to contribute to the
 project.
@@ -22,7 +36,7 @@ project.
    If the Pip build doesn’t work, please submit a bug. (And if you have
    fixed it, a PR.)
 
-Manual instructions follow, but see also how we actually build the wheels
+Manual instructions follow, but may be outdated, so see also how we actually build the wheels
 at https://github.com/electronstudio/raylib-python-cffi/blob/master/.github/workflows/build.yml
 
 Windows manual build
@@ -207,6 +221,10 @@ Build and install module.
 Raspberry Pi
 ~~~~~~~~~~~~
 
+Latest info: https://github.com/electronstudio/raylib-python-cffi/issues/55#issuecomment-1012629701
+
+Old possibly out of date info that was written for RPi3 and Raylib 3 follows.
+
 The integrated GPU hardware in a Raspberry Pi (“VideoCore”) is rather
 idiosyncratic, resulting in a complex set of software options. Probably
 the most interesting two options for Raylib applications are:

docs/_sources/README.md.txt

@@ -1,4 +1,4 @@
-# Python Bindings for Raylib 4.0-dev
+# Python Bindings for Raylib 4.0.0
 
 New CFFI API static bindings.
 * Automatically generated to be as close as possible to 
@@ -51,7 +51,7 @@ There is now a separate dynamic version of this binding:
 
 ## Beta testing
 
-You can install an alpha or beta version by specifying the version number like this:
+You can install an alpha or beta version by specifying the exact version number like this:
 
     python3 -m pip install raylib==4.0a6
 
@@ -68,8 +68,11 @@ Use [the C API](https://electronstudio.github.io/raylib-python-cffi/raylib.html)
 
 Use [the Python API](https://electronstudio.github.io/raylib-python-cffi/pyray.html).
 
+# App showcase
 
+[Tanki](https://github.com/pkulev/tanki)
 
+Add your app here!
 
 # RLZero
 

docs/dynamic.html

@@ -37,10 +37,11 @@
         </div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
               <p class="caption"><span class="caption-text">Contents:</span></p>
 <ul class="current">
-<li class="toctree-l1"><a class="reference internal" href="README.html">Python Bindings for Raylib 4.0-dev</a></li>
+<li class="toctree-l1"><a class="reference internal" href="README.html">Python Bindings for Raylib 4.0.0</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#quickstart">Quickstart</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#installation">Installation</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#how-to-use">How to use</a></li>
+<li class="toctree-l1"><a class="reference internal" href="README.html#app-showcase">App showcase</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#rlzero">RLZero</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#help-wanted">Help wanted</a></li>
 <li class="toctree-l1"><a class="reference internal" href="README.html#license-updated">License (updated)</a></li>