Differences

This shows you the differences between two versions of the page.

--- making_bioconda_recipes [2024/10/08 11:11] – [After an eternity, my checks are all passing...] 134.190.221.192
+++ making_bioconda_recipes [2024/10/08 11:21] (current) – 134.190.221.192
@@ Line 4: / Line 4: @@
 Since the linked guide does a better job at explaining the basics than I could ever do, I will therefore only share **some useful hints and pitfalls to avoid**.
+If you are interested in seeing a loose example, [[https://github.com/Tassadaar/bioconda-recipes/tree/master/recipes/eukfinder|here]] is my work on eukfinder.
 I wish you the best of luck in your quest!
@@ Line 31: / Line 33: @@
 ====My program is for Linux only? Think again!====
 Bioconda and their Apple fanboys insisted that every bioconda recipe must be available for both Linux and MacOS, so don't be blindsided by this, fellow Linux enjoyer!
-Making your program more compatible entails adding binary executables and alternative build scripts for MacOS. **uname** is an universal environment variable to check for architecture, so you can put an if-elif block in your build.sh like this:
+Making your program more compatible entails adding appropriate binary executables and **tags** for MacOS. Follow this example **source** section of meta.yaml:
 <code>
-if [[ $(uname) == "Darwin" ]]; then
+source:
-    Your Code
+  - url: <executable compatible to both platforms>.tar.gz
-elif [[ $(uname) == "Linux" ]]; then
+    sha256: <sha256 of url>
-    Your Code
+  - url: <MacOS executable>.tar.gz # [osx]
-else
+    sha256: <sha256 of url> # [osx]
-    Your Code
+  - url: <Linux executable>.tar.gz # [linux]
-if
+    sha256: <sha256 of url> # [linux]
 </code>
-And before you ask, yes it is really called Darwin -- the Darwin we all know and **love**, thanks to Steve Jobs' sensationalism in the late 90s: "Because it's about evolution." ¯\_(ツ)_/¯
 ====After an eternity, my checks are all passing...====