Petr Kmoch wrote:
> On Thu, Jun 18, 2015 at 1:43 AM, Robert Dailey
> wrote:
>
>> On Wed, Jun 17, 2015 at 4:31 PM, Dan Liew
>> wrote:
>> > On 17 June 2015 at 12:28, Robert Dailey
>> >
>> wrote:
>> >> Is there a way to only take (recursively) the include directiories
>> >> from a target or set o
On Thu, Jun 18, 2015 at 4:24 PM, Dan Liew wrote:
> Hi,
>
> On 18 June 2015 at 12:16, Robert Dailey wrote:
>> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote:
Can you explain what you mean by "strong" and "weak" symbols?
>>>
>>>
>>> Google is your friend
>>>
>>> https://en.wikipedia.org/wik
Hi,
On 18 June 2015 at 12:16, Robert Dailey wrote:
> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote:
>>> Can you explain what you mean by "strong" and "weak" symbols?
>>
>>
>> Google is your friend
>>
>> https://en.wikipedia.org/wiki/Weak_symbol
>>
>> http://stackoverflow.com/questions/2290587
Did you read through the pointed to stack overflow question and answers?
Is the information there misleading or incorrect?, ... because it
seems to say there is a way to do it with MSVC...
On Thu, Jun 18, 2015 at 3:16 PM, Robert Dailey wrote:
> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew w
On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote:
>> Can you explain what you mean by "strong" and "weak" symbols?
>
>
> Google is your friend
>
> https://en.wikipedia.org/wiki/Weak_symbol
>
> http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio
Normally Google is my
> Can you explain what you mean by "strong" and "weak" symbols?
Google is your friend
https://en.wikipedia.org/wiki/Weak_symbol
http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake F
On Thu, Jun 18, 2015 at 1:57 AM, Dan Liew wrote:
>> The reason I'm asking this question is because of how I handle unit
>> tests in CMake right now. Instead of just defining an executable
>> target for the test and then adding a link dependency on the library
>> containing the class or set of clas
> The reason I'm asking this question is because of how I handle unit
> tests in CMake right now. Instead of just defining an executable
> target for the test and then adding a link dependency on the library
> containing the class or set of classes to be tested, I am manually
> pulling in the CPP a
> This is the approach that the LLVM project uses which is very simple
> and very clean (take a look at the sources). This also works very well
> for installing your header files, the contents of ${CMAKE_SOURCE_DIR}
> just need to be copied into /usr/include .
Oops I meant to say the contents of
On Thu, Jun 18, 2015 at 1:43 AM, Robert Dailey
wrote:
> On Wed, Jun 17, 2015 at 4:31 PM, Dan Liew wrote:
> > On 17 June 2015 at 12:28, Robert Dailey
> wrote:
> >> Is there a way to only take (recursively) the include directiories from
> >> a target or set of targets? I know that include directo
On Wed, Jun 17, 2015 at 4:31 PM, Dan Liew wrote:
> On 17 June 2015 at 12:28, Robert Dailey wrote:
>> Is there a way to only take (recursively) the include directiories from
>> a target or set of targets? I know that include directories propagate
>> when passing targets to target_link_libraries(),
On 17 June 2015 at 12:28, Robert Dailey wrote:
> Is there a way to only take (recursively) the include directiories from
> a target or set of targets? I know that include directories propagate
> when passing targets to target_link_libraries(), but I do not want to
> link the libs; I only want the
Is there a way to only take (recursively) the include directories from
a target or set of targets? I know that include directories propagate
when passing targets to target_link_libraries(), but I do not want to
link the libs; I only want the include directories.
How can I do this? Thanks.
--
Pow
13 matches
Mail list logo
