On 2010-11-28 12:22 +0100, Thomas Dickey wrote:
> On Sun, 28 Nov 2010, Sven Joachim wrote:
>
>> On 2010-11-21 12:52 +0100, Thomas Dickey wrote:
>>
>>> On Sun, 21 Nov 2010, Sven Joachim wrote:
>>>
>>>> On 2010-11-20 23:13 +0100, Thomas Dickey wrote:
>>>>
>>>>> On Fri, Nov 19, 2010 at 06:23:03PM +0100, Sven Joachim wrote:
>>>>>>
>>>>>> Actually rpath is not a problem when running test/configure, but I could
>>>>>> not get it to use the just compiled-but-not-yet-installed ncurses
>>>>>> library. Because it is built out of tree, the libs are not adjacent to
>>>>>> the headers which is expected by the "--with-curses-dir" configure
>>>>>> option.
>>>>>>
>>>>>> It would be good if this could be made to work, because the simplistic
>>>>>> solution of just copying everything from obj/test has the drawback that
>>>>>> cruft files like "Makefile" creep into the binary package. And we can
>>>>>> only run "make install" in the test directory if we had run
>>>>>> test/configure before, see the recent discussion on bug-ncurses.
>>>>>
>>>>> I've just implemented the latter, for today.
>>>>
>>>> Thanks, this seems to work. However, I just discovered the next missing
>>>> piece in the puzzle -- the tests themselves fail to build out of tree:
>>>
>>> sorry - I keep overlooking that aspect (most of my builds are in-tree,
>>> just because they're simpler to manage). Will fix...
>>
>> Was the VPATH change to test/Makefile.in you made yesterday supposed to
>> fix the problem? It does not seem to help.
>
> I tested it with a couple of configurations (which worked):
>
> a) a subdirectory of "test"
> This was a case that needed VPATH.
>
> b) a completely different tree (for the whole ncurses tree).
>
> c) an in-build-tree copy from the result of make_tar.sh
> That reminded me about term_entry.h, fixed as well.
>
> I didn't do an out-of-build-tree build for (c).
Alas, this is exactly what I want to do (not necessarily running
make_tar.sh before, though), and it does not work. :-(
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
