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

List:       kdevelop-bugs
Subject:    [Bug 298859] New: [CMake 2.8.8] Support new target property INCLUDE_DIRECTORIES.
From:       <bungeman () gmail ! com>
Date:       2012-04-26 15:46:46
Message-ID: bug-298859-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=298859

            Bug ID: 298859
          Severity: normal
           Version: unspecified
          Priority: NOR
          Assignee: kdevelop-bugs@kdevelop.org
           Summary: [CMake 2.8.8] Support new target property
                    INCLUDE_DIRECTORIES.
    Classification: Unclassified
                OS: Linux
          Reporter: bungeman@gmail.com
          Hardware: Compiled Sources
            Status: UNCONFIRMED
         Component: Build tools: CMake
           Product: kdevelop

With CMake 2.8.8 released last week, it is now possible to write something like

set_property(TARGET zlib APPEND PROPERTY INCLUDE_DIRECTORIES
"${CMAKE_CURRENT_SOURCE_DIR}/../include/config")

This ability to have target specific includes has been a long time in coming,
and is finally here. KDevelop should support these includes as soon as
possible.

Reproducible: Always

Steps to Reproduce:
1. Create a 2.8.8 cmake project.
2. Put something like
set_property(TARGET zlib APPEND PROPERTY INCLUDE_DIRECTORIES
"${CMAKE_CURRENT_SOURCE_DIR}/../include/config")
in it.
3. Load the project in KDevelop.
Actual Results:  
KDevelop does not find the include file.

Expected Results:  
KDevelop does find the include file.

It appears that right now a relative path is interpreted relative to the cmake
build directory instead of the cmake source directory (which would make more
sense). This may or may not be a bug in CMake, so for the time being I'm
playing it safe and just using ${CMAKE_CURRENT_SOURCE_DIR} to get what I want
in the above example.

-- 
You are receiving this mail because:
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]