[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    Re: [kde-edu]: KTouch : build and install issues
From:       "Andreas Nicolai" <Andreas.Nicolai () gmx ! net>
Date:       2005-06-26 15:55:14
Message-ID: opssziicapt8lo91 () smtp ! kuleuven ! ac ! be
[Download RAW message or body]

Hi Albert,

ok, that sort of explains and solves my issues. I thought there is some easy way to \
configure a program in a module to look for a dependent program/lib in the same \
module first. Basically something like: when KTouch is built, "make install" first in \
libkdeedu module and only if that is successful, built KTouch.

But if that is not possible, I agree that using relative filenames for headers and \
libs (as you changed it now) is better.

Still two questions remain:
1. how can we ensure that libkdeedu is compiled first when I just build a single \
program like KTouch and not all of KDEEDU? 2. are we still going to install headers \
and libs of libkdeedu so that other modules can use our lib?

Andreas
_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu


[prev in list] [next in list] [prev in thread] [next in thread]