You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am testing locally the following recipe (meta.yaml) with the command bioconda-utils build --git-range master --packages drompa:
{% set version = "3.7.2" %}
package:
name: drompa3
version: {{ version }}
source:
url: https://github.com/rnakato/DROMPA3/archive/refs/tags/v{{version}}.tar.gz
sha256: 48aa8a5144e190b92e1c2c53c7782723584d8e923f563a58cc2beec08822fb94
requirements:
build:
- {{ compiler('c') }}
- make
host:
- gtk2
- gsl
- samtools
- zlib
- r-base
test:
commands:
- parse2wig
about:
home: https://github.com/rnakato/DROMPA3
license: GNU General Public License v2.0
summary: DROMPA can be used for multiple analyses of ChIP-seq data
However, it does not manage to find the command parse2wig. I am wondering if this is because the uncompressed file is in uppercase DROMPA3-3.7.2 ? The linting tells me however that I cannot use an uppercase package name.
I have also tested the building with and without the following build.sh:
The build.sh needs to do something more along the lines of
#!/bin/bash## let Conda provide `CC` variable;
sed -ie /^CC/d Makefile
## connect extra paths to Makefile## see: https://github.com/rnakato/DROMPA3/blob/master/Makefile
CFLAGS="${CFLAGS} -I${PREFIX}/include/cairo -I${PREFIX}/include/gtk-2.0/gtk"
LIBS="${LIBS}${LDFLAGS}"## compile the binaries
make parse2wig drompa_peakcall
## transfer the binaries to prefix
cp parse2wig drompa_peakcall ${PREFIX}/bin/
I left out drompa_draw because that needs the GIO library, which I'm not sure is packaged for Conda.
Hi,
I am testing locally the following recipe (meta.yaml) with the command
bioconda-utils build --git-range master --packages drompa
:However, it does not manage to find the command
parse2wig
. I am wondering if this is because the uncompressed file is in uppercaseDROMPA3-3.7.2
? The linting tells me however that I cannot use an uppercase package name.I have also tested the building with and without the following
build.sh
:Any help will be greatly appreciated. Thanks.
The text was updated successfully, but these errors were encountered: