> Right, but if the crossover namespace for my library is defined in its
project.clj, and I'm importing that library as a dependency into another
project, it's sort of redundant to repeat information already specified. I
guess what I hoped for was that crossover namespaces would automatically be
^ To be clear, that's in the project dependent upon the library, where I'm
trying to use it, not the library itself.
On Thursday, 28 March 2013 02:03:38 UTC, Matthew Hill wrote:
>
> Hi Evan. Thanks for the response.
>
> The ClojureScript compiler looks for *.cljs files to compile as
>> ClojureSc
Hi Evan. Thanks for the response.
The ClojureScript compiler looks for *.cljs files to compile as
> ClojureScript. Hence, at a minimum, the *.clj files that you want to also
> use from ClojureScript need to be copied (or perhaps symlinked, but that's
> not what lein-cljsbuild does) to *.cljs f
>
>
> My question is, is this necessary? If it's on the classpath, why must I
> specifically tell it what namespaces I'm going to use? [...]
>
The ClojureScript compiler looks for *.cljs files to compile as
ClojureScript. Hence, at a minimum, the *.clj files that you want to also
use from Clo
Hello, I'm working on a library that works with both Clojure and
ClojureScript.
Here's the project.clj for the library:
(defproject libtest "0.1.0-SNAPSHOT"
:description "FIXME: write description"
:url "http://example.com/FIXME";
:license {:name "Eclipse Public License"
:url "h
