On Thu, 2017-09-21 at 16:23 +0200, Nagy-Egri Máté Ferenc via CMake wrote:
> Hi Paul!
>
> I do not quite understand your comments.
>
> Are you referring to the SFML distribution model? I am aware that
> deliberately forcing my end-users to ship a FindModule script sucks and I
> was not trying to
Hi Gonzalo,
Zlib has a C interface (or rather, its all C) so a version of it built with
vc2013 can work with c++ code built with vs2015. But this probably means
that you need both redistributables installed on the target machine (2013
and 2015). Id make sure you install both runtimes unless you bu
El 21/09/2017 a las 11:08, Luis Caro Campos escribió:
Hi Gonzalo,
Since you are using ninja files and building from command line, I
suspect you are using a Visual Studio 2015 command prompt.
It may be beneficial to initialise a command prompt to specifically
target Windows 8.1 SDK which is
Hi Paul!
I do not quite understand your comments.
- Are you referring to the SFML distribution model? I am aware that
deliberately forcing my end-users to ship a FindModule script sucks and I was
not trying to promote that. I just said that it happens. The part where you say
„emphasize that is
On Thu, Sep 21, 2017 at 03:35:13PM +0200, Nils Gladitz wrote:
> On Thu, Sep 21, 2017 at 3:26 PM, Patrick Welche wrote:
> When unquoted each list items is turned into a distinct argument for the
> message() invocation.
> message() concatenates its arguments hence "onetwo".
>
> To preserve the semi
Hi Gonzalo,
Since you are using ninja files and building from command line, I suspect
you are using a Visual Studio 2015 command prompt.
It may be beneficial to initialise a command prompt to specifically target
Windows 8.1 SDK which is the one to go to target Windows 7.
First, make sure Windows
Hi Patrick,
On Thu, Sep 21, 2017 at 9:26 AM, Patrick Welche wrote:
> Having run cmake 3.9.2 once already, I see:
>
> $ cat CMakeLists.txt
> set(var one two)
> message(${var})
> $ cmake .
> onetwo
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /tmp/cmaketest
>
>
On Thu, Sep 21, 2017 at 3:26 PM, Patrick Welche wrote:
> Having run cmake 3.9.2 once already, I see:
>
> $ cat CMakeLists.txt
> set(var one two)
> message(${var})
> $ cmake .
> onetwo
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /tmp/cmaketest
>
> Would you ha
Having run cmake 3.9.2 once already, I see:
$ cat CMakeLists.txt
set(var one two)
message(${var})
$ cmake .
onetwo
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/cmaketest
Would you have expected "one;two" rather than "onetwo"?
Cheers,
Patrick
--
Powered by
On Thu, Sep 21, 2017 at 4:21 AM, Craig Scott
wrote:
> You probably want the BUILD_ALWAYS option. Have a look at the overhauled
> docs for ExternalProject (only available on master at the moment) for a
> more informative description of the option and the module in general:
>
> Excellent that fixes
On Thu, Sep 21, 2017 at 1:09 PM, J Decker wrote:
> how do I make sure that externalprojects get built if I change a source in
> one?
>
"BUILD_ALWAYS 1" should always trigger the build of the external project.
This would be required since only the external project's build system will
know if some
You probably want the BUILD_ALWAYS option. Have a look at the overhauled
docs for ExternalProject (only available on master at the moment) for a
more informative description of the option and the module in general:
https://cmake.org/cmake/help/git-master/module/ExternalProject.html
On Thu, Sep 2
By manually deleting (or touching) the stamp file associated with the
earliest step you need to re-run.
ExternalProject is not for auto-detecting changes to stuff and
minimally re-running build steps. It's for static stuff that doesn't
change much.
Find the "-build" stamp file that's associated w
how do I make sure that externalprojects get built if I change a source in
one?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on e
14 matches
Mail list logo