On Mon, 07 Oct 2013 08:47:10 -0400 Jonathan Bayer <
linuxgu...@gmail.com> wrote:
JB> I just started looking at the Design Center. It looks impressive, but
JB> I ran into a roadblock:
...
JB> I traced this to the fact that the stdlib wasn't in the inputs list.
JB> This is the "inputs" as it was generated:
JB> "inputs" slist => { "sketches/libraries/dclib/
library.cf",
JB> "sketches/system/tzconfig/
main.cf" };
JB> When I changed it to the following and copied the stdlib into the
JB> libraries directory, it worked:
...
JB> So, did I do anything wrong?
You didn't do anything wrong :)
This is due to some recent changes in the master branch:
commit 1f981349ac24b002c046706335f15dca46a7c122
Author: Nick Anderson <
ni...@cmdln.org>
Date: Fri Sep 13 00:06:10 2013 -0400
So I've added a --standalone_inputs list parameter to
cf-sketch.pl to
make adding the stdlib easier (the example you gave becomes a
modification of the
cf-sketch.pl invocation), but the proper solution is
not ready yet. In the end, no sketches will have a hard dependency on
the stdlib bundled with DC. This is still under construction and we
will have more concrete things to say next week; it only affects the
standalone runfile. Sorry for the inconvenience.
JB> Also, I'd like to have a comment automatically included at the top of
JB> the generated deploy file, warning users to not change it. Is it
JB> possible to do that, or do I have to do it manually?
I added the --runfile_header="x" option to
cf-sketch.pl, which sets a
"header" option for the runfile as far as the DC API is concerned. That
should do it for you, whether you use the command-line option or change
your DC API config.json.
HTH
Ted