Simon,
>> Now, pdf2 does not use "manually created config.h",
>
> I was referring to R - there is no configure step in the Windows build so
> config.h is created "manually" (or semi-automatically if you wish) and then
> shipped with R in a special location.
I misunderstand what you meant. I found
On Jul 2, 2008, at 6:41 AM, Tadashi Kadowaki wrote:
Simon,
Now, pdf2 does not use "manually created config.h",
I was referring to R - there is no configure step in the Windows build
so config.h is created "manually" (or semi-automatically if you wish)
and then shipped with R in a special
Simon,
Now, pdf2 does not use "manually created config.h", but create own
config.h by itself.
The package also does not refer internal headers installed with R.
However, the package
needs internal headers, because original pdf device code needs them.
Therefore, It has
local copies of the headers.
Tobias,
that package uses headers internal to R (a really bad thing to do).
Although it attempts to supply them (very dangerous again since they
are R-version-dependent) they rely on configured R sources which are
not present on Windows. I don't have a Windows machine handy, but I
dimly r
Dear list,
Tadashi Kadowaki has developed a pdf device package
that allows to add hyperlinks and popups
to (currently) text, mtext and rect calls.
The package passes R CMD check (minor warnings) and compiles
on MacOS X and GNU/Linux, but we do not succeed in building
the package for Windows.
The
