Saxon

Legacy ID: #8068764 Legacy Poster: Michael Kay (mhkay)

A tricky one, this. For Saxon 9.2, I did a special build of IKVM in order to reduce the size of the Classpath libraries (basically eliminating many classes that were not needed to support Saxon). I worked with 0.40.0.1 as my baseline, and called my revised version (perhaps a little naughtily) 0.40.0.2 to make sure it was distinguished. If I remember correctly, I also made a trivial change to IKVMC to add some tracing/diagnostics in support of this exercise; there were no changes to the IKVM runtime proper. Technically, therefore, there is absolutely no reason why Saxon should not work with 0.40.0.1, and it will almost certainly also work with 0.40.0.3. The question is how best to create a build that has the right dependencies. If you are only using Saxon-HE (open source) code, then I think the best I can suggest is that you master the build process and build the product yourself from source code. You will find Ant scripts to do this in the Subversion repository. If you cut out all the parts of the build that are concerned with Saxon on Java or with the PE and HE products, or with generation of documentation and sample applications, then it's not actually that complex. If you know your way around the .NET tools you could of course also try to find a way to modify the DLLs to change the dependencies. On the other hand if you're using Saxon-PE or Saxon-EE then I will have to do this for you, and I think I will have to make this a chargeable service.

Legacy ID: #8069743 Legacy Poster: Markus Schaber (schabi)

For our first experiments, the HE edition is enough. I'll see whether I get it built myself. Although I suggest that you publish a 0.42.0.3 based build as this is the currently supported ikvm release, and I suspect that there might have been important fixes between 0.42.0.2 and 0.42.0.3. Thanks for your help, Markus

Legacy ID: #8069784 Legacy Poster: Michael Kay (mhkay)

My general policy when doing Saxon maintenance builds is to make no change to the environment unless there are known problems that need fixing; when I do a development build I move forward to the version that appears to be most stable at the time.

Legacy ID: #8071595 Legacy Poster: Markus Schaber (schabi)

Ok, that seems a reasonable policy. And I guess that my problem qualifies not as "known problem that needs fixing". I'll try to compile Saxon for myself then (having some experience with ant and java in the past). Thanks for your patience and your good work!