I had the same issue and solved it by having 3 source paths:
- src (containing the app)
- src-dev (containing the dev version of the logging ns)
- src-prod (containing the production version of the logging ns)
cljsbuild development builds use source paths [src src-dev] and
production builds use
I'd love to know the correct answer to this too, but in the meantime,
here's how I've been doing it:
I define the release version in some namespace. To use it, I require this
namespace. Eg release-namespace/func
Then I create a separate file for the debug build and I require the release
Hi,
I'm trying to figure out how to do the following:
Have a shared cljs/* ...
For the dev build, have (debug ...) compile to (js/console.log ...)
For the release build, have (debug ...) compile to (do).
Basically, I want different things to happen depending on whether
the build is
If you used cljx, you could probably use the feature expressions to do what
you want.
https://github.com/lynaghk/cljx
You'd need to set up a custom rule for it, but it seems well within the
scope of the project.
On Thu, Apr 3, 2014 at 8:50 AM, t x txrev...@gmail.com wrote:
Hi,
I'm trying
I don't use cljx. It slows down lein cljsbuild auto.
I'm using pure clojurescript. Is there a way to get the dev /
release tag passed somehow?
On Thu, Apr 3, 2014 at 6:58 AM, Alex Robbins
alexander.j.robb...@gmail.com wrote:
If you used cljx, you could probably use the feature expressions to do
The correct statement should be: I *no longer* use cljx. :-)
On Thu, Apr 3, 2014 at 8:05 AM, t x txrev...@gmail.com wrote:
I don't use cljx. It slows down lein cljsbuild auto.
I'm using pure clojurescript. Is there a way to get the dev /
release tag passed somehow?
On Thu, Apr 3, 2014 at
