I went through a bit of this in earlier AudioIO versions where I had a C shim around PortAudio. I think this commit[1] should be a decent one to see how I was doing it. Eventually I ended up pre-compiling and shipping binaries, before finally ditching the C code and writing it in pure Julia.
That said, are you sure you need the C code? It definitely makes distribution more of a pain, and slows down the install process. I also discovered there are a lot of Julia users who don't have a C toolchain installed, so none of them will be able to use your package. On Thu, Feb 19, 2015, at 09:46 AM, Sergey Bartunov wrote: > I'm going to release a new julia package which contains some C code. I > would like to compile that code during installation and to specify > somehow that this package is UNIX-only as it uses SharedArrays. What > is the best way to implement this? > > This package implements a machine learning algorithm and the learning > process is quite sophisticated, so I also would like to include some > julia and shell scripts which simplify usage of the package but are > not 100% required. So would it be a good practice to put these scripts > in a separate directory? Links: 1. https://github.com/ssfrr/AudioIO.jl/tree/9d9af6e4cd01caf518de90cd97ab32f209ec5615
