On 03/21/2013 04:47 PM, Alexander Neundorf wrote:
> At least for me it is also easier to differentiate between "use this when
> building foo" and "use this when using foo" vs. the three options.
Then don't use PUBLIC in your code.
Others have the opposite view. When something does need to be in
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 o
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
On Thursday 21 March 2013, Brad King wrote:
> 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 sufficien
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}
>
