2012/8/28 Bruce Cartland :
> I'm currently generating multiple distinct debian packages (runtime and
> dev).
>
> I have a typical cmake file with cpack commands in it ending with
> "inlude(CPack)" . This generates the targets "package" and "package-source".
> On debian platforms, I want "package_so
I'm currently generating multiple distinct debian packages (runtime and
dev).
I have a typical cmake file with cpack commands in it ending with
"inlude(CPack)" . This generates the targets "package" and
"package-source". On debian platforms, I want "package_source" but I'd
like to redefine/ov
Hi,
I'm trying to compile a very simple program (called wrl2smol) with CMake.
This program is a single file of plain C, has no dependencies other than C
standard libraries, and has no graphics. It's a test for a more complex
program, so I want to get the build system to work with CMake, even if
Hello All,
OS X 10.8.1
CMAKE 2.8.9
Apple clang version 4.0 (tags/Apple/clang-421.10.60) (based on LLVM 3.1svn)
I found: http://vtk.org/Wiki/CMake_FAQ#Does_CMake_support_precompiled_headers.3F
But I am not seeing how I would specify/use a pre-compiled header in
my CMakeLists.txt file.
Can anyone
I'm seeing different results here between Windows 7 and Windows XP.
Here is the CMake code I use to add /FI (force includes) to the
compiler flags for a source file:
function( _force_include header_file )
if( MSVC )
foreach( source ${ARGN} )
get_file
Great, this regex solution is much better, thanks!
I've tested it with the German cl version and it works.
I've pushed it to next.
Peter
On 27.08.2012 09:58, Nils Gladitz wrote:
I replaced the five string commands in CMakeCLDeps.cmake with:
string(REGEX MATCH "\n([^:]*:[^:]*:[ \t]*)" sh
I replaced the five string commands in CMakeCLDeps.cmake with:
string(REGEX MATCH "\n([^:]*:[^:]*:[ \t]*)" showOut2 "${showOut}")
set(showOut3 "${CMAKE_MATCH_1}")
Which looks like it would work but I don't know if it is safe to assume
that the localized messages match as well(?)
Nils
