[
https://issues.apache.org/jira/browse/COUCHDB-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848582#comment-13848582
]
Jan Lehnardt commented on COUCHDB-1987:
---------------------------------------
Noah said he’s going to fix this in his build-fauxton branch, but I’d like to
explain this for posterity.
make indeed throws this error, I didn’t suggest it is a grunt.js error, but
it’s the way we use Autotools. In particular, in how we use Autotools for
packaging. Each file that is supposed to end up in our final
apache-couchdb-x.y.z.tar.gz tarball needs to be marked as such in a
Makefile.am. For Fauxton that means we maintain a list of Fauxton files in
src/Makefila.am specified as `FAUXTON_FILES`:
FAUXTON_FILES = \
fauxton/app/addons/activetasks/assets/less/activetasks.less \
fauxton/app/addons/activetasks/base.js \
fauxton/app/addons/activetasks/resources.js \
…and so on
In that list, there is a line: `fauxton/app/initialize.js`, e.g. where we say
that file is supposed to go into the release tarball. That file however does
not exist at the time `make dist` is run, so make complains. I assume the
solution is that make needs to call grunt at some point to turn
fauxton/app/initialize.underscore into fauxton/app/initialize.js and I think
that is what Noah is doing in his branch. I just wanted to explain, why this
isn’t a make error.
> make distcheck broken
> ---------------------
>
> Key: COUCHDB-1987
> URL: https://issues.apache.org/jira/browse/COUCHDB-1987
> Project: CouchDB
> Issue Type: Bug
> Components: Build System
> Reporter: Jan Lehnardt
>
> make[1]: Entering directory `/vagrant/src'
> make[1]: *** No rule to make target `fauxton/app/initialize.js', needed by
> `distdir'. Stop.
> make[1]: Leaving directory `/vagrant/src'
> make: *** [distdir] Error 1
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
