On 03/20/2013 04:31 PM, Alexander Neundorf wrote:
The keywords won't interact well with PUBLIC/PRIVATE/INTERFACE keywords.
Let's assume there would be only PRIVATE, INTERFACE_BUILD and
INTERFACE_INSTALL.
I'll use PRIVATE for building the target.
I'll add INTERFACE_BUILD if I want to make
On Thursday 21 March 2013, Brad King wrote:
On 03/20/2013 04:31 PM, Alexander Neundorf wrote:
...
So e.g. I could do
tid(hello
PRIVATE ${Foo_INCLUDE_DIRS} ${Bar_INCLUDE_DIRS}
${CMAKE_SOURCE_DIR}/blub INTERFACE_BUILD ${CMAKE_SOURCE_DIR}/blub
${Bar_INCLUDE_DIRS}
On 03/21/2013 02:47 PM, Alexander Neundorf wrote:
Still, is the PUBLIC part necessary ?
IMO PRIVATE and INTERFACE suffice, and for me it seems more straighforward to
separate only between these two.
PRIVATE and INTERFACE are sufficient but need to be duplicated
to produce the equivalent of
On Tuesday 19 March 2013, Stephen Kelly wrote:
Alexander Neundorf wrote:
which automatically adds
$BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR};
${CMAKE_CURRENT_SOURCE_DIR}
to the INTERFACE_INCLUDE_DIRECTORIES of each target.
Since cmake 2.4.0. the global cmake variable
On 03/19/2013 04:02 PM, Alexander Neundorf wrote:
On Tuesday 19 March 2013, Stephen Kelly wrote:
I don't mind renaming it, but it's a topic for the cmake list.
So, I think the variable name CMAKE_BUILD_INTERFACE_INCLUDES is to general.
Since it is similar to the effect of
Alexander Neundorf wrote:
What I actually propose would look something like
install(TARGETS KArchive EXPORT KArchiveTargets NAMESPACE KF5::
...
INCLUDES DESTINATION $INSTALL_PREFIX/${INCLUDES_INSTALL_DIR}
)
so it could be folded into INSTALL_TARGETS_DEFAULT_ARGS. I don't know if
