On Mon, Sep 23, 2002, Fringe Ryder wrote:
> not providing docs on what is required in the form of support
> libraries, headers, and tools.
Hmm, from the REQUIREMENTS and README files,
netpbm 9.15 or later
jpeg header/libraries
python
prc-tools (i.e. m68k-palmos-gcc etc.)
PalmOS4 SDK
pilrc (v2.8 or later)
ZLib (1.1.3 source package)
GNU Make
GNU sed
GCC
autoconf (requires perl)
LaTeX
Latex2HTML (requires perl and a few other tools)
wxWindows 2.3.3 (odd minor number indicating dev version, more
info available in plucker_desktop/BUILDING.txt)
However, you don't *need* all these packages unless you are going to
work on all parts of Plucker. Neither do you need autoconf (and perl)
unless you get the code direct from cvs and have to create a configure
script from the configure.in file (neither do we tell you that you
need tools to access cvs or a text editor to edit some of the files;
some things we expect developers to figure out by themselves:)
The viewer's Makefile uses some common unix tools, but its README also
tells you that "other platforms would probably require some changes to
the Makefile and scripts."
NOTE: any stuff that a package may require is not a Plucker problem,
e.g. if we tell you that you need Latex2HTML to convert the docs into
HTML it goes without saying that you need whatever tools Latex2HTML
requires to work.
> No, it's the large quantity of dependencies that you aren't noticing
> because you've got them set up.
And if you open your eyes you will find that most (if not all) of
them are documented, too. Please tell us more about this *large*
quantity of (undocumented) dependencies.
> but yesterday (my second day of Plucker, third of Palm)
Maybe that should tell something about not being so quick to pass
judgements about this project.
/Mike
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
