David Cole wrote:
> That's just the quick brain dump version. If necessary, I can actually
> look at old commits, or the current code to try to refresh my memory.
>
I think that's needed. Can you do that research into the commits and
discussion?
Thanks,
Steve.
--
Powered by www.kitware.co
Dear All,
I am trying to update an cmake based project with additional features.
Current Structure
FOO_Main_Dir
--- filters
--- surface
After adding my features
FOO_Main_Dir
--- filters
--- surface
--- CMakeLists.txt
--- my_feature
--- filters --- CMakeLists.txt
--- surface --- CMakeList
This is surely something basic, but I'm far from a CMake guru and would rather
not spend weeks digging to solve something that *seems* like it'll be simple.
We have assembler modules in a project. These use macros, as assembler modules
are wont to do.
So if module FOO.asm uses macro BAR.mac, an
Hello all:
I've tried this a few different ways and ran into issues. If someone
wouldn't mind pointing out where I'm going wrong, I would appreciate it.
(for example if there's a better way to do what I'm trying).
Thanks,
cmake_minimum_required(VERSION 2.8)
project(BLOXWEB)
#include addition
I've updated my patch again to V3. In this version, the WinRT is considered
as a platform. Generators with "WinRT" suffix, such as "Visual Studio 12
WinRT", "Visual Studio 12 ARM WinRT", can be used to generate a WinRT
targeting MSVC project. It would be easier to use than the hack before.
Comment
Hi.
CMake already has "CMAKE_BUILD_TYPE" I'd recommend using that instead of your
own solution. I'm not aware of similar switch for static/shared, however in my
opinion it should be done the same way the "CMAKE_BUILD_TYPE" works. You don't
have to play in checking for invalid configurations.