cuneiform team mailing list archive

["Jussi Pakkanen" <jpakkane@xxxxxxxxx>]

On Tue, Oct 28, 2008 at 2:53 PM, Ladwig, Mike <mike.ladwig@xxxxxxx> wrote:

> I have cuneiform working correctly under windows.  Here is what I did, hopefully without forgetting anything important.

Thanks for your work. I'll look into integrating this as soon as
possible. Once the MinGW version is working and merged to mainline
I'll do a new release.

Some comments on your steps.

> 8. Update derived makefile: In cuneiform/builddir/cuneiform_src/Kern/CMakeFiles/cuneiform.dir/build.make find "-lMagick++" and add after it "-lMagickCore -lMagickWand".  This is because cuneiform cmake is only picking up the Magick++.pc and not the two other required ImageMagick libraries.

This is a bug in either MinGW's pkg-conf or ImageMagick. On my OS X
machine, pkg-config --libs Magick++ gives

-L/opt/local/lib -lMagick++ -lMagickCore

Editing the makefiles by hand is dangerous, because CMake overwrites
them whenever build configuration changes. Additional libraries should
be added using CMake gui. Additions made there are persistent.

> 9. Apply the patch at the end of this email.  The util_spl.cpp change is to read the intermediate file in binary mode so as to prevent the automatic newline behaviors from occuring, and the rling_ma.c change is to take advantage of the automatic newline conversion behavior.

Ah yes, the infamous fread_m wrapper wrappers. The only reason I did
not get rid of them is that I don't know whether Visual Studio
supports fread/fopen/etc functions directly and properly
(Unfortunately Windows C is usually extremely standards-noncompliant.)
Can someone tell if this is the case?

The latter patch might better be fixed by changing the definition of
constant ch. It should probably be '\n' on MSVC and MinGW and '\r'
everywhere else. I'll have to check.