It seems to be the cause.
Thanks
Vania
On 09/12/2016 09:42 AM, Magnus Therning wrote:
Bruce Stephens writes:
Looks like https://github.com/redguardtoo/cpputils-cmake might be involved...
If that is the case then this section could be of interest:
Bruce Stephens writes:
> Looks like https://github.com/redguardtoo/cpputils-cmake might be involved...
If that is the case then this section could be of interest:
https://github.com/redguardtoo/cpputils-cmake#stop-creating-makefiles-for-flymake
/M
--
Magnus
Looks like https://github.com/redguardtoo/cpputils-cmake might be involved...
On Fri, Sep 9, 2016 at 5:04 PM, Vania Joloboff wrote:
> On 09/09/2016 05:45 PM, Michael Ellery wrote:
>>
>> This kinda’ sounds like you are doing an in-source build. Are you certain
>> that
On 09/09/2016 05:45 PM, Michael Ellery wrote:
This kinda’ sounds like you are doing an in-source build. Are you certain that
your currrent/working directory is different from your source tree root when
you run cmake? The typical way of doing this is just to make a subdirectory of
your source
On Fri, Sep 9, 2016 at 4:45 PM, Michael Ellery wrote:
> This kinda’ sounds like you are doing an in-source build. Are you certain
> that your currrent/working directory is different from your source tree root
> when you run cmake? The typical way of doing this is just to
This kinda’ sounds like you are doing an in-source build. Are you certain that
your currrent/working directory is different from your source tree root when
you run cmake? The typical way of doing this is just to make a subdirectory of
your source root:
mkdir my_build
cd my_build
cmake
Hi,
I have started to use CMake for my software.
I build in a separate directory using :
$> cmake -G "Unix Makefiles"
Everything is built correctly and the software works fine.
However all of my source code directories get polluted.
Into each source directory, a new Makefile is created.
All