nfoTools

D211101f VCrayApp FAILCODE MESSAGES

nfoTools dev>D211101>f index.html 0.0.9 2023-07-14
nfotools Work-in-Progress Hard Hat Area
     
This Version as of VCrayApp 0.1.0 beta release D211101e

This material is provided to supplement VCrayApp FAILCODEn messages from VCrayApp.bat starting with VCrayApp-0.1.0. When a subsequent version of VCrayApp has significant changes for one of these, a new FAILCODE will be introduced.

These explanations are intended to support trouble-shooting and failures in performance of VCrayApp.bat in a VCrayApp-based project.

Feedback and requests concerning this material should be addressed to the nfoTools GitHub Project with mention of D211101 and the particular FAILCODE. Feedback on actual experience and the utility of these explanations is valued.

Review discussions, issues, and projects for discussions and comments related to specific VCrayApp releases and their application.

FAILCODE CATALOG

LABEL FAILCODE
:FAIL0 FAILCODE0: COMMAND SHELL EXTENSIONS REQUIRED
:FAIL1 FAILCODE1: INCORRECT VCrayApp FILES CONFIGURATION
:FAIL2 FAILCODE2: UNSUPPORTED VCRAYAPP.BAT PARAMETERS
:FAIL3 FAILCODE3: NO VS NATIVE COMMAND-LINE ENVIRONMENT
:FAIL4 FAILCODE4: COMPILING CACHE OF RAYLIB FILES FAILED
:FAIL5 FAILCODE5: PRODUCING/OPERATING %VCEXE% FAILED
:FAIL6 FAILCODE6: RAYLIB NOT FOUND WHERE EXPECTED
:FAIL7 FAILCODE7: RAYLIB VERSION NOT > 3.0.0
:FAIL8 FAILCODE8: RAYLIB %VCRAYVER% NOT SUPPORTED

The labels are where the message is produced in VCrayApp.bat code. All the references to them can be found by searching the VCrayApp.bat file.

THE DEMONSTRATION SETUP

VCrayDemo Folder

For demonstration purposes, the folder VCrayDemo is setup with two subfolders, VCrayDemo\raylib\, the installed raylib source-code release, and VCrayDemo\demo\, the VCrayApp setup for the project. The additional files are downloaded zip packages for handy reuse. The two files for checking the integrity of the VCrayApp-semver.zip are also kept handy.

VCrayDemo Project

Folder VCrayDemo\demo\ is simply the standard VCrayApp structure with one addition. A [custom shortcut is created for initiating a VS Developer Command Prompt directly at VCrayDemo\demo. The demonstrations are initiated by double-clicking directly on that shortcut in the Windows File Explorer. For example, it simplifies checking VCrayApp usage.

VCrayDemo Usage

For comparison with usage of the Command Prompt directly, see the examples for FAILCODE3.


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.