I added a link here http://clojure.org/clojureclr to the binary download wiki page. I'm happy to update this page in whatever way people find useful - feel free to ping me on email David, Frank, or others.
On Monday, November 25, 2013 12:48:51 PM UTC-6, Frank Hale wrote: > > Are there any plans to directly link the CLR downloads on the Clojure > downloads page on Clojure.org? I think it may be helpful to do that because > it's a bit difficult to get to the SourceForge download site by first going > to Clojure.org. The link on Clojure.org takes you to the Github repo, there > you have to click on a link to get to the binary downloads and then you > have to scroll through to find the SourceForge link. > > > > > > > On Mon, Nov 25, 2013 at 1:38 PM, Frank Hale <fran...@gmail.com<javascript:> > > wrote: > >> Thanks David for this information, I really appreciate the work you (and >> others) are doing on the CLR version. >> >> >> On Sun, Nov 24, 2013 at 7:56 AM, Shantanu Kumar >> <kumar.s...@gmail.com<javascript:> >> > wrote: >> >>> I am trying to run some tests (that worked fine with Mono+ClojureCLR >>> 1.4.1) in Mono+ClojureCLR 1.5.0 from SourceForge and finding the below >>> exception: >>> >>> $ # CLOJURE_LOAD_PATH is configured properly >>> $ mono "/path/to/clojure-clr-1.5.0-Release-4.0/Clojure.Main.exe" -i >>> /tmp/intermediate-file -e "(use 'clojure.test) (run-tests >>> 'sqlrat.template-test 'sqlrat.entity-test)" >>> >>> FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An >>> exception was thrown by the type initializer for Clojure.CljMain ---> >>> System.TypeInitializationException: An exception was thrown by the type >>> initializer for clojure.lang.RT ---> >>> clojure.lang.Compiler+AssemblyInitializationException: Cannot find >>> initializer for clojure.core.clj, Version=0.0.0.0, Culture=neutral, >>> PublicKeyToken=null.clojure/core >>> at clojure.lang.Compiler.InitAssembly (System.Reflection.Assembly >>> assy, System.String relativePath) [0x00000] in <filename unknown>:0 >>> at clojure.lang.Compiler.LoadAssembly (System.IO.FileInfo assyInfo, >>> System.String relativePath) [0x00000] in <filename unknown>:0 >>> at clojure.lang.RT.load (System.String relativePath, Boolean >>> failIfNotFound) [0x00000] in <filename unknown>:0 >>> at clojure.lang.RT.load (System.String relativePath) [0x00000] in >>> <filename unknown>:0 >>> at clojure.lang.RT.DoInit () [0x00000] in <filename unknown>:0 >>> at clojure.lang.RT..cctor () [0x00000] in <filename unknown>:0 >>> --- End of inner exception stack trace --- >>> at Clojure.CljMain..cctor () [0x00000] in <filename unknown>:0 >>> --- End of inner exception stack trace --- >>> >>> Can you give any pointer where should I probe? >>> >>> Shantanu >>> >>> >>> On Sunday, 24 November 2013 04:59:56 UTC+5:30, dmiller wrote: >>>> >>>> 1.5.0 of Clojure CLR includes the one fix in 1.5.1. I got excited and >>>> went one too far. Normally, the version numbers match exactly. >>>> >>>> I tagged 1.5.0 a little prematurely. We had some troubles on the NuGet >>>> release and on the mono build. I wasn't really ready for an official >>>> 1.5.0 >>>> release, so I hadn't done the SourceForge binary distributions. >>>> >>>> That's all been fixed as of earlier today (11/23/2013 relative to >>>> Central Standard). >>>> >>>> ClojureCLR 1.5.0 is officially out. >>>> >>>> This version has a NuGet package, with binaries for .Net 3.5 and .Net >>>> 4.0. All the binaries to run ClojureCLR itself are in one file, >>>> Clojure.dll, due to the magic of ILMerge and a lot of new internal >>>> plumbing >>>> to allow embedded DLL resources and merged DLLs. Also, this version is >>>> signed so that it can be referenced in signed projects or GAC'd. >>>> >>>> There are Debug and Release binaries (not ILMerged) for .Net 3.5 and >>>> 4.0 on the SourceForge site. >>>> >>>> The wiki pages on the github site have been updated. >>>> >>>> Mono is now supported. You can run it under Mono. You can compile it >>>> directly using xbuild with mono. Details on the wiki. >>>> >>>> Regarding the Clojure.Main and Clojure.Compile binaries in the NuGet >>>> package: Yes, you have to move them to run them. Clojure.dll has to be >>>> in >>>> the lib\ folder in order for the package to work properly when included in >>>> a project. Ancillary files such as Clojure.Main and Clojure.Compile are >>>> standalones and are not needed for other projects. They are properly >>>> contained in the tools\ folder. I was asked to include them in the NuGet >>>> package for ClojureCLR. I'm not happy with the current arrangement, in a >>>> nitpicky way. I'm open to suggestions. >>>> >>>> -David >>>> >>>> >>>> >>>> On Friday, November 22, 2013 8:41:58 PM UTC-6, Frank Hale wrote: >>>>> >>>>> As far as I can tell the Clojure CLR version number does not track the >>>>> JVM version number at least for some builds. The latest build 1.5.0 as >>>>> far >>>>> as I can tell is at the same patch level as 1.5.1 on the JVM. This >>>>> numbering seems confusing to me. Are there any plans to streamline the >>>>> version numbers between the two platforms? >>>>> >>>>> Additionally I don't understand why on the Clojure CLR SourceForge >>>>> page there are only debug versions available for download and 1.5.0 is >>>>> not >>>>> represented there. If you want 1.5.0 you have to use nuget to get it. I >>>>> was >>>>> also a bit dumbfounded that the nuget version was broken out of the box >>>>> and >>>>> what I mean by that is that once you have downloaded it you cannot run >>>>> the >>>>> compiler or the REPL from it's current directory without first dumping >>>>> the >>>>> exe's into the lib folder since they are segregated in the package. >>>>> Running >>>>> the compiler or REPL from their directory will result in them complaining >>>>> that they cannot find the required Clojure CLR DLL's that they need. >>>>> >>>>> These are kind of nit-picky issues but they've been bugging me for a >>>>> while. >>>>> >>>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@googlegroups.com<javascript:> >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+u...@googlegroups.com <javascript:> >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+u...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
