It seems I need to create an account to add to the Wiki
(understandable)... I'll look into this when I have the time, but if
anyone else already has editing privilidges, feel free add any
relevant info from below yourself.
On 3/28/07, inkscape-user-request@...
> Message: 4
> Date: Mon, 26 Mar 2007 12:17:17 -0700
> From: Bryce Harrington <bryce@...>
> Subject: Re: [Inkscape-user] for posterity: inkscape export in
> To: Inkscape User Community <inkscape-user@...>
> Message-ID: <20070326191717.GY6836@...>
> Content-Type: text/plain; charset=us-ascii
> Hi Maciej,
> This is good info, thanks for posting it. Can you also post it onto the
> Inkscape Wiki, where others will be able to find it? I think there's a
> page for Windows off of the CompilingInkscape page.
> On Mon, Mar 26, 2007 at 11:51:12AM -0400, Maciej Kalisiak wrote:
> > Now that I got everything sorted out (thanks to all who replied!), I
> > figure I might as well post to the list how I automated Inkscape SVG
> > exporting under Windows+cygwin, perhaps it will save someone else some
> > time in the future. I use GNU "make" to build my documents, and here
> > are the relevant bits of the Makefile:
> > ------
> > INKSCAPE=d:/portable_apps/inkscape/inkscape.exe
> > SRCDIR=$(shell cygpath -d -m `pwd`)
> > %.pdf: %.svg
> > $(INKSCAPE) -f $(SRCDIR)/$< -A $(SRCDIR)/$@
> > # list of PDFs to build from SVGs:
> > all: foo.pdf bar.pdf baz.pdf
> > ------
> > The first stumbling block was that inkscape requires full paths to the
> > original file and the destination file. The second stumbling block
> > was how to translate them for inkscape, which does not like cygwin's
> > /cygdrive/c/... notation.
> > The above is not optimal, so if anybody spots better ways to go about
> > things, let me know. I just have to figure out how to avoid
> > hardcoding the path to inkscape, which is in different directories on
> > my various machines...
mac [at] dgp.toronto.edu