Hi everyone,
I want to build PLplot on Linux in such a way that all the components (drivers
and supporting libraries like nn and csa) are retrieved via the LD_LIBRARY_PATH
variable. The path must not be hard-coded. What CMake do we have for that?
Regards,
Arjen
DISCLAIMER: This messag
On 2015-02-20 12:40- Arjen Markus wrote:
> I want to build PLplot on Linux in such a way that all the
components (drivers and supporting libraries like nn and csa) are
retrieved via the LD_LIBRARY_PATH variable. The path must not be
hard-coded. What CMake do we have for that?
Use the cmake co
Hi Alan,
Ah, I overlooked that option. Thanks, I will give that a try.
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Friday, February 20, 2015 7:08 PM
> To: Arjen Markus
> Cc: plplot-devel@lists.sourceforge.net
> Subject: Re: [Plplot-devel] Conf
I've gone through the coordinate transformation and where/how it is applied in
the library. The coordinates that are stored in the plot buffer can be best
described as "device virtual pixels" and the definition is not necessarily
consistent across all the devices. I don't think that is a show s
On 2015-02-20 18:24- Arjen Markus wrote:
>> From the point of view of someone who needs to supply programs and
libraries to customers (both inside and outside the organisation), it
seems much more convenient to have LD_LIBRARY_PATH take priority.
Yes. That is exactly why all the Linux packag
On 2015-02-20 14:32-0500 Jim Dishaw wrote:
> I've gone through the coordinate transformation and where/how it is applied
> in the library. The coordinates that are stored in the plot buffer can be
> best described as "device virtual pixels" and the definition is not
> necessarily consistent ac
On Feb 20, 2015, at 4:13 PM, "Alan W. Irwin" wrote:
> On 2015-02-20 14:32-0500 Jim Dishaw wrote:
>
>
> Hi Jim:
>
> I have read and re-read Solutions 1 and 2 and I don't see any
> difference between how you have presented them. Did you mean to say
> something else for one of them or am I miss
I've made some updates to the test_diff.sh script so you can now call it
with the --device= option to specify a device other than psc you want to
compare. I've not (yet) incorporated all this more generalised logic in
the cmake tests, but you can run it in the examples directory. I've done
this
