diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3a5f9b54..d561ee13 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -8,7 +8,7 @@ project(fastafs)
# Do this once in a while - find different bugs
#set(CMAKE_CXX_COMPILER "clang++")
-set(PROJECT_VERSION "1.6.1")
+set(PROJECT_VERSION "1.6.2")
set(PACKAGE_URL "https://github.com/yhoogstrate/fastafs")
set(PACKAGE_BUGREPORT "${PACKAGE_URL}/issues")
@@ -110,9 +110,23 @@ add_executable(fastafs
src/fuse.cpp
src/lsfastafs.cpp
)
-
set_target_properties(fastafs PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${BUILD_DIR}")
+# mount-only binary, without all the other stuff 'mount.fastafs' [for fstab]
+add_executable(mount.fastafs
+ src/main_mount.cpp
+ src/fasta_to_fastafs.cpp
+ src/ucsc2bit_to_fastafs.cpp
+ src/fastafs.cpp
+ src/ucsc2bit.cpp
+ src/twobit_byte.cpp
+ src/database.cpp
+ src/utils.cpp
+ src/fuse.cpp
+ src/lsfastafs.cpp
+ )
+set_target_properties(mount.fastafs PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${BUILD_DIR}")
+
add_library(libfastafs SHARED
src/fasta_to_fastafs.cpp
src/ucsc2bit_to_fastafs.cpp
@@ -166,6 +180,7 @@ add_test(test_utils "${BUILD_TEST_DIR}/test_utils")
# The compiled binary, usually to: /usr/local/bin/fastafs
install(TARGETS fastafs DESTINATION "bin")
+install(TARGETS mount.fastafs DESTINATION "bin")
install(TARGETS libfastafs LIBRARY DESTINATION "lib" PUBLIC_HEADER DESTINATION "include/libfastafs")
# ----------------------------------------------------------------------
diff --git a/Changelog b/Changelog
index 0f6d4ee6..7d6166b6 100644
--- a/Changelog
+++ b/Changelog
@@ -1,3 +1,10 @@
+2019-09-06 Youri Hoogstrate
+
+ * v1.6.2
+ * Rewritten argument parsing of fuse/mounting
+ * Added binary `mount.fastafs` only for mounting, wihtout the toolkit
+ * `fastafs --version` will now also output whether the binary was compiled as debug or release.
+
2019-08-21 Youri Hoogstrate
* v1.6.1
diff --git a/README.md b/README.md
index 73ed1301..5cff4e4b 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ Here we propose a solution; a mixture of 2bit compression and random on FASTA ve
FASTAFS is compatible with 2bit files but 2bit has some limitations and does for instance not allow mounting DICT files needed for CRAM and Picard tools. The 2bit files can be convert to FASTAFS and, more importantly, a mounted FASTAFS mountpoint will not only virtualize the FASTA but also the 2bit file. Is FASTAFS this famous 15th standard ()?
Partially, but it is not designed to replace FASTA nor 2bit as those mountpoints should be used as flat files did before and the virtualization of dict files is not possible when we mount 2bit files.
-## installation and compilation
+## Installation and compilation
Currently the package uses cmake for compilation
Required dependencies are:
@@ -165,6 +165,30 @@ aaaa
c
```
+### Find all running `fastafs mount` / `mount.fastafs` instances
+
+The output format of `fastafs ps` is: `\t