From: "Claudio Bley" <bley@cs.uni-magdeburg.de>
To: Sawa <sawa@cse.iitb.ac.in>
Cc: gcc-help@gcc.gnu.org
Subject: Re: image magic compilation errorrs
Date: Wed, 23 Oct 2002 07:46:00 -0000 [thread overview]
Message-ID: <15798.46707.713817.181679@wh2-19.st.uni-magdeburg.de> (raw)
In-Reply-To: <Pine.HPX.4.21.0210231910200.9770-100000@voxel.cse.iitb.ac.in>
>>>>> "Sawa" == Sawa <sawa@cse.iitb.ac.in> writes:
Sawa> bash-2.05b$ c++ -o test test.cpp `Magick++-config -cxxflags
Sawa> -cppflags -ldflags -libs` Usage: Magick++-config
Sawa> [--cppflags] [--cxxflags] [--exec-prefix] [--ldflags]
Sawa> [--libs] [--prefix] [--version]
Sawa> For example, "example.cpp" may be compiled to produce
Sawa> "example" as follows:
Sawa> "c++ -o example example.cpp `Magick++-config --cppflags
Sawa> --cxxflags --ldflags --libs`"
Why don't you just follow the advice given in the line above???
There need to be 2 dashes in front of cppflags, cxxflags, libs and
ldflags options to the Magick++-config script.
bash-2.05b $ Magick++-config --cppflags --cxxflags --ldflags --libs
-DHAVE_CONFIG_H -I/usr/include/freetype2 -I/usr/include/freetype2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -I/usr/X11R6/include/X11/magick -I/usr/X11R6/include -I/usr/X11R6/include/X11
-O2 -march=i686
-L/usr/lib -L/usr/X11R6/lib -L/usr/X11R6/lib
-lMagick++ -lMagick -L/usr/X11R6/lib -lMagick -ltiff -lfreetype -ljpeg -lpng -ldpstk -ldps -lXext -lXt -lSM -lICE -lX11 -lbz2 -lz -lpthread -lm
--
Claudio Bley ASCII ribbon campaign (")
Debian GNU/Linux advocate - against HTML email X
http://www.cs.uni-magdeburg.de/~bley/ & vCards / \
next prev parent reply other threads:[~2002-10-23 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 6:39 Sawa
2002-10-23 7:46 ` Claudio Bley [this message]
2002-10-23 8:28 ` Sawa
2002-10-23 16:26 ` Claudio Bley
2002-10-24 8:34 ` Sawa
2002-10-28 5:18 ` Claudio Bley
2002-10-28 22:50 ` Abhineet Sawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15798.46707.713817.181679@wh2-19.st.uni-magdeburg.de \
--to=bley@cs.uni-magdeburg.de \
--cc=gcc-help@gcc.gnu.org \
--cc=sawa@cse.iitb.ac.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).