Skip to content
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

Added four new CMake options #933

Closed
wants to merge 1 commit into from
Closed

Added four new CMake options #933

wants to merge 1 commit into from

Conversation

jagoly
Copy link

@jagoly jagoly commented Jul 28, 2015

SFML_BUILD_WINDOW, SFML_BUILD_NETWORK, SFML_BUILD_GRAPHICS, SFML_BUILD_AUDIO
These all default to TRUE. When set to FALSE, the specified module will not be built. This can be useful if you are, for example, using only the Window module, and don't wish to install the dependencies of Graphics or Audio, just to build SFML.

SFML_BUILD_WINDOW, SFML_BUILD_NETWORK, SFML_BUILD_GRAPHICS, SFML_BUILD_AUDIO
These all default to TRUE. When set to FALSE, the specified module will not be built. This can be useful if you are, for example, using only the Window module, and don't wish to install the dependencies of Graphics or Audio, just to build SFML.
@LaurentGomila
Copy link
Member

#800 ...

@Bromeon
Copy link
Member

Bromeon commented Jul 28, 2015

Why is nobody reading the contribution guidelines? 😞

Please don't just open a pull request when you feel like it, but discuss the issue first on the forum and check if nobody has suggested it yet. This simplifies things for everybody, as we don't have to discuss the same thing in different places, multiple times.

It is okay to have multiple pull requests for one issue, but you have to refer to an existing one and argue what is fundamentally different in your implementation. Ideally, you first participate in the existing discussion and give feedback there.

Do you basically agree with #800 (and for minor differences, give feedback)? If so, we can close this one.

@jagoly
Copy link
Author

jagoly commented Jul 29, 2015

Yes, sorry. I briefly spoke to Tank about it on IRC, but he didn't remember the other one at the time, so I made this one. I'll close this one, since the other one already has had some discussion. Sorry!

@jagoly jagoly closed this Jul 29, 2015
@TankOs
Copy link
Member

TankOs commented Jul 29, 2015

Sorry from my side as well. One thing, though: jagoly created the patch for himself mainly, and sent it in because others might benefit from it as well (classic FOSS principle). This is not a feature request that requires a preceeding discussion, it's more like a gift that we can take or not.

The contribution guidelines help to not waste time building something and getting frustrated when we reject a PR. In this case I'm not so concerned about it, and the only good intervention I can see is by telling about the guidelines section which tells you to look for similar PRs first. ;)

Anyway, thanks for the contribution jagoly, and sorry again. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants