Re: [Plplot-devel] "make check" support installed for c++, f77, and tk examples

[Alan W. I. <ir...@be...>]

On Mon, 9 Dec 2002, [iso-8859-1] Jo=E3o Cardoso wrote:

> To make things clear: I just want to avoid the need to do a "make
> install".

> [...]The problem is not how to generate libraries, but how/where will the
> mother app (tcl or python) find them.
> Anyhow, if you say that you will be able to run the tcl and python
> examples *without* a "make install", then I will be happy. But in the
> original post you said:
>
>     "The python examples assume an installed location for the
>      wrapper library, and the tcl and tk examples are even more
>      dependent on installed data."
>
> Again, I think that there is no problem for now if only data needs to be
> installed. With "data" I *don't* mean the drivers. And yes, now I see,
> the drivers are a good example to discuss this issue, because the
> drivers are a kind of "extension modules" of plplot.
>
> How do you intend to load the drivers without a "make install"? In the
> installed directory, you can find a driver,
>     /usr/local/test/lib/plplot5.1.0/drivers/xwin_drv.so
>
> but in the build directory you only found
>    drivers/xwin_drv.la
>    drivers/xwin_drv_la-xwin.lo
>    drivers/xwin_drv_la-xwin.o -> xwin_drv_la-xwin.lo
>
> the real driver is in
>    drivers/.libs/xwin_drv.la@
>    drivers/.libs/xwin_drv.so*
>    drivers/.libs/xwin_drv.lai
>    drivers/.libs/xwin_drv.soT*
>
> When the plplot library wants to load a driver, what will it look for?
> xwin_drv.so, right? Or is that changed? That object can only be found at
> the installed directoy or hidden in drivers/.libs.
> [...]

We have complete control of where to find the drivers.  Look in plcore.c
at

        sprintf( drvspec, "%s/%s/%s",
=09 DATA_DIR, "../drivers", driver->drvnam );

Another stanza would have to be put in there to look in an alternative
location.  Also look elsewhere in src/*.c for DATA_DIR to find out
all locations that are affected.

I am not so familiar with the tcl part, but I believe in that case the
plplot initialization scripts define where the dynloaded shared objects are
so it is those scripts that would have to be modified if you want this no
"make install" capability.  Similar remarks pertain to the location
of the plplot tcl initialization scripts as well.

For python, the location of the plplotc module is in
examples/python/plplot_python_start.py(.in).  So we have complete control o=
f
specifying the module location in that case as well.

So to sum this up, with some work this should all be doable, but there are =
a
a fair number of places in the code and scripts that are affected so I woul=
d
still like to put this (the "no make install" option for lack of a better
description) under firm control of a configuration option.

Alan