Difference: BreseqDevelopment (1 vs. 2)

Revision 22011-01-30 - JeffreyBarrick

 
META TOPICPARENT name="ToolsBacterialGenomeResequencing"

Breseq Developer Notes

Changed:
<
<
In addition to the normal prerequisites for breseq, you will also need updated versions of these tools to work on breseq development. (On MacOSX, these can be installed using MacPorts.)
>
>
In addition to the normal prerequisites for breseq, you will also need updated versions of these tools to work on breseq development. On Mac OS X, these can be installed using MacPorts.
 
Changed:
<
<
  • Mercurial
  • automake
  • autoconf
  • libtool
>
>
Deleted:
<
<
  • Sphinx (optional, only required for building documentation)
 
Changed:
<
<
To get started, first clone the breseq repository.
>
>
To get started, first clone the breseq code repository.
 
Changed:
<
<
Then run the bootstrap script. This generates the usual configure script.
>
>
Added:
>
>
 >hg clone http://barricklab.org/hg

Then change into the breseq directory and run the bootstrap script.

 >./bootstrap

This generates the usual configure script, so now you can:

 >./configure
 >make
 >make install

In order to make dist you will also need to install:

Again, this can be done using MacPorts on Mac OS X.

 

Revision 12011-01-25 - JeffreyBarrick

 
META TOPICPARENT name="ToolsBacterialGenomeResequencing"

Breseq Developer Notes

In addition to the normal prerequisites for breseq, you will also need updated versions of these tools to work on breseq development. (On MacOSX, these can be installed using MacPorts.)

  • Mercurial
  • automake
  • autoconf
  • libtool
  • Sphinx (optional, only required for building documentation)

To get started, first clone the breseq repository.

Then run the bootstrap script. This generates the usual configure script.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright ©2025 Barrick Lab contributing authors. Ideas, requests, problems? Send feedback