Re: Writing PDF files

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Tue, 18 Oct 2011 13:24:13 +0200, Simon Wright <simon@pushface.org> a  
écrit:
> I don't see those words in COPYING.LIB version 2 as distributed with
> plplot (and I thought you don't hold with Wikipedia???!).
Please, what means “to get hold with” in that context ?

> However, the plplot bindings have no generics, so may be OK. But I think
> that for statically-linked proprietary executables using plplot you
> would have to supply at least object code for your proprietary
> application so that the user could relink with a newer version of
> plplot.
>
> Sounds fraught with difficulty.
I read it twice, and understood you are are required to allow reverse  
engineering if ever you statically link to an LGPL stuff. So to feel at  
rest, the best is to use dynamic linking only. On Windows, that's easy,  
just put a DLL into the directory where the binary application reside  
(application's directory is the first place where Windows application  
loader will look to solve DLL dependencies). May seems more difficult on  
Unicies without installing a library system wide, except that may not be  
so much difficult: for Linux and derivatives, use a tiny utility which is  
named “patchelf”, to write an rpath entry in your ELF executable. I did  
not check if relative paths are OK here of only absolute paths make sense,  
but at least, this allow you to dynamically link an application to an  
exact library, without system wide installation (if relative paths are not  
OK for an rpath, then do it from an installer). For MacOS, I can't tell, I  
don't own and don't have access to any.

This PlPlot seems interesting (support a wide range of output among the  
most interesting ones), will have a look at it a later time.

-- 
“Syntactic sugar causes cancer of the semi-colons.”  [Epigrams on  
Programming — Alan J. — P. Yale University]
“Structured Programming supports the law of the excluded muddle.” [Idem]
Java: Write once, Never revisit