This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-26
Channels
- # admin-announcements (4)
- # beginners (3)
- # boot (78)
- # cider (13)
- # cljs-dev (29)
- # cljs-edn (8)
- # cljsjs (11)
- # cljsrn (15)
- # clojure (81)
- # clojure-beijing (2)
- # clojure-belgium (3)
- # clojure-canada (1)
- # clojure-dusseldorf (8)
- # clojure-greece (6)
- # clojure-russia (40)
- # clojure-sg (1)
- # clojure-uk (59)
- # clojurebridge (1)
- # clojurescript (101)
- # core-logic (1)
- # cursive (3)
- # data-science (1)
- # datomic (60)
- # emacs (4)
- # error-message-catalog (12)
- # funcool (1)
- # hoplon (60)
- # jobs (1)
- # jobs-discuss (40)
- # leiningen (5)
- # liberator (1)
- # mount (22)
- # off-topic (8)
- # om (16)
- # onyx (53)
- # re-frame (11)
- # reagent (2)
- # specter (4)
- # testing (18)
- # untangled (51)
@juhoteperi: I still have to specify a source path env in build.boot though, right?
and can you elaborate on why it makes sense to have different builds in different files?
@shaunlebron: Yes, Boot source-paths specify sources for fileset
Okay, so if I have .cljs.file in relative path public/js/main.cljs.edn
inside the fileset, the resulting output would be public/js/main.js
. We use the relative path of cljs edn file to set output-to etc. options.
@juhoteperi: thanks I understand that location of the build files specifies location of the output
it can be specified as a key inside the file as well of course
i was just wondering if anything about how boot was working required that to be the case
so you’re saying it makes sense because it chooses to represent the path that way