-
Notifications
You must be signed in to change notification settings - Fork 44
Update xcode tutorial to demonstrate project setup without templates #270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
b9fe3ef to
13ef12d
Compare
| You can find more details in [this document](https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/DynamicLibraries/ "Go to Apple's documentation about dylib"). | ||
| - Frameworks are fundamentally the same as dylibs, except that they can encapsulate external resources. | ||
| Here is [the in-depth documentation](https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPFrameworks/Frameworks.html "Go to Apple's documentation about framework"). | ||
| Then, in order to start developing SFML applications, you have to install the following items: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which following items?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, seems like a leftover line from before
eXpl0it3r
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be great to add periods at the end of the sentences / paragraphs.
| - **Xcode templates** | ||
| This feature is optional but we strongly recommend that you install it. | ||
| Copy the SFML directory from templates to `~/Library/Developer/Xcode/Templates` (create the folders if they don't exist yet). | ||
| Now you have a basic project with a `main.cpp` file for your code. You can replace the contents with this SFML code to draw a green circle: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each sentence should be on its own line, for better diffs
| But currently it will not build, as we need to configure Xcode so it can find SFML's headers and libraries | ||
|
|
||
|  | ||
| For header paths, select your project on the sidebar, go to the build settings tab and set the Header Search paths (filter can help find the setting) to the `include` folder in your unpacked SFML folder (or brew include folder if using brew, e.g. `/opt/homebrew/include`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| For header paths, select your project on the sidebar, go to the build settings tab and set the Header Search paths (filter can help find the setting) to the `include` folder in your unpacked SFML folder (or brew include folder if using brew, e.g. `/opt/homebrew/include`) | |
| For header paths, select your project on the sidebar, go to the build settings tab and set the Header Search paths (filter can help find the setting) to the `include` folder in your unpacked SFML folder, e.g. `<sfml-install-path>/include` (or brew include folder if using brew, e.g. `/opt/homebrew/include`) |
|
|
||
|  | ||
|
|
||
| For library paths, do the same for the Library Search path setting, using the `lib` folder in your unpacked SFML folder (or brew lib folder if using brew, e.g. `/opt/homebrew/lib`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| For library paths, do the same for the Library Search path setting, using the `lib` folder in your unpacked SFML folder (or brew lib folder if using brew, e.g. `/opt/homebrew/lib`) | |
| For library paths, do the same for the Library Search path setting, using the `lib` folder in your unpacked SFML folder, .e.g `<sfml-install-path>/lib` (or brew lib folder if using brew, e.g. `/opt/homebrew/lib`) |
With imminent removal of our xcode templates (SFML/SFML#3622) the tutorials need updating (frankly they needed it anyway as they are very old)
This replaces the template tutorial with the manual project setup for both static and dynamic linking
Framework setup is omitted as I found some issues when testing them (I never use them normally) so want to try and work them out first, and there's possibly even an argument that we shouldn't bother shipping frameworks at all, for a separate discussion