FSPLIB is a C-based implementation of an FSP protocol stack that enables file service communication.
The FSPLIB project provides an efficient implementation of an FSP (file service protocol) stack that is coded in C. Its library API is simple to use and modeled according to POSIX API standards. Any C/C++ program can easily incorporate FSP support through this library.
For building the software, the recommended methods are either Scons or GNU Autotools. Although both are viable options, the former is more commonly preferred due to its ease of use. If you prefer using autotools, you need to create ./configure first by running autoreconf -i.
To initiate Scons building, run the command "scons [options] [install]" to get started on building and installing the library and header file. Unlike Autotools, Scons requires build-time configure options to be added to the install target as well.
You have the ability to configure the locking subsystem at build time, which involves two lock configuration options. It is important to note that Scons does not use leading "--" before option names. For instance, you may run the command "scons with-lockprefix=/tmp/.FSPL install" to set the lock prefix path to /tmp/.FSPL, (default setting), or "scons with-locking=none/semop/lockf" to select from one of the three current types of locking subsystem: none, lockf, and semop.
The prefix=/path option informs Scons where to install the built library and header file. This is a standard option. Additionally, you may choose to compile the code with more debug code inside by using the option "--enable-maintainer-mode=yes."
For building the software, the recommended methods are either Scons or GNU Autotools. Although both are viable options, the former is more commonly preferred due to its ease of use. If you prefer using autotools, you need to create ./configure first by running autoreconf -i.
To initiate Scons building, run the command "scons [options] [install]" to get started on building and installing the library and header file. Unlike Autotools, Scons requires build-time configure options to be added to the install target as well.
You have the ability to configure the locking subsystem at build time, which involves two lock configuration options. It is important to note that Scons does not use leading "--" before option names. For instance, you may run the command "scons with-lockprefix=/tmp/.FSPL install" to set the lock prefix path to /tmp/.FSPL, (default setting), or "scons with-locking=none/semop/lockf" to select from one of the three current types of locking subsystem: none, lockf, and semop.
The prefix=/path option informs Scons where to install the built library and header file. This is a standard option. Additionally, you may choose to compile the code with more debug code inside by using the option "--enable-maintainer-mode=yes."
What's New
Version 0.10: N/A