Michael R. Crusoe

@temehi That's fine, I understand moving to a new milestone, but shouldn't the issue remain open?

Releasing version 1.0 of https://github.com/common-workflow-language/common-workflow-language/ is my sole priority until BOSC/ISMB in July. Let's talk there?

and by there I mean Orlando, Florida at the conference; if anyone is attending from this group

Thank you @esiragusa for making this a priority

Ping :-)

Thanks for the update. On Tue Feb 24 2015 at 9:50:11 AM Enrico Siragusa [email protected] wrote: > @h-2 https://github.com/h-2 this flag triggers tons of warnings... > > — > Reply...

@h-2 Yes, I had to manually specify `util/cmake/seqan-config.cmake usr/share/cmake/` as otherwise it didn't install.

> Is there a particular reason for not using the cmake-targets? E.G. for libseqan2-dev, it would be SEQAN_BUILD_SYSTEM=SEQAN_RELEASE_LIBRARY. No particular reason; I think too much else was "on fire" to...

From https://buildd.debian.org/status/fetch.php?pkg=seqan2&arch=mips&ver=2.4.0%2Bdfsg-3&stamp=1518109921&raw=0 which has no build parallelism > [ 16%] Building CXX object tests/seeds/CMakeFiles/test_seeds_banded_chain_alignment_interface.dir/test_banded_chain_alignment_interface.cpp.o cd //seqan2-2.4.0+dfsg/obj-mips-linux-gnu/tests/seeds && /usr/bin/c++ -DSEQAN_DISABLE_VERSION_CHECK -DSEQAN_ENABLE_TESTING=1 -DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_EXECINFO=1 -DSEQAN_HAS_OPENMP=1 -DSEQAN_HAS_ZLIB=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I//seqan2-2.4.0+dfsg/include -g -O2 -fdebug-prefix-map=//seqan2-2.4.0+dfsg=....

@h-2 Ah, I remember the problem now. We can't combine `-DSEQAN_BUILD_SYSTEM=SEQAN_RELEASE_LIBRARY` and `-DSEQAN_BUILD_SYSTEM=SEQAN_RELEASE_APPS` in a single build :-/