CMake: Implement WITH_AUTO_UPDATER

[TheOneRing]

Fixes: #9082

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[dragotin]

This needs to be documented in the client docs, there is a paragraph about building the client. @mmattel

Are there, apart from this switch, ohters that should be documented there?

[TheOneRing]

They are already kind of documented in code.

client/CMakeLists.txt

Lines 80 to 105 in 3ae537b

	# this option removes Http authentication, keychain, shibboleth etc and is intended for
	# external authentication mechanisms
	option(TOKEN_AUTH_ONLY "TOKEN_AUTH_ONLY" OFF)
	option(NO_MSG_HANDLER "Don't redirect QDebug outputs to the log window/file" OFF)
	# this option builds the shell integration
	option(BUILD_SHELL_INTEGRATION "BUILD_SHELL_INTEGRATION" ON)
	# this option builds/installs the generic shell integration icons
	option(BUILD_SHELL_INTEGRATION_ICONS "BUILD_SHELL_INTEGRATION_ICONS" ON)
	# this options builds the dolphin integration plugin
	option(BUILD_SHELL_INTEGRATION_DOLPHIN "BUILD_SHELL_INTEGRATION_DOLPHIN" ON)
	# this options builds the nautilus (like) integration plugins
	option(BUILD_SHELL_INTEGRATION_NAUTILUS "BUILD_SHELL_INTEGRATION_NAUTILUS" ON)
	# this option builds the client
	option(BUILD_CLIENT "BUILD_CLIENT" ON)
	# this option creates only libocsync and libowncloudsync (NOTE: BUILD_CLIENT needs to be on)
	option(BUILD_LIBRARIES_ONLY "BUILD_LIBRARIES_ONLY" OFF)
	# build the GUI component, when disabled only owncloudcmd is built
	option(BUILD_GUI "BUILD_GUI" ON)

[TheOneRing]

TOKEN_AUTH_ONLY is no longer supported and will be removed one day

[dragotin]

They are already kind of documented in code.

yes, and with a cmake-guru-level above 8 people will find that ;-)

[TheOneRing]

Those settings are available in the cmake gui and in most IDE's

[dragotin]

Yes, I know. Sorry if I am stubborn: A good "How to build" documentation should mention the most important ones anyway, because packagers (that you want to help ;-) do not starts UIs for every program they are packaging.

WHAT the heck is the problem to add that to documentation? At least a hint?

[TheOneRing]

I don't really have a problem with it, its just an other part of the documentation that can be outdated quite fast