# BinDeps for an executable

**URL:** https://discourse.julialang.org/t/bindeps-for-an-executable/3161
**Category:** General Usage
**Created:** [April 11, 2017, 9:02am UTC](https://discourse.julialang.org/t/bindeps-for-an-executable/3161 "2017-04-11T09:02:57Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)
#### Post date: [April 11, 2017, 4:24pm UTC](https://discourse.julialang.org/t/bindeps-for-an-executable/3161/3 "2017-04-11T16:24:08Z")

</div>

Another option would be to use the low-level build steps (which automate things like downloading and unzipping files) from BinDeps without actually using the full dependency handling tools (which, as @tkelman says, are only designed for libraries).

I ran into the same problem when trying to require the cmake executable, and I ended up creating a simple package [https://github.com/rdeits/CMakeWrapper.jl](https://github.com/rdeits/CMakeWrapper.jl) that handles the cmake download and compilation on all platforms using the low-level BinDeps tools: [https://github.com/rdeits/CMakeWrapper.jl/blob/master/deps/build.jl#L64](https://github.com/rdeits/CMakeWrapper.jl/blob/master/deps/build.jl#L64)

---

_[View the full topic](https://discourse.julialang.org/t/bindeps-for-an-executable/3161)._