Building ImageMagick on Cygwin
Hello,
Heads up. Some persons reading this List might want to know
this information.
ImageMagick is not yet available as a binary
Cygwin package. I have no way of knowing what the likelihood is of it
becoming such a supported Cygwin package at any time in the future.
Thus for now building ImageMagick from source is the way to get it on
one's Cygwin system And after all, to me, is an example of one of the fun
reasons to have Cygwin in the first place.
If one does things in a
fairly standard plain manner: i.e. you don't have some stuff already
prepared or adapted but you just go and get the latest I~M~ source
package and unpack it and try to run `configure', you're going to have
trouble with a couple of libraries which you might want to build I~M~
with: libpng (latest version, all older installations cleanly and
completely removed please) and Freetype2. The Gnu autotools-
generated configure script isn't going to work on detecting those
libraries. Don't take my word for it: to the letter of my brief
description, try it for yourself.
About Freetype2: because it's
a package (on Cygwin) "owned" by the XFree86-Cygwin folks, it isn't
installed in the usual place (such as a lib like jpeglib: /usr/include
for its headers and /lib for the library [and /bin for the dll of
course]). Because of strategies by the Freetype folk, it isn't
directly in a X header path either: its in a subdir ("freetype2") of
XFree86/include. You either need to know this when you run configure,
or you need to get a fixed configure script.
I've got a fixed
configure script. I've also got a bellyfull of discussing this with
arrogant and recalcitrant individuals on other Lists and so I won't
answer any inquiries here concerning this posting. I am posting
merely as a public service for those who might stumble on this problem
in the future, and to invite those who are not so steeped in some
ideological "Gnu can do no wrong" brainwashed state that they might be
interested in sharing my work or collaborating, without the purile
lectures and misguided, deaf cluelessness, thanks, to contact
me.
Soren Andersen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Building ImageMagick on Cygwin
The URL I promised (as the o.p. who started this thread): http://home.att.net/~perlspinr/IM_build.html That page will give some background information, as well as I am able at this time. Hope it helps those who might want the help. I am sure that many readers of this List don't want my "help" but fortunately -- blessedly -- we live in a time of relative freedom of expression, so I can still offer what I know even if it falls on a lot of deaf ears. Thanks for reading, Soren Andersen -- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated: pkgconfig-0.12.0-1
Hello Charles, I'll just mention, since I've been thinking a lot about pkg-config lately, that I wondered whether the buggy m4 macro code that makes it work (theoretically) with autoconf, has been fixed. I'll download the source along with the updated package and look for a changelog or something. But in case I run out of time: the primary thing I am referring is that the shell code written out to a `configure' file due to the inclusion of the macro call PKG_CHECK_MODULES(LIBPNG, libpng10 >= 1.0.13, [blah blah]) is VERY odd stuff, even for `configure'. The shell script code looks like this (this is one *section* of a huge file, NOT meant to be clear, complete, stand-alone, or anything else, and *I* basically didn't write it but rather it was written by "autoconf" -- so if you see something you don't like then before you sound off about my bad shell scripting style, please get it STRAIGHT about what this IS and where it comes from and why I am bringing it up!) watch for miswrapping case $PKG_CONFIG in [\\/]* | ?:[\\/]*) ac_cv_path_PKG_CONFIG="$PKG_CONFIG" # Let the user override the test with a path. ;; *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH do test -z "$as_dir" && as_dir=. if ! test -d $as_dir; then continue 1; fi for ac_exec_ext in '' $ac_executable_extensions; do if eval $as_executable_p "$as_dir/ $ac_word$ac_exec_ext"; then ac_cv_path_PKG_CONFIG="$as_dir/ $ac_word$ac_exec_ext" echo "$as_me:$LINENO: found $as_dir/ $ac_word$ac_exec_ext" >&5 break 2 fi done done IFS=$as_save_IFS test -z "$ac_cv_path_PKG_CONFIG" && ac_cv_path_PKG_CONFIG="no" ;; esac fi #RINGWALD PKG_CONFIG=$ac_cv_path_PKG_CONFIG end of shell code excerpt from `configure' === The part I mean to bring to your attention is this line: if eval $as_executable_p "$as_dir/ $ac_word$ac_exec_ext"; then The 'eval' is my modification because on my system at least (Cygwin running in Win98SE), that is a syntax error without the "eval". $as_executable_p resolves to "test -f" I believe and the shell sees as a single argument, not as a call to "test" followed by an argument flag "-f". All that above is just to detect whether pkg-config is installed on the system ,BTW. It seems very bizarre to me that this baroque code is invoked when a simple test for a non-zero return value from a shell call to `pkg- config --version >/dev/null' would do. I know I know, nobody understands what I am talking about ;-). Regards, Soren Andersen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwin BASH prompt a little weird?
Hello,
In Cygwin using this version of BASH, my attempts to get
a simple name of the shell interpreter into my prompt
(PS1) using escaped-s ('\s'), which should work accoding
to
http://www.linuxselfhelp.com/HOWTO/Bash-Prompt-
HOWTO/bash-prompt-escape-sequences.html
does not give the basename of of the shell but the
relative path by which I invoked bash: '/bin/bash'.
The HOWTO above states:
\s the name of the shell, the basename of $0
(the portion following the final slash)
Is Cygwin not compliant with this?
Thanks,
Soren Andersen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
