# Shared library for stand-alone executable

**URL:** https://swi-prolog.discourse.group/t/shared-library-for-stand-alone-executable/659
**Category:** Help!
**Created:** [May 17, 2019, 7:59pm UTC](https://swi-prolog.discourse.group/t/shared-library-for-stand-alone-executable/659 "2019-05-17T19:59:55Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jamesnvc](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jamesnvc/32/14_2.png) [@jamesnvc](https://swi-prolog.discourse.group/u/jamesnvc)
#### Post date: [May 17, 2019, 10:05pm UTC](https://swi-prolog.discourse.group/t/shared-library-for-stand-alone-executable/659/2 "2019-05-17T22:05:29Z")

</div>

I was trying to do something similar previously & resorted to making the binary + libswipl.so (+ some other shared libraries) & started the binary with a script that set LD\_LIBRARY\_PATH to point to where those .so’s live. I would very like to have a better solution as well…

---

_[View the full topic](https://swi-prolog.discourse.group/t/shared-library-for-stand-alone-executable/659)._