makeflow_linker(1)

✨ makeflow_linker — the manual, but make it make sense ✨

okay bestie, sit down, hydrate, and let me tell you about makeflow_linker from the Cooperative Computing Tools 🫶 this is the makeflow_linker(1) page, section 1, and yes it's giving "my workflow has trust issues and I need to fix them automatically" 💅

---

🌸 NAME 🌸

makeflow_linker — automatic dependency location for workflows ✨

like. it finds your workflow's dependencies for you. no cap. 👑

---

🎀 SYNOPSIS 🎀

makeflow_linker [options] <workflow_description>

---

🦋 DESCRIPTION 🦋

so makeflow_linker is that girl who automatically figures out the dependencies of your workflows. she takes a workflow description — and heads up, right now Makeflow syntax is required — and then she recursively determines all the dependencies and produces a self-contained package. periodt. ✨

she's fluent in Python, Perl, and shared libraries. multilingual queen 🌈

now the tea ☕ — makeflow_linker finds dependencies by static analysis. that means eval and other dynamic code loading can obscure dependencies, which makes makeflow_linker miss some critical dependencies 😭 so the recommendation, fr fr, is to avoid these techniques when designing a workflow. don't be sneaky with your code loading, bestie, she can't read your mind 🫶

---

💖 OPTIONS 💖

• --dry-run — run it without actually creating directories or copying dependencies. a little dress rehearsal, no commitment 🎭
• -h, --help — shows this help screen. your girl is helpful 💅
• -n, --use-named — do not copy files that are part of a named dependency, e.g. standard libraries. leave the stdlibs where they live, they're fine 🏠
• -o, --output=<directory> — specify the output directory. tell her where to put the goods 📦
• --verbose — output status during the run. she'll narrate the whole thing, main character energy 🎤
• -v, --version — display version information ⭐

---

🔥 EXIT STATUS 🔥

• On success, returns zero. slay ✨
• On failure (typically permission errors), returns non-zero. it's giving "you didn't have permission, bestie" 😭

---

💀 BUGS 💀

• The makeflow_linker does not check for naming collisions beyond the initial workflow inputs 🙈
• The makeflow_linker relies on regex parsing of files 💀

ngl these are real. regex is iconic but she is not a compiler. iykyk 🧚

---

🌈 EXAMPLES 🌈

Package a workflow:

makeflow_linker -o example_mf example.mf

Run packaged workflow:

makeflow example_mf/example.mf

look at her go 😭✨ obsessed.

---

👑 COPYRIGHT 👑

The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. This software is distributed under the GNU General Public License. See the file COPYING for details.

---

🍓 SEE ALSO 🍓

• makeflow(1) perl(1), python(1), ldd(1)

---

and that's the whole page, bestie!! this was CCTools 8.0.0 DEVELOPMENT, and the page you just read was dated like a proper manpage footer because we keep the facts even when we keep the vibe 💖 go package something cute, stay static-analysis-safe, and remember: no eval, no regrets 🦋💅