# Call alternative binary from appimage?

**URL:** <https://discourse.appimage.org/t/call-alternative-binary-from-appimage/93>\
**Category:** Creating AppImages\
**Created:** [November 4, 2016, 7:11am UTC](https://discourse.appimage.org/t/call-alternative-binary-from-appimage/93 "2016-11-04T07:11:25Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![probono](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/probono/32/81_2.png) [@probono](https://discourse.appimage.org/u/probono)\
**Post date:** [November 5, 2016, 3:02pm UTC](https://discourse.appimage.org/t/call-alternative-binary-from-appimage/93/6 "2016-11-05T15:02:14Z")

</div>

Well, the architectural question is what should be handled by AppRun (YOUR launcher that is supposed to also work outside of an AppImage, e.g., in a standalone AppDir) vs. AppImage’s `runtime.c` (common to all AppImages)… which already has some `--appimage-...` options.

---

_[View the full topic](https://discourse.appimage.org/t/call-alternative-binary-from-appimage/93)._