SFML/examples/sockets/CMakeLists.txt

# all source files
set(SRC Sockets.cpp
        TCP.cpp
        UDP.cpp)

# define the sockets target
sfml_add_example(sockets
                 SOURCES ${SRC}
                 DEPENDS SFML::Network)
Source code changes. * Changed newlines to \n. * Removed whitespace before colons. * Fixed several alignments. 2014-09-30 22:07:25 +08:00			`# all source files`
Simplify how examples are built CMake doesn't require absolute paths so we can safely remove SRCROOT and let implicit relative pathing achieve the same result with less work on our part. 2022-06-13 00:48:48 +08:00			`set(SRC Sockets.cpp`
			`TCP.cpp`
			`UDP.cpp)`
Source code changes. * Changed newlines to \n. * Removed whitespace before colons. * Fixed several alignments. 2014-09-30 22:07:25 +08:00
			`# define the sockets target`
			`sfml_add_example(sockets`
			`SOURCES ${SRC}`
Add SFML:: namespace to targets This removes the sfml- prefixed targets from the export set. The sfml- prefixed targets are still available within the build tree but not to downstream users thus making this an API breaking change when compared to the 2.x releases. To keep things consistent, usage of the sfml- targets were replaced with their namespaced counterparts. This has a number of benefits: 1. It's more idiomatic. Modern CMake libraries are expected to have namespaced targets. 2. Namespaced targets are less likely to collide with user-defined targets. No one will accidentally define a SFML:: target. 3. If a namespaced target is not found by CMake, configuration will immediately stop. 2021-12-29 13:28:50 +08:00			`DEPENDS SFML::Network)`