No, nor do I think it should be... I originally implemented it that way,
but I decided against it because I think explicitly having a build script
is cleaner.... do you disagree?


On Fri, Jan 24, 2014 at 4:09 AM, Brendan Zabarauskas <
notifications@github.com> wrote:

> In build.sh:
>
> > @@ -0,0 +1,9 @@
> > +#!/bin/sh
> > +
> > +mkdir build
> > +pushd build 1>&2
> > +cmake .. 1>&2
> > +make lib 1>&2 # cargo-lite wants stdout
> > +echo "cargo-lite: artifacts"
> > +find build/lib -type f
> > +popd 1>&2
>
> Is it possible to embed this stuff in the cargo-lite.conf file?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bjz/glfw-rs/pull/80/files#r9142992>
> .
>