How we test the install process for gintro

[StefanSalewski]

As no one has asked for it in the last 8 years, here is a short description how we test the bindings generation. A plain "nimble install gintro@#head" works not very good for displaying a useful issue description, so we create a separate directory for manually testing. Creating this directory is basically executing the script

#cat ~/gintro/prepairtest.sh 
cd
#git clone https://github.com/stefansalewski/gintro.git
mkdir gintrotest
mkdir gintrotest/test
cd gintrotest/test
mkdir nim_gi
cp ~/gintro/tests/* .
wget https://raw.githubusercontent.com/StefanSalewski/oldgtk3/master/oldgtk3/gobject.nim -O gobject.nim
wget https://raw.githubusercontent.com/StefanSalewski/oldgtk3/master/oldgtk3/glib.nim -O glib.nim
wget https://raw.githubusercontent.com/StefanSalewski/oldgtk3/master/oldgtk3/gir.nim -O gir.nim

# nim c gen.nim
# ./gen # gtk3 -- for latest version, we have to generate gtk3 files first!
# ./gen 1 # gtk4 

We need the 3 files from oldgtk3 for bootstrapping, and a local directory nim_gi, where the binding modules are stored. We compile the gen.nim generator script, and execute it with "./gen" to generate the GTK3 bindings first, then with "./gen 1" to generate the GTK4 bindings. Order is important for latest gintro version, as the GTK3 generation process now tests for libsoup/libnice interaction, and stores the test result in a local file.