2020-12-23 22:21:36 +01:00
|
|
|
/* SPDX-License-Identifier: LGPL-2.1-or-later */
|
2014-07-24 08:53:33 -04:00
|
|
|
/*
|
2019-10-01 09:20:35 +02:00
|
|
|
* Copyright (C) 2007 - 2009 Red Hat, Inc.
|
|
|
|
|
* Copyright (C) 2007 - 2008 Novell, Inc.
|
2014-07-24 08:53:33 -04:00
|
|
|
*/
|
|
|
|
|
|
all: fix up multiple-include-guard defines
Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and
libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include
guard, which meant that nm-test-utils.h could not tell which of them
was being included (and so, eg, if you tried to include
nm-ip4-config.h in a libnm test, it would fail to compile because
nm-test-utils.h was referring to symbols in src/nm-ip4-config.h).
Fix this by changing the include guards in the non-API-stable parts of
the tree:
- libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H
- libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__
- src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__
And likewise for all other headers.
The two non-"nm"-prefixed headers, libnm/NetworkManager.h and
src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and
__NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely
consistent with the general scheme, do still mostly make sense in
isolation.
2014-08-13 14:10:11 -04:00
|
|
|
#ifndef __NM_SETTING_BLUETOOTH_H__
|
|
|
|
|
#define __NM_SETTING_BLUETOOTH_H__
|
2014-07-24 08:53:33 -04:00
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
#if !defined(__NETWORKMANAGER_H_INSIDE__) && !defined(NETWORKMANAGER_COMPILATION)
|
|
|
|
|
#error "Only <NetworkManager.h> can be included directly."
|
2014-07-06 16:53:02 -04:00
|
|
|
#endif
|
|
|
|
|
|
2014-07-24 08:53:33 -04:00
|
|
|
#include "nm-setting.h"
|
|
|
|
|
|
|
|
|
|
G_BEGIN_DECLS
|
|
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
#define NM_TYPE_SETTING_BLUETOOTH (nm_setting_bluetooth_get_type())
|
|
|
|
|
#define NM_SETTING_BLUETOOTH(obj) \
|
|
|
|
|
(G_TYPE_CHECK_INSTANCE_CAST((obj), NM_TYPE_SETTING_BLUETOOTH, NMSettingBluetooth))
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_CLASS(klass) \
|
|
|
|
|
(G_TYPE_CHECK_CLASS_CAST((klass), NM_TYPE_SETTING_BLUETOOTH, NMSettingBluetoothClass))
|
|
|
|
|
#define NM_IS_SETTING_BLUETOOTH(obj) (G_TYPE_CHECK_INSTANCE_TYPE((obj), NM_TYPE_SETTING_BLUETOOTH))
|
|
|
|
|
#define NM_IS_SETTING_BLUETOOTH_CLASS(klass) \
|
|
|
|
|
(G_TYPE_CHECK_CLASS_TYPE((klass), NM_TYPE_SETTING_BLUETOOTH))
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_GET_CLASS(obj) \
|
|
|
|
|
(G_TYPE_INSTANCE_GET_CLASS((obj), NM_TYPE_SETTING_BLUETOOTH, NMSettingBluetoothClass))
|
2014-07-24 08:53:33 -04:00
|
|
|
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_SETTING_NAME "bluetooth"
|
|
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
#define NM_SETTING_BLUETOOTH_BDADDR "bdaddr"
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_TYPE "type"
|
2014-07-24 08:53:33 -04:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* NM_SETTING_BLUETOOTH_TYPE_DUN:
|
|
|
|
|
*
|
|
|
|
|
* Connection type describing a connection to devices that support the Bluetooth
|
|
|
|
|
* DUN profile.
|
|
|
|
|
*/
|
2020-09-28 16:03:33 +02:00
|
|
|
#define NM_SETTING_BLUETOOTH_TYPE_DUN "dun"
|
2014-07-24 08:53:33 -04:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* NM_SETTING_BLUETOOTH_TYPE_PANU:
|
|
|
|
|
*
|
2017-05-22 18:47:42 +02:00
|
|
|
* Connection type describing PANU connection to a Bluetooth NAP (Network
|
|
|
|
|
* Access Point).
|
2014-07-24 08:53:33 -04:00
|
|
|
*/
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_TYPE_PANU "panu"
|
|
|
|
|
|
2017-05-22 18:47:42 +02:00
|
|
|
/**
|
|
|
|
|
* NM_SETTING_BLUETOOTH_TYPE_NAP:
|
|
|
|
|
*
|
|
|
|
|
* Connection type describing a Bluetooth NAP (Network Access Point),
|
|
|
|
|
* which accepts PANU clients.
|
|
|
|
|
*/
|
|
|
|
|
#define NM_SETTING_BLUETOOTH_TYPE_NAP "nap"
|
|
|
|
|
|
2016-05-05 09:36:32 +02:00
|
|
|
/**
|
|
|
|
|
* NMSettingBluetooth:
|
2017-03-10 20:04:34 +01:00
|
|
|
*
|
|
|
|
|
* Bluetooth Settings
|
2016-05-05 09:36:32 +02:00
|
|
|
*/
|
2014-10-21 22:09:52 -04:00
|
|
|
struct _NMSettingBluetooth {
|
2020-09-28 16:03:33 +02:00
|
|
|
NMSetting parent;
|
2014-10-21 22:09:52 -04:00
|
|
|
};
|
2014-07-24 08:53:33 -04:00
|
|
|
|
|
|
|
|
typedef struct {
|
2020-09-28 16:03:33 +02:00
|
|
|
NMSettingClass parent;
|
2014-07-24 08:53:33 -04:00
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
/*< private >*/
|
|
|
|
|
gpointer padding[4];
|
2014-07-24 08:53:33 -04:00
|
|
|
} NMSettingBluetoothClass;
|
|
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
GType nm_setting_bluetooth_get_type(void);
|
2014-07-24 08:53:33 -04:00
|
|
|
|
2020-09-28 16:03:33 +02:00
|
|
|
NMSetting * nm_setting_bluetooth_new(void);
|
|
|
|
|
const char *nm_setting_bluetooth_get_bdaddr(NMSettingBluetooth *setting);
|
|
|
|
|
const char *nm_setting_bluetooth_get_connection_type(NMSettingBluetooth *setting);
|
2014-07-24 08:53:33 -04:00
|
|
|
|
|
|
|
|
G_END_DECLS
|
|
|
|
|
|
all: fix up multiple-include-guard defines
Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and
libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include
guard, which meant that nm-test-utils.h could not tell which of them
was being included (and so, eg, if you tried to include
nm-ip4-config.h in a libnm test, it would fail to compile because
nm-test-utils.h was referring to symbols in src/nm-ip4-config.h).
Fix this by changing the include guards in the non-API-stable parts of
the tree:
- libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H
- libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__
- src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__
And likewise for all other headers.
The two non-"nm"-prefixed headers, libnm/NetworkManager.h and
src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and
__NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely
consistent with the general scheme, do still mostly make sense in
isolation.
2014-08-13 14:10:11 -04:00
|
|
|
#endif /* __NM_SETTING_BLUETOOTH_H__ */
|