Domen Vrankar wrote:
> I've started solving this a while ago with treating every library as
> an external dependency even if it is part of the same repository as
> the code for the executable.
> For every new library that I write I also write a FindSomeLib.cmake
Much of what you describe should n
Angeliki Chrysochou wrote:
> Hi Bill,
>
> He wrote
>
> "Note also that prog.cpp includes this header via #include "myfunc.h"."
>
> in his first email, so I thought he wants to include it directly.
>
See his second email.
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages
Chris Johnson wrote:
> Yes, by adding another directory between my top-level ./src/ directory and
> ./mylib, I can cause the example to fail. I understand now that the
> include_directory() directive really has no hidden intelligence to it at
> all, as I had mistakenly believed. It's just a path
Chris Johnson wrote:
> That
> seems to imply the top-level source is not part of the default include
> path, correct?
Correct. CMake doesn't add anything by default. The only defaults are those
provided by the compiler.
--
Powered by www.kitware.com
Please keep messages on-topic and check t
2014-12-03 21:22 GMT+01:00 Chris Johnson :
> I think I've made it work by adding 1 ugly hack and 1 reasonable directive
> to each library's CMakeLists.txt, which is at least far preferable to adding
> several new include paths to potentially hundreds of programs which refer to
> those libraries.
Y
I think I've made it work by adding 1 ugly hack and 1 reasonable directive
to each library's CMakeLists.txt, which is at least far preferable to
adding several new include paths to potentially hundreds of programs which
refer to those libraries.
The hack is a function which is defined in my global
On 12/2/2014 5:19 PM, Chris Johnson wrote:
The target_link_libraries() directive is adequate for this job when the
header files for the library are simply referred to with no directory
prefix, i.e. #include "some file.h" instead of #include "my
lib/somefile.h". Referencing the library with targe
Hi.
The difference is that if there are any variables defined in something,
they will be defined in the scope of the function in the second case,
making them invisible outside of the function.
If that is your problem, you could help this by turning the function into a
macro (which has its own set
I have a something.cmake file that works when included directly, but
does not work when it is included from inside a function.
can someone explain if there is an intentional difference, and what it
is, between
include(something)
and
function(use_something)
On 02.12.2014 12:28, Georg Altmann wrote:
> Hi,
>
> I am using CMake for generating a project file for nvidia nsight to edit
> CUDA sources.
>
> $ mkdir myproj-build && cd myproj-build
> $ cmake -G"Eclipse CDT4 - Unix Makefiles" ../myproj
>
> The problem is, eclipse won't recognize the compiler
10 matches
Mail list logo
