Changeset 3983
- Timestamp:
- Aug 26, 2020, 4:40:05 AM (3 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/README.developer
r3550 r3983 62 62 63 63 Code that depends on samtools API should be excluded from the build 64 when configured --without-samtools, i.e., put files within 65 `YAT_HAVE_LIBBAM` conditionals (or alternatively put code inside 66 `#ifdef YAT_HAVE_SAMTOOL` preprocessor conditionals). To 67 differatniuate between code that compiles against libhts and libbam, 68 use `#ifdef YAT_HAVE_HTSLIB` (or `#ifndef`. In order to support 69 multiple inclusion styles we do not include <bam.h> directly, but 70 `#include <config_bam.h>` and `#include YAT_BAM_HEADER`. Similarly, 71 for `<sam.h>` include `YAT_SAM_HEADER`. For more details on this, 72 refer to `yat/omic/config_bam.h`. 64 when configured --without-htslib, i.e., put files within 65 `YAT_HAVE_HTSLIB` conditionals, as defined in 66 'yat/utility/config_public.h'. 73 67 74 68 === Doxygen === … … 154 148 http://www.gnu.org/software/libtool/manual/libtool.html#Debugging-executables 155 149 156 157 == Avoid compiler warnings from hts.h ==158 159 When compiling with GCC in C++98 mode with -pedantic (as is160 recommended under development) the file 'htslib/hts.h' will cause161 warnings if it's not installed as system header. You can avoid this162 warning by replacing CPPFLAGS=-I/path/to/htslib with163 CPPFLAGS="-isystem /path/to/htslib".164 150 165 151 = Release Procedure =
Note: See TracChangeset
for help on using the changeset viewer.