Updating to explain how to get setup with VSCode as per recent additions to that project format

master
Murray Campbell 6 years ago
parent
commit
6e0c10fdf3
1 changed files with 3 additions and 0 deletions
  1. +3
    -0
      Working-on-macOS.md

+ 3
- 0
Working-on-macOS.md

@ -92,6 +92,9 @@ otool -L my_app
This shows you everything your application links to. Basically, if anything is pointing to anything but /usr/lib/* or /System/Library/*, your application will throw an error if you run it on any other Mac. It's not portable.
For example if it's linking to something in /usr/local/lib, or a relative folder, that would be bad. But after the above, you should be clear of dynamic dependencies!
## Using VSCode
Copy the files from raylib/projects/VSCODE to a folder. Make sure you set the proper paths to your static build of raylib in c_cpp_properties.json and tasks.json (look for fields named <path_to_raylib>). This will be specific to your installation of raylib. Once that's done, set the default build task to the OSX debug and launch using the OSX debug configuration.
# Bundle your app in an Application

Loading…
Cancel
Save