Hi David,
next monday me, Federico and Francesco (in cc) which are interns in sinapsi to
learn about big data, machine learning and data visualizations/infographics,
will take a look at cljsbuild code to understand where Compilable protocol is
involved.
Thank again for your advice and support.
I chimed in on the patch. Taking Brenton's approach sounds like it would be
significantly simpler and require a very small patch to lein-cljsbuild.
On Fri, Dec 7, 2012 at 1:24 PM, Mimmo Cosenza wrote:
> Hi Evan,
> Brenton Ashworth said that this kind of options should not be added to the
> compi
Hi Evan,
Brenton Ashworth said that this kind of options should not be added to the
compiler, but to the tools that use the compiler.
Could yowl please give me some advice from where to start patching
lein-cljsbuild following Brenton advice?
Thank so much
Mimmo
Here is Brenton comment on :ex
Yeah, I saw that. Very cool stuff! Glad you could contribute.
On Thursday, December 6, 2012 7:14:21 PM UTC-8, Mimmo Cosenza wrote:
>
> Hi Evan,
> just to let you that I submitted on clojurescript repo the patch to
> exclude a file and/or a directory of cljs from compilation.
>
> the new compil
Hi Evan,
just to let you that I submitted on clojurescript repo the patch to exclude a
file and/or a directory of cljs from compilation.
the new compiler option is :exclude and accepts both a name of a file or
directory o a vector of files and/or directories.
Hope it helps
mimmo
On Nov 16
On Friday, November 16, 2012 8:28:18 AM UTC+1, Evan Mezeske wrote:
>
> If you wouldn't mind, please create a new issue, or maybe just add to this
> one: https://github.com/emezeske/lein-cljsbuild/issues/108 .
>
done. added issue #157 with reference to #108 and viceversa.
thanks
mimmo
>
> Th
On Nov 16, 2012, at 8:28 AM, Evan Mezeske wrote:
>
> Unfortunately, there's no way to do that right now. I can't even think of a
> decent workaround (although that doesn't mean there isn't one).
>
Hi Evan and thanx for the answer
> This is part of a more general problem, which is that each
Hi Mimmo,
Unfortunately, there's no way to do that right now. I can't even think of
a decent workaround (although that doesn't mean there isn't one).
This is part of a more general problem, which is that each build can only
have a single :source-path and is not otherwise customizable. If you
Hi all,
my question is the following:
- I like to have the usual brepl connect to the browser during development
- I like to have the same source-base (e.g. :source-path "src/cljs") for both
the development and production builds (e.g. :builds {:prod {.} {:dev
{.} of :cljsbuild keyword)
