-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 VCrayApp-0.1.0.txt 0.0.11 UTF-8 2023-05-08 *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* NFOTOOLS DEVKIT FOR RAYLIB APPS =============================== BUILDING RAYLIB APPS WITH VS DEVELOPER COMMAND PROMPT ----------------------------------------------------- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * SPECIAL NOTICE * * ************** * * * * If this VCrayApp-0.1.0.txt appears in a VCrayApp folder within a * * different application project's folder/respository, ignore this * * account and follow instructions provided for the project that * * contains VCrayApp as a component. The embedded VCrayApp should * * be maintained only with the containing application. * * * * WARNING * * * * There are breaking changes between VCrayApp-0.1.0 and the earlier * * VCrayApp-0.0.0 (alpha). See the accompanying CHANGES-0.1.0.txt. * * * * CAUTION * * ******* * * * * This is a beta release of VCrayApp. The release is intended * * as a preview of the stable release to follow once there has been * * a period of testing and review with feedback from trial use. * * * * There could still be breaking changes, possibly to adjust for * * changes in raylib and other tools that occur in the interim. * * * * Be cautious. Be careful. It is recommended that VCrayApp be * * used solely with official stable releases of raylib and other * * tools. Use of development versions of raylib\ and other tools * * is recommended only for those interested in working on and *. * * contributing to raylib itself. * * * * IMPORTANT * * ********* * * * * It is recommended that VS 2022 Version 17.5 or later (including * * Build Tools) be employed with VCrayApp. There are improvements * * in C Language 2011 support that are expected in some examples * * and other usage of raylib. * * * * No VCrayApp support is provided for development using anything * * but the C language and the Microsoft VC C/C++ compiler and * * related developer tools on a Windows desktop PC, laptop or * * Microsoft Surface. * * * * VCRAYAPP 0.1.0 IS BEING TESTED WITH THE RAYLIB 4.5.0 SOURCE * * CODE. RAYLIB 4.2.0 CANNOT BE USED BECAUSE OF A VC/C++ * * INCOMPATIBILITY. VCRAYAPP 0.1.0 CAN ALSO BE USED WITH 4.0.0, * * 3.7.0, AND 3.5.0. CONFIRMATION WITH LATER RAYLIB RELEASES IS * * FUTURE WORK. * * * * Ramon Santamaria's raylib software is written in a clean-form of * * the C Language (C99 standard). Use of the raylib code, include * * files, and the API interfaces requires confidence in the use of * * the C or C++ languages with such libraries. VCrayApp is meant * * to be used directly only for programs written in the C Language. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * The VCrayApp-0.1.0 distribution is available on the web at . Consult that page for the latest status, links to useful related material, and any more-recent version. If there is concern for the authenticity or correctness of any VCrayApp distribution, obtain a full replacement via . VCrayApp is designed to work with versions of Visual Studio that are free for personal/open-source use, including the Visual Studio Build Tools (recommended) and the Visual Studio Community editions. Additional levels of licensed Visual Studio can also be used, all via their Native Tools Command Prompt. PREREQUISITES AND DEPENDENCIES Development with VCrayApp and illustration of usage involves the following tools along with confident use of C Language: * Windows File Explorer * Windows Built-in Zip-Folder Tool * Visual Studio Native Build Tools * Developer Command Prompt * Microsoft VC/C++ Command Line Compiler, CL.exe * raylib *source* code *release* later than 3.0.0 downloaded and unzipped * A text-editor for work on source code, other files, all in plain text (Visual Studio Code recommended for its C/C++ and Microsoft support) + Git4Win implementation for source-code control + TortoiseGit for File Explorer integration of Git + GitHub Windows Client for public access to development projects + GPG4Win for creation and verification of digital signatures The first seven are essential. The remainder are recommended; those are not required for starting up. There are alternatives. The specific ones happen to be those relied upon in the development of nfoTools projects. For more information on dependencies, see . NOTE: VCrayApp does not work with raylib 4.2. Releases 4.0 and 4.5 are successful. For versions later than 4.5, check at . DOWNLOADS AND SETUP It is recommended that you have already installed Visual Studio Native Build Tools and confirmed that the Developer Command Prompt is operating properly. See . If you have not already done so, choose where on your computer you want to have the raylib source code and your own adjacent projects. See and also the setup arrangement described at and . raylib\ must be setup before VCrayApp can be used. Download VCrayApp from . If a later version is available, consider using that version instead. It is useful to download VCrayApp-0.1.0.zip to a location that you can use as a source of copies for one or more VCrayApp projects. EXTRACTION AND RENAMING OF VCrayApp-0.1.0.zip CONTENT After downloading VCrayApp-0.1.0.zip to a place where you want to keep it, make a copy to a place where you want to use it. Right click on File Explorer VCrayApp-0.1.0.zip and click "Extract all ..." in the context menu that appears. In the "Extract Compressed (Zipped) Folders" Dialog that appears, accept the "Files will be extracted to this folder:" choice that is offered automatically. Check the "Show extracted files when complete" entry. Click "Extract". There should now be a VCrayApp-0.1.0\ sub-folder in the same folder as the Zip file you extracted it from. Rename that sub-folder to the name you want for this VCrayApp project of yours. This is the new project folder. CONFIRMING THE VCrayApp SETUP AND OPERATION Using a Visual Studio Developer Command Prompt, navigate to your project folder and use the command VCrayApp ? To confirm that the project folder is setup properly and that VCrayApp.bat is operating. If that succeeds, use the command VCrayApp This will compile some raylib components to the cache\ folder along with some setup checks and the program VCrayConfirm.exe. That program will run, confirming usability of the setup and the cache. If there are any failure messages, correct for them until this VCrayApp succeeds. See for additional information. You can now use the src\ folder of the new project for source code. It will be compiled when you provide the name of your executable as a parameter to VCrayApp. MANIFEST OF VCrayApp-0.1.0.zip VCrayApp-0.1.0.txt 0.0.11 14,152 byte 2023-05-08T20:49 armor-signed version. This description file on organization of the archive and use of its materials. NOTICE.txt 1.0.5 2,671 byte 2023-05-05T17:43 armor-signed version NOTICE applicable to VCrayApp-0.1.0.zip and its content CHANGES-0.1.0.txt 0.0.16 8,412 byte 2023-05-07T18:56 armor-signed version identifying changes made from VCrayApp-0.0.0. VCrayApp.bat 0.0.18 10,901 byte 2022-12-31T20:30Z version Script that, when run, will confirm VC/C++ command-prompt settings, performing compilations of a raylib cache\ as well as project source codes to deliver a compiled result in app\. .vscode\ provided for use of Visual Studio Code with .vscode.txt a .txt project synopsis and manifest for c_cpp_properties.json the .vscode folder app\ .gitignore used to suppress compiled binaries from source control app.txt synopsis and manifest for the app\ folder cache\ .gitignore used to suppress intermediate files from source control cache.txt synopsis and manifest for the cache\ folder. There are several "helper" files there for use of VCrayApp as part of its operation src\ src.txt synopsis and manifest for the src\ folder this is the recommended place for adding code for a standalone raylib project. More-advanced cases are described on the VCrayApp web pages. The supplied text files provide further descriptions and explanations for usage and customization of app\, cache\ and src\. *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* Copyright 2021-2023 Dennis E. Hamilton Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* ATTRIBUTION Hamilton, Dennis E. Building raylib Apps with VS Developer Command Prompt. nfoTools file VCrayApp-0.1.0.txt version 0.0.11 dated 2023-05-08 available on the internet as a version of *---|----1----|----2----|----3----|----4----|----5----|----6----|----7----|--* 0.0.11 2023-05-08T19:47Z Touch-ups to make release candidate 0.0.10 2023-05-04T17:14Z Touch-ups to align with changes to VCrayApp API 0.0.9 2023-02-22T23:40Z Final draft for VCrayApp-0.1.0 0.0.8 2023-02-09T23:37Z Rough-draft retargeting for VcrayApp-0.1.0. 0.0.7 2023-01-07T20:44Z Clearsigned version 0.0.6 2023-01-02T22:36Z Updating manifested time stamps 0.0.5 2022-12-31T20:12Z Review and Touch-ups 0.0.4 2022-10-26T17:34Z Near-final draft before signing 0.0.3 2022-08-24T17:28Z Provisional draft for Alpha release 0.0.2 2022-07-13T17:24Z Draft Editing of Expanded Boilerplate. 0.0.1 2022-06-07T22:27Z Include boilerplate from VCbind-0.1.0 0.0.0 2021-10-09T00:46Z Placeholder draft ***** end of VCrayApp-0.1.0.txt ***** -----BEGIN PGP SIGNATURE----- iQFGBAEBCAAwFiEEBNBDIpebhN4QdwM0+W6J/9RWYooFAmRZUyoSHG9yY21pZEBh cGFjaGUub3JnAAoJEPluif/UVmKK8MIH/jNUyOiuiaXRoxFkkDcxUUfOI1FtRzut VZDwuweKtAodN+FsKWvJTFErUES4ncnyFDrerb/tTtmkuAqrdxe3ufkeh8UYeH6c 0dOFqouBDoTEcpA6Tl7jpbnpunnqsoTQL3UXIRXcieL7/CPJUGhBaNYj31kMPFdc t6Ppen006Uk6lBKpOOh4/kr0e1lIqrA1pxNfXiR4Ocw+wOKT+MyDw17BdPUGoQBS itKbO2gqyDo0udJH5xnAjhxV6cC9pvlIcd2KG6AzxKkW9eOIM1jBJA/NkNfWYhwr YcvZGB/R3N05i89iR4wU8TvD+0gMJsNjLI9MojI9mleTJtpdtQbqHH0= =2n9j -----END PGP SIGNATURE-----