Ok, how does it sound if we have a variable, such as
CMAKE_EXPORT_COMPILE_COMMANDS?
Let's say, CMAKE_EXPORT_TARGETS_INFORMATION.
I would prefer CMAKE_EXPORT_TARGETS_FILE, or some name that implies it
is a filename value, with the value of the variable being the name of
the file to generate.
On Tue, Sep 2, 2014 at 1:03 PM, David Cole dlrd...@aol.com wrote:
Ok, how does it sound if we have a variable, such as
CMAKE_EXPORT_COMPILE_COMMANDS?
Let's say, CMAKE_EXPORT_TARGETS_INFORMATION.
I would prefer CMAKE_EXPORT_TARGETS_FILE, or some name that implies it
is a filename value,
It seems so. I was thrown off by the multiple levels of indirection
happening since the actual values in the OPTIONAL_INCLUDES end up as
foo1;foo2-NOTFOUND;bar. I was thinking that if(VARNAME) would only work
if the value of VARNAME was actually VARNAME-NOTFOUND but that's not the
case, it works
On 08/29/2014 05:26 AM, Nils Gladitz wrote:
I tried wrapping the libraries returned by FindBoost.cmake in
$BUILD_INTERFACE in a target_link_libraries() call and noticed that
this breaks because of the debug/optimized keywords that the find module
inserts.
Specifically it results in CMake
On 09/02/2014 04:12 PM, Brad King wrote:
On 08/29/2014 05:26 AM, Nils Gladitz wrote:
Steve K and I discussed this once. Since DEBUG_CONFIGURATIONS can be
set differently in exporting and importing projects so there is no
global meaning across all targets. See the
On 08/28/2014 08:52 AM, Pascal Bach wrote:
This brings the behavior of Visual Studio 2013 in line with the one of Visual
Studio 2012.
In combination with your related issue report:
WindowsCE: /SUBSYSTEM and /ENTRYPOINT does not end up in the generated Visual
Studio project
Hi Brad
In combination with your related issue report:
WindowsCE: /SUBSYSTEM and /ENTRYPOINT does not end up in the
generated Visual Studio project
http://www.cmake.org/Bug/view.php?id=15115
it looks like a bit of work is needed to get Windows CE support
working with VS 2013. Also,
On 09/02/2014 11:27 AM, Bach, Pascal wrote:
we should now be able to activate cross-compiling
with -DCMAKE_SYSTEM_NAME=WindowsCE or -
DCMAKE_TOOLCHAIN_FILE=...
while still using -G Visual Studio 12 2013 as the generator.
I think proposal would make things cleaner.
Great. It should be able
On Tuesday, September 02, 2014 09:58:37 David Cole via cmake-developers wrote:
It makes sense. But what IDE are you referring to? Eclipse? Some other
concrete example? Or just any IDE and this feature should work
everywhere CMake works...?
AFAIK it is kdevelop4, and the goal is that developers
Preliminaries to this topic have already been posted on the cmake
list, but the only response there (from Mark Abraham) was
Raw try_compile is not a great idiom for general use (though it is
unclear why it is not working well for you). Using the
Modules/Check*cmake gear is a much better option,
10 matches
Mail list logo
