By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 599 - kdepim 3.5.13 cmake files incorrectly install header files into the incorrect location
Summary: kdepim 3.5.13 cmake files incorrectly install header files into the incorrect...
Status: RESOLVED DUPLICATE of bug 600
Alias: None
Product: TDE
Classification: Unclassified
Component: tdepim (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: Other Other
: P1 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-11-08 17:12 CST by Darrell
Modified: 2012-10-19 15:57 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
kludge patch to install to correct location (11.42 KB, patch)
2011-11-22 17:36 CST, Darrell 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2011-11-08 17:12:36 CST 
Building kdepim results in most of the header files being installed in $PREFIX/include/kde rather than $PREFIX/include. KDE 3.5.10 never had that subdirectory. Placing the header files in the kde subdirectory prevents other packages from building correctly, such as kipi-plugins.

A clunky patch was used to fix the cmake files before building:

http://humanreadable.nfshost.com/trinity/patches/kdepim/include-dirs.patch

The best repair is to fix the cmake files to install the header files in the correct location.
Comment 1 Darrell 2011-11-22 17:36:44 CST 
Created attachment 151 [details]
kludge patch to install to correct location
Comment 2 Darrell 2011-11-27 11:29:26 CST 
Bug reports 599 and 600 address the incorrect installation of header files, which causes dependent packages to fail to build.

Rather than trying to discover which packages are affected, in my build scripts I now run the following inline patch to all cmake files after uncompressing the sources to my build directory:

find $APP_SOURCES_DIR -name CMakeLists.txt -exec sed -i s'|DESTINATION \${INCLUDE_INSTALL_DIR}/kde |DESTINATION \${INCLUDE_INSTALL_DIR} |g' {} \;

Applying this one-time search patch to the entire SVN/GIT tree would repair all affected CMakeLists.txt files and avoid the problem of dependent packages failing to build correctly. No additional patching would be required by packagers.
Comment 3 Timothy Pearson 2012-01-15 17:48:46 CST 
Marking this as a duplicate of Bug 600, as both cover the same philosophical ground.

*** This bug has been marked as a duplicate of bug 600 ***