On 05/06/11 15:56, Stuart Henderson wrote:
Christopher Zimmermann<madroach<at> zakweb.de> writes:this is a port of pdftk, a very handy pdf utility. It's looking for someone to commit it to the ports tree.a few things need fixing first;
>
- should use MODULES for gcc4 and iconv (borrow parts from lang/classpath)
done, but does not completely work as I would wish it did.
- Makefile.OpenBSD should be in files/ not pkg/
done
- don't hardcode paths in Makefile.OpenBSD, set them via variables in the port's Makefile.
done. builds without path to LIBGCJ as well.
the gcc4 MODULE takes care of adding symlinks where required so you don't need to force the compiler names. as-is this doesn't work on gcc4 arch unless you have the C++ compiler from the gcc4.2 package installed. using the symlinks provided by the module, you can use default names for the compilers, which should fix this.
I don't really understand how this is supposed to work. Is there any more documentation on this than just port-modules(5) ?
Anyhow. I changed $(GCC) $(GCJ) from egcc resp. egcj to gcc resp. gcj. Only $(JAR) had to stay ejar, because there is no ejar, and $(CXX) needs to be eg++, because gcc 4.2.1 doesn't understand the syntax of pdftk.cc.
Is there a way to tell the gcc4 MODULE to use a specific version of gcc4?
- don't overwrite CXXFLAGS etc in Makefile.OpenBSD, add to them instead. you should be able to type 'make DEBUG="-O0 -g"' and have it honoured in the build.
done
- using the full path to libgcj is messy but if there's no way around that, at least use LOCALBASE rather than /usr/local.
done
- if "Split PDF Pages into a New Document" is the same thing as "Burst a PDF Document into Single Pages" then remove one or other from DESCR. maybe drop/merge a few other lines for the sake of brevity?
done
pdftk.tgz
Description: Binary data
