• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

autom4te.cache/H03-Jul-2021-33,87829,447

doc/H03-May-2022-3,3622,629

examples/H03-May-2022-3,3062,400

lscp/H03-May-2022-1,369912

src/H03-May-2022-6,9674,212

AUTHORSH A D03-Jul-202134 21

COPYINGH A D03-Jul-202125.8 KiB505418

ChangeLogH A D03-Jul-202112 KiB292210

INSTALLH A D03-Jul-202115.2 KiB366284

Makefile.amH A D03-Jul-2021128 74

Makefile.gitH A D03-Jul-2021611 2017

Makefile.inH A D03-May-202227.3 KiB870771

NEWSH A D03-Jul-2021132 84

READMEH A D03-Jul-2021639 3219

README.cmakeH A D03-Jul-20212.5 KiB7351

TODOH A D03-Jul-2021255 128

aclocal.m4H A D03-Jul-2021363.4 KiB10,1619,185

autogen.shH A D03-Jul-202136 41

compileH A D03-Jul-20217.2 KiB349259

config.guessH A D03-Jul-202148.5 KiB1,6981,486

config.subH A D03-Jul-202133.4 KiB1,8541,677

configureH A D03-Jul-2021440.5 KiB15,11012,614

configure.acH A D03-Jul-20214.5 KiB135113

depcompH A D03-Jul-202123 KiB792502

install-shH A D03-Jul-202115 KiB542352

liblscp.spec.inH A D03-Jul-20217.2 KiB209182

lscp.pc.inH A D03-Jul-2021216 119

ltmain.shH A D03-Jul-2021316.5 KiB11,1487,979

missingH A D03-Jul-20216.7 KiB216143

README

1liblscp - LinuxSampler Control Protocol API
2-------------------------------------------
3
4liblscp is an implementation of the LinuxSampler control protocol,
5proposed as a C language API.
6
7Homepage: https://www.linuxsampler.org
8
9License: GNU Lesser General Public License (LGPL)
10
11Installation
12------------
13
14Unpack the tarball and in the extracted source directory:
15
16    cmake [-DCMAKE_INSTALL_PREFIX=/usr/local] -B build -S .
17    make -C build
18
19and optionally as root:
20
21    sudo make -C build install
22
23See also the README.cmake file in the source distribution.
24
25
26Enjoy.
27--
28rncbc aka Rui Nuno Capela
29rncbc at rncbc.org
30https://www.rncbc.org
31
32

README.cmake

1What is CMake?
2==============
3
4CMake is a cross platform build system, that can be used to replace the old
5auto-tools, providing a nice building environment and advanced features.
6
7Some of these features are:
8* Out of sources build: CMake allows you to build your software into a directory
9  different to the source tree. You can safely delete the build directory and
10  all its contents once you are done.
11* Multiple generators: classic makefiles can be generated for Unix and MinGW,
12  but also Visual Studio, XCode and Eclipse CDT projects among other types.
13* Graphic front-ends for configuration and build options.
14
15More information and documentation is available at the CMake project site:
16    http://www.cmake.org
17
18CMake is free software. You can get the sources and pre-compiled packages for
19Linux and other systems at:
20     http://www.cmake.org/cmake/resources/software.html
21
22How to use it?
23==============
24
251. You need CMake 3.13 or newer to build liblscp
26
272. Unpack the liblscp sources somewhere, or checkout the repository,
28   and create a build directory. For instance, using a command line shell:
29
30$ tar -xvzf Downloads/liblscp-x.y.z.tar.gz
31$ cd liblscp-x.y.z
32$ mkdir build
33
342. Execute CMake from the build directory, providing the source directory
35   location and optionally, the build options. There are several ways.
36
37* From a command line shell:
38
39$ pwd
40liblscp-x.y.z
41$ cd build
42$ cmake -DCMAKE_BUILD_TYPE=debug ..
43
443. Execute the build command. If you used the Makefiles generator (the default
45   in Linux and other Unix systems) then execute make, gmake, or mingw32-make.
46   If you generated a project file, use your IDE to build it.
47
48Compiling with make
49===================
50
51There are many targets available. To see a complete list of them, type:
52
53$ make help
54
55The build process usually hides the compiler command lines, to show them:
56
57$ make VERBOSE=1
58
59There is a "clean" target, but not a "distclean" one. You should use a build
60directory different to the source tree. In this case, the "distclean" target
61would be equivalent to simply removing the build directory.
62
63If something fails
64==================
65
66If there is an error message while executing CMake, this probably means that a
67required package is missing in your system. You should install the missing
68component and run CMake again.
69
70If there is an error executing the build process, after running a flawless CMake
71configuration process, this means that there may be an error in the source code,
72or in the build system, or something incompatible in 3rd party libraries.
73