On 31 Jul 2006, at 11:55 , Ben Fowler wrote:
On 31/07/06, jiho <jo.irisson@...400...> wrote:
hi all,
[...]
I don't have cairo on my system yet so this is not surprising but ./ configure lets me go into making without warning for anything. If not having cairo breaks the build there should be a configure check or a switch (--with[out]-cairo).
I am stuck on this as well. I was (or perhaps still am) intending to install the 'package' that provides cairo-pdf.h,
cairo-pdf.h is the header of cairo-pdf.cpp which is a source file of inkscape. so you have it. The problem is elsewhere in fact.
There are three problems IMHO: 1. local cairo headers (#include "...) are included instead of system ones (#include <...). I can understand this is usefull when using a local patched cairo but the defautl in the SVN source should be system libraries i.e. replace #include "cairo.h" #include "cairo-pdf.h" #include "cairo-ft.h" by #include <cairo.h> #include <cairo-pdf.h> #include <cairo-ft.h>
2. the presence of cairo is not checked in configure and appropriate include flags are not added to the compilation command. To use system wide header I therefore have to add: export CPPFLAGS="-I$FINK/include -I$FINK/include/cairo/" on OS X. (understand -I/usr/include/cairo/ on linux but maybe this path is checked for headers by default)
3. l.64: of cairo-pdf.cpp #ifdef USE_PANGO_CAIRO #include <pango/pangocairo.h> #endif and USE_PANGO_CAIRO is never defined. where does this come from? Even if it is not defined, the build requires pangocairo.h. I don't have pangocairo.h on my system and have no idea in which package it is at the moment (I have pango and pango-dev installed though so it is not in the base version). So this is what is holding the build right now.
Thanks for any help.
so that I can get on, but this may be a bit tricky - the explanation is the same as the one on the page http://wiki.inkscape.org/wiki/index.php/NativeUIMacOsX - as the ability to provide the PDF backend is picked up automatically when configuring cairo.
Perhaps the short term solution is to wrap the problematic code in
#if FOR_THRILL_SEEKERS ... #endif
I agree that something in the configure script should select the back-end et cetera, but I am not sure what form this take. A fully automated test might be better than forcing the dev to fully understand what this is about.
Ben
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php? page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Jean-Olivier Irisson --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- Personal address: Château St Martin, 66200 Elne, France Professional address: EPHE- UMR CNRS 8046, 52 av Paul Alduy, 66860 Perpignan Cedex, France
Mobile: 06 21 05 19 90 Web site: http://jo.irisson.free.fr/work/