Installation and use of CoAP on Linux server (2)

1. Download the libcoap source code

https://github.com/obgm/libcoap/tree/release-4.2.0

2. Installation steps

./autogen.sh
mkdir Linux
./configure --prefix=$(pwd)/ISVP_lib --disable-dtls    

There will be the following problems when performing the above operations:

checking for dot... no
configure: WARNING: ==> dot not found - continuing without DOT support
configure: WARNING: ==> The libcoap html documentation will be build without DOT graphics!
checking for a2x... no
configure: WARNING: ==> You want to build the manpages, but a2x was not found!
configure: error: ==> Install the package that contains a2x (mostly asciidoc) or disable the build of the manpages using '--disable-manpages'.

Solution:

./configure --prefix=$(pwd)/Linux --disable-manpages --disable-dtls

Execute after no error

make && make install

The generated header files and library files will be stored in the Linux directory of the current path 

Then we get the following version information:

3. The meaning of compilation parameters

Execute ./configure -help

`configure' configures libcoap 4.2.0 to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version           display version information and exit
  -q, --quiet, --silent   do not print `checking ...' messages
      --cache-file=FILE   cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create         do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR            user executables [EPREFIX/bin]
  --sbindir=DIR           system admin executables [EPREFIX/sbin]
  --libexecdir=DIR        program executables [EPREFIX/libexec]
  --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR    modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR     modifiable single-machine data [PREFIX/var]
  --libdir=DIR            object code libraries [EPREFIX/lib]
  --includedir=DIR        C header files [PREFIX/include]
  --oldincludedir=DIR     C header files for non-gcc [/usr/include]
  --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]
  --datadir = DIR read-only architecture-independent data [DATAROOTDIR]
  --infodir = DIR info documentation [DATAROOTDIR / info]
  --localedir = DIR locale-dependent data [DATAROOTDIR / locale]
  --mandir = DIR man documentation [DATAROOTDIR / man]
  --docdir = DIR documentation root [DATAROOTDIR / doc / libcoap]
  --htmldir = DIR html documentation [DOCDIR]
  --dvidir = DIR dvi documentation [DOCDIR]
  --pdfdir = DIR pdf documentation [DOCDIR]
  --psdir = DIR ps documentation [DOCDIR]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Optional Features:
  --disable-option-checking  ignore unrecognized --enable/--with options
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --enable-silent-rules   less verbose build output (undo: "make V=1")
  --disable-silent-rules  verbose build output (undo: "make V=0")
  --enable-dependency-tracking
                          do not reject slow dependency extractors
  --disable-dependency-tracking
                          speeds up one-time build
  --enable-shared[=PKGS]  build shared libraries [default=yes]
  --enable-static[=PKGS]  build static libraries [default=yes]
  --enable-fast-install[=PKGS]
                          optimize for fast installation [default=yes]
  --disable-libtool-lock  avoid locking (might break parallel builds)
  --enable-documentation  Enable building all the documentation [default=yes]
  --enable-doxygen        Enable building the doxygen documentation
                          [default=yes]
  --enable-manpages       Enable building the manpages [default=yes]
  --enable-dtls           Enable building with DTLS support [default=yes]
  --enable-tests          Enable building the binary testsuite [default=no]
  --enable-examples       Enable building the example binaries [default=yes]
  --enable-gcov           Enable building with gcov test coverage support
                          [default=no]

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-pic[=PKGS]       try to use only PIC/non-PIC objects [default=use
                          both]
  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
  --with-sysroot=DIR Search for dependent libraries within DIR
                        (or the compiler's sysroot if not specified).
  --with-gnutls           Use GnuTLS for DTLS functions
  --with-openssl          Use OpenSSL for DTLS functions
  --with-tinydtls         Use TinyDTLS for DTLS functions

Some influential environment variables:
  PKG_CONFIG  path to pkg-config utility
  PKG_CONFIG_PATH
              directories to add to pkg-config's search path
  PKG_CONFIG_LIBDIR
              path overriding pkg-config's built-in search path
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  LIBS        libraries to pass to the linker, e.g. -l<library>
  CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  CPP         C preprocessor
  A2X         a2x command
  GnuTLS_CFLAGS
              C compiler flags for GnuTLS, overriding pkg-config
  GnuTLS_LIBS linker flags for GnuTLS, overriding pkg-config
  OpenSSL_CFLAGS
              C compiler flags for OpenSSL, overriding pkg-config
  OpenSSL_LIBS
              linker flags for OpenSSL, overriding pkg-config
  CUNIT_CFLAGS
              C compiler flags for CUNIT, overriding pkg-config
  CUNIT_LIBS  linker flags for CUNIT, overriding pkg-config
  CTAGS_PROG  the 'exctags' program to use for make target 'update-map-file'

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

4. Debug and use

Open the server

cd examples/
./coap-server

At this time, you can Copperopen the server address on FireFox with the plug- in installed . Note: The CoAP debugging tool Copper is a plug-in of Firefox. The highest version of Firefox supported by this plug-in is 52.0, which is not compatible with the new version of Firefox; it can be used in Chrome Install copper plug-in in the browser;

 For the installation Copperprocess of the plug-in, see "CoAP Client Copper Plug-in (3)"

Guess you like

Origin blog.csdn.net/Swallow_he/article/details/112365343