2019-09-10 09:19:01 +00:00
|
|
|
// SPDX-License-Identifier: LGPL-2.1+
|
2014-07-24 12:53:33 +00:00
|
|
|
/*
|
2019-10-01 07:20:35 +00:00
|
|
|
* Copyright (C) 2007 - 2008 Novell, Inc.
|
|
|
|
* Copyright (C) 2007 - 2011 Red Hat, Inc.
|
2014-07-24 12:53:33 +00: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 18:10:11 +00:00
|
|
|
#ifndef __NM_ACCESS_POINT_H__
|
|
|
|
#define __NM_ACCESS_POINT_H__
|
2014-07-24 12:53:33 +00:00
|
|
|
|
2014-07-06 20:53:02 +00:00
|
|
|
#if !defined (__NETWORKMANAGER_H_INSIDE__) && !defined (NETWORKMANAGER_COMPILATION)
|
|
|
|
#error "Only <NetworkManager.h> can be included directly."
|
|
|
|
#endif
|
|
|
|
|
2017-03-09 12:02:20 +00:00
|
|
|
#include "nm-object.h"
|
2014-07-24 12:53:33 +00:00
|
|
|
|
|
|
|
G_BEGIN_DECLS
|
|
|
|
|
|
|
|
#define NM_TYPE_ACCESS_POINT (nm_access_point_get_type ())
|
|
|
|
#define NM_ACCESS_POINT(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), NM_TYPE_ACCESS_POINT, NMAccessPoint))
|
|
|
|
#define NM_ACCESS_POINT_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), NM_TYPE_ACCESS_POINT, NMAccessPointClass))
|
|
|
|
#define NM_IS_ACCESS_POINT(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), NM_TYPE_ACCESS_POINT))
|
|
|
|
#define NM_IS_ACCESS_POINT_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), NM_TYPE_ACCESS_POINT))
|
|
|
|
#define NM_ACCESS_POINT_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), NM_TYPE_ACCESS_POINT, NMAccessPointClass))
|
|
|
|
|
|
|
|
#define NM_ACCESS_POINT_FLAGS "flags"
|
|
|
|
#define NM_ACCESS_POINT_WPA_FLAGS "wpa-flags"
|
|
|
|
#define NM_ACCESS_POINT_RSN_FLAGS "rsn-flags"
|
|
|
|
#define NM_ACCESS_POINT_SSID "ssid"
|
|
|
|
#define NM_ACCESS_POINT_BSSID "bssid"
|
|
|
|
#define NM_ACCESS_POINT_FREQUENCY "frequency"
|
|
|
|
#define NM_ACCESS_POINT_MODE "mode"
|
|
|
|
#define NM_ACCESS_POINT_MAX_BITRATE "max-bitrate"
|
|
|
|
#define NM_ACCESS_POINT_STRENGTH "strength"
|
2015-04-27 17:50:39 +00:00
|
|
|
#define NM_ACCESS_POINT_LAST_SEEN "last-seen"
|
2014-07-24 12:53:33 +00:00
|
|
|
|
|
|
|
/* DEPRECATED */
|
|
|
|
#define NM_ACCESS_POINT_HW_ADDRESS "hw-address"
|
|
|
|
|
2016-05-05 07:36:32 +00:00
|
|
|
/**
|
|
|
|
* NMAccessPoint:
|
|
|
|
*/
|
2019-10-18 06:12:01 +00:00
|
|
|
typedef struct _NMAccessPointClass NMAccessPointClass;
|
2014-07-24 12:53:33 +00:00
|
|
|
|
|
|
|
GType nm_access_point_get_type (void);
|
|
|
|
|
|
|
|
NM80211ApFlags nm_access_point_get_flags (NMAccessPoint *ap);
|
|
|
|
NM80211ApSecurityFlags nm_access_point_get_wpa_flags (NMAccessPoint *ap);
|
|
|
|
NM80211ApSecurityFlags nm_access_point_get_rsn_flags (NMAccessPoint *ap);
|
2014-07-02 18:25:43 +00:00
|
|
|
GBytes * nm_access_point_get_ssid (NMAccessPoint *ap);
|
2014-07-24 12:53:33 +00:00
|
|
|
const char * nm_access_point_get_bssid (NMAccessPoint *ap);
|
|
|
|
guint32 nm_access_point_get_frequency (NMAccessPoint *ap);
|
|
|
|
NM80211Mode nm_access_point_get_mode (NMAccessPoint *ap);
|
|
|
|
guint32 nm_access_point_get_max_bitrate (NMAccessPoint *ap);
|
|
|
|
guint8 nm_access_point_get_strength (NMAccessPoint *ap);
|
2015-08-09 10:24:22 +00:00
|
|
|
NM_AVAILABLE_IN_1_2
|
all: don't use gchar/gshort/gint/glong but C types
We commonly don't use the glib typedefs for char/short/int/long,
but their C types directly.
$ git grep '\<g\(char\|short\|int\|long\|float\|double\)\>' | wc -l
587
$ git grep '\<\(char\|short\|int\|long\|float\|double\)\>' | wc -l
21114
One could argue that using the glib typedefs is preferable in
public API (of our glib based libnm library) or where it clearly
is related to glib, like during
g_object_set (obj, PROPERTY, (gint) value, NULL);
However, that argument does not seem strong, because in practice we don't
follow that argument today, and seldomly use the glib typedefs.
Also, the style guide for this would be hard to formalize, because
"using them where clearly related to a glib" is a very loose suggestion.
Also note that glib typedefs will always just be typedefs of the
underlying C types. There is no danger of glib changing the meaning
of these typedefs (because that would be a major API break of glib).
A simple style guide is instead: don't use these typedefs.
No manual actions, I only ran the bash script:
FILES=($(git ls-files '*.[hc]'))
sed -i \
-e 's/\<g\(char\|short\|int\|long\|float\|double\)\>\( [^ ]\)/\1\2/g' \
-e 's/\<g\(char\|short\|int\|long\|float\|double\)\> /\1 /g' \
-e 's/\<g\(char\|short\|int\|long\|float\|double\)\>/\1/g' \
"${FILES[@]}"
2018-07-11 05:40:19 +00:00
|
|
|
int nm_access_point_get_last_seen (NMAccessPoint *ap);
|
2014-07-24 12:53:33 +00:00
|
|
|
|
2014-10-22 16:32:46 +00:00
|
|
|
GPtrArray * nm_access_point_filter_connections (NMAccessPoint *ap,
|
|
|
|
const GPtrArray *connections);
|
2014-07-24 12:53:33 +00:00
|
|
|
|
|
|
|
gboolean nm_access_point_connection_valid (NMAccessPoint *ap,
|
|
|
|
NMConnection *connection);
|
|
|
|
|
|
|
|
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 18:10:11 +00:00
|
|
|
#endif /* __NM_ACCESS_POINT_H__ */
|