Le 19/08/2012 18:24, David C. Rankin a écrit :
> On 08/19/2012 02:26 AM, Francois Andriot wrote:
>> To avoid this, I hardcode the directory directly in the build process in
>> autotools-built packages. Something like:
>> sed -i admin/acinclude.m4.in -e
>> "s|kde_htmldir='.*'|kde_htmldir='/opt/trinity/share/doc/kde/HTML'|g"
>>
>> This is a just a workaround until we take a final decision.
>>
>> Francois
> Agreed,
>
>    At present, I just want the help system working. I can look at modifying my
> build scripts to get the application manuals in the right place.
>
>    Historically, I can see a reason you would want all core kde apps in:
>
> /opt/trinity/share/doc/kde/HTML/<language>
>
>    while wanting 3rd party apps somewhere else like:
>
> /opt/trinity/share/doc/HTML/<language>
>
>    But today, I just think that makes a mess out of things. To be consistent and
> provide seamless interoperability between R14 and 3513, it makes sense to just use:
>
> /opt/trinity/share/doc/HTML/<language>
>
>    My big question is where is this initially set? tdelibs sounds like it sets
> the base docpath that everything else must follow. So we have to get tdelibs
> set, then point everything else to the same place. Are there any other
> considerations there?
>

The default path is set in kdelibs in file:
   cmake/modules/TDESetupPaths.cmake
Look for variable HTML_INSTALL_DIR .

But you should also be able to specify a different path at build time 
for each package, for instance:
cmake -DHTML_INSTALL_DIR=/opt/trinity/share/doc/HTML

Francois