nfoTools
VCrayApp FAILCODE7: RAYLIB VERSION NOT > 3.0.0
| nfoTools | dev>D211101>f>FAIL7 | index.html 0.0.6 2023-07-14 |
|---|---|---|
 |
Work-in-Progress |  |
| This Version | since VCrayApp 0.1.0 | D211101e |
VCrayApp is not workable with raylib-3.0.0 and older releases. There is no effort to support such older releases. Releases in the 4.x series other than 4.2 are now preferred. The verbose output demonstrates detection and rejection after installation of raylib-3.0.0.
Background
Starting with raylib-4.0.0, the file src\raylib.h provides a version
preprocessor variable.
The small program VCrayVerCheck.c is compiled on the first run of VCrayApp
and on every cache refresh. It checks raylib.h for that preprocessor
variable and its value. If the value is not defined, VCrayVerCheck reports
that the version is unidentified. VCrayApp.bat acquires the result from
execution of VCrayVerCheck.exe.
In the unidentified (pre-raylib-4.0) case,
VCrayApp.bat inspects for the presence and absence of some raylib\ files
that differ among pre-4.0 raylib releases. That is how versions 3.5 and 3.7
are identified and accepted for cache construction. All other unidentified
cases lead to FAILCODE7.
For identified versions, VCrayApp.bat will present FAILCODE8 for
specific versions of raylib that are known to be unusable with Visual Studio
Build Tools. Otherwise, compiling of the cache of raylib components will
proceed.
Discussion about nfoTools is welcome at the Discussion section. Improvements and removal of defects in this particular documentation can be reported and addressed in the Issues section. There are also relevant projects from time to time.