Rhett

Here is the very first game on the engine. An implementation of a game on the engine is called a module. Hence this is module Paths_of_Glory.BETA.ver.0.1 on GameTop. The module comes complete with images. I am very greateful for using the images taken from the VASSAL module Paths of Glory found here. All tribute to the makers of that module. A few changes has been made to the images in the VASSAL module. All SVG files have been replaced by PNG files. That was necessary because the rendering of the...

Here is the very first game on the engine. An implementation of a game on the engine is called a module. Hence this is module Paths_of_Glory.BETA.ver.0.1 on GameTop. The module comes complete with images. I am very greateful for using the images taken from the VASSAL module Paths of Glory found here. All tribute to the makers of that module. A few changes has been made to the images in the VASSAL module. All SVG files have been replaced by PNG files. That was necessary because the rendering of the...

Here is the very first game on the engine. An implementation of a game on the engine is called a module. Hence this is module Paths_of_Glory.BETA.ver.0.1 on GameTop. The module comes complete with images. I am very greateful for using the images taken from the VASSAL module Paths of Glory found here. All tribute to the makers of that module. A few changes has been made to the images in the VASSAL module. All SVG files have been replaced by PNG files. That was necessary because the rendering of the...

Making the Windows deployment was more difficult. A poor understanding of cross-compiling and cmake did not make it easier. This is the downside of development. One would rather use time on one's own code. First of all, it may be obvious, but you make libraries and executables from the Linux version of Qt. There is actually no difference between the Linux and Windows source code. The Windows version of Qt is only needed if you want to use the precompiled Windows libraries (and of course compile on...

A deployment is setting up the necessary files to run a game on a host. The files are (as of now): -- The eight Luau script files. -- The _ _images, images and setups folders. -- The lib folder holding the Qt libraries. -- The plugins folder for image formats (libqjpeg.so) and platforms (libqxcb.so) used by Qt. -- The engine executable main. Note: The Luau libraries are not needed at run-time, only when making main. The engine can not be downloaded separately from the module. The engine is always...

A deployment is setting up the necessary files to run a game on a host. The files are (as of now): -- The four Luau static libraries. -- The eight Luau script files. -- The _ _images, images and setups folders. -- The lib folder holding the Qt libraries. -- The plugins folder for image formats (libqjpeg.so) and platforms (libqxcb.so) used by Qt. -- The engine executable main. The engine can not be downloaded separately from the module. The engine is always downloaded as an implementation of a specific...

A deployment is making the necessary files to run a game on a host. The files are (as of now): -- The four Luau static libraries. -- The eight Luau script files. -- The __images, images and setups folders. -- The lib folder holding the Qt libraries. -- The plugins folder for image formats and platforms used by Qt. -- The engine executable ./main. The engine can not be downloaded separately from a module. It is always downloaded as an implementation of a specific game (in this case Paths of Glory)....

A deployment is making the necessary files to run a game on a host. The files are (as of now): The four Luau static libraries. The eight Luau script files. The __images, images and setups folders. The lib folder holding the Qt libraries. The plugins folder for image formats and platforms used by Qt. The engine executable ./main. The engine can not be downloaded separately from a module. It is always downloaded as an implementation of a specific game (in this case Paths of Glory). Likewise, the Qt...