Replace Pipewire with PipeWire for consistency

And set up a CI job to check for that.

.gitlab-ci.yml

@@ -260,6 +260,14 @@ shellcheck:
   script:
     - shellcheck $(git grep -l "#\!/.*bin/.*sh")
 
+spellcheck:
+  extends:
+    - .build_on_fedora
+  stage: analysis
+  script:
+    - git ls-files | grep -v .gitlab-ci.yml | xargs -d '\n' sed -i 's/Pipewire/PipeWire/g'
+    - git diff --exit-code || (echo "Please fix the above spelling mistakes" && exit 1)
+
 pages:
   extends:
     - .not_coverity

INSTALL.md

@@ -1,6 +1,6 @@
 ## Building
 
-Pipewire uses a build tool called *Meson* as a basis for its build
+PipeWire uses a build tool called *Meson* as a basis for its build
 process.  It's a tool with some resemblance to Autotools and CMake. Meson
 again generates build files for a lower level build tool called *Ninja*,
 working in about the same level of abstraction as more familiar GNU Make
@@ -33,7 +33,7 @@ Define the installation prefix:
 $ meson configure builddir -Dprefix=/usr # Default: /usr/local
 ```
 
-Pipewire specific build options are listed in the "Project options"
+PipeWire specific build options are listed in the "Project options"
 section. They are defined in `meson_options.txt`.
 
 Finally, invoke the build:

autogen.sh

@@ -7,7 +7,7 @@ if [ -z "$MESON" ]; then
 fi
 if [ -z "$MESON" ]; then
 	echo "error: Meson not found."
-	echo "Install meson to configure and build Pipewire. If meson" \
+	echo "Install meson to configure and build PipeWire. If meson" \
 	     "is already installed, set the environment variable MESON" \
 	     "to the binary's path."
 	exit 1;

spa/plugins/bluez5/bluez5-dbus.c

@@ -3039,7 +3039,7 @@ static int adapter_register_endpoints(struct spa_bt_adapter *a)
 
 	if (!a->endpoints_registered) {
 		/* Should never happen as SBC support is always enabled */
-		spa_log_error(monitor->log, "Broken Pipewire build - unable to locate SBC codec");
+		spa_log_error(monitor->log, "Broken PipeWire build - unable to locate SBC codec");
 		err = -ENOSYS;
 	}
 

src/modules/module-protocol-pulse/pulse-server.c

@@ -3220,7 +3220,7 @@ static int64_t get_port_latency_offset(struct client *client, struct pw_manager_
 	size_t j;
 
 	/*
-	 * The latency offset is a property of nodes in Pipewire, so we look it up on the
+	 * The latency offset is a property of nodes in PipeWire, so we look it up on the
 	 * nodes. We'll return the latency offset of the first node in the port.
 	 *
 	 * This is also because we need to be consistent with

src/pipewire/client.h

@@ -35,7 +35,7 @@ extern "C" {
 #include <pipewire/proxy.h>
 #include <pipewire/permission.h>
 
-/** \defgroup pw_client Pipewire Client
+/** \defgroup pw_client PipeWire Client
  *
  */
 

src/pipewire/context.h

@@ -47,7 +47,7 @@ extern "C" {
  *
  */
 
-/** \defgroup pw_context Pipewire Context
+/** \defgroup pw_context PipeWire Context
  *
  * \brief The PipeWire context object manages all locally available
  * resources. It is used by both clients and servers.

src/pipewire/filter.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_filter Pipewire Filter
+/** \defgroup pw_filter PipeWire Filter
  *
  * \brief PipeWire filter object class
  *

src/pipewire/impl-core.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_impl_core Pipewire Core Interface
+/** \defgroup pw_impl_core PipeWire Core Interface
  *
  * \brief PipeWire core interface.
  *

src/pipewire/impl-device.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_impl_device Pipewire Device Interface
+/** \defgroup pw_impl_device PipeWire Device Interface
  *
  * The device is an object that manages nodes. It typically
  * corresponds to a physical hardware device but it does not

src/pipewire/impl-factory.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_impl_factory Pipewire Factory Interface
+/** \defgroup pw_impl_factory PipeWire Factory Interface
  *
  * The factory is used to make objects on demand.
  */

src/pipewire/impl-metadata.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_impl_metadata Pipewire Metadata Interface
+/** \defgroup pw_impl_metadata PipeWire Metadata Interface
  *
  * The metadata is used to store key/type/value pairs per object id.
  */

src/pipewire/link.h

@@ -34,7 +34,7 @@ extern "C" {
 
 #include <pipewire/proxy.h>
 
-/** \defgroup pw_link Pipewire Link
+/** \defgroup pw_link PipeWire Link
  *
  * A link is the connection between 2 nodes (\ref pw_node). Nodes are
  * linked together on ports.

src/pipewire/loop.h

@@ -32,7 +32,7 @@ extern "C" {
 #include <spa/support/loop.h>
 #include <spa/utils/dict.h>
 
-/** \defgroup pw_loop Pipewire Loop
+/** \defgroup pw_loop PipeWire Loop
  *
  * PipeWire loop object provides an implementation of
  * the spa loop interfaces. It can be used to implement various

src/pipewire/main-loop.h

@@ -29,7 +29,7 @@
 extern "C" {
 #endif
 
-/** \defgroup pw_main_loop Pipewire Main-Loop Interface
+/** \defgroup pw_main_loop PipeWire Main-Loop Interface
  *
  * A main loop object
  */

src/pipewire/node.h

@@ -39,7 +39,7 @@ extern "C" {
 
 #include <pipewire/proxy.h>
 
-/** \defgroup pw_node Pipewire Node
+/** \defgroup pw_node PipeWire Node
  *
  */
 

src/pipewire/permission.h

@@ -31,7 +31,7 @@ extern "C" {
 
 #include <spa/utils/defs.h>
 
-/** \defgroup pw_permission Pipewire Permission
+/** \defgroup pw_permission PipeWire Permission
  *
  * Permissions are kept for a client and describe what the client is
  * allowed to do with an object.

src/pipewire/port.h

@@ -38,7 +38,7 @@ extern "C" {
 
 #include <pipewire/proxy.h>
 
-/** \defgroup pw_port Pipewire Port
+/** \defgroup pw_port PipeWire Port
  *
  */
 

src/pipewire/type.h

@@ -31,7 +31,7 @@ extern "C" {
 
 #include <spa/utils/type.h>
 
-/** \defgroup pw_type Pipewire Types
+/** \defgroup pw_type PipeWire Types
  */
 
 /**

src/pipewire/utils.h

@@ -38,7 +38,7 @@ extern "C" {
 #include <spa/utils/defs.h>
 #include <spa/pod/pod.h>
 
-/** \defgroup pw_utils Pipewire Utility Functions
+/** \defgroup pw_utils PipeWire Utility Functions
  *
  * Various utility functions
  */