Consider the following:
CMakeLists.txt:
set (ZERO 0)
configure_file (
${CMAKE_SOURCE_DIR}/include/config.h.cmake
${CMAKE_BINARY_DIR}/include/config.h
)
${CMAKE_SOURCE_DIR}/include/config.h.cmake:
#cmakedefine ZERO @ZERO@
When I run cmake, I get the follow
Command files are a normal occurrence in builds on Windows platforms.
Example:
C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe
@C:\Users\myself\AppData\Local\Temp\nmEC62.tmp
If VERBOSE is true, the contents of these command files are not
displayed in the build output but I believe they should be. I'
Where can I find info/tutorials on adding support for new languages to
CMake?
Thanks,
Eric.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Oct 16, 2008, at 8:08 PM, "Alan W. Irwin"
<[EMAIL PROTECTED]> wrote:
On 2008-10-16 18:08-0600 Eric (Brad) Lemings wrote:
Where can I find info/tutorials on adding support for new languages
to
CMake?
The following is pretty minimal, but I think this is all t
Alan W. Irwin wrote:
> On 2008-10-16 18:08-0600 Eric (Brad) Lemings wrote:
>
>>
>> Where can I find info/tutorials on adding support for new languages to
>> CMake?
>
> The following is pretty minimal, but I think this is all there is at the
> moment.
>
> Loo
Eric (Brad) Lemings wrote:
> Alan W. Irwin wrote:
>
>> On 2008-10-16 18:08-0600 Eric (Brad) Lemings wrote:
>>
>>
>>> Where can I find info/tutorials on adding support for new languages to
>>> CMake?
>>>
>> The following i
Alan W. Irwin wrote:
> On 2008-10-16 18:08-0600 Eric (Brad) Lemings wrote:
>
>>
>> Where can I find info/tutorials on adding support for new languages to
>> CMake?
>
> The following is pretty minimal, but I think this is all there is at the
> moment.
>
> Loo
Eric (Brad) Lemings wrote:
> Greetings,
>
> I just noticed that if you define RUNTIME_OUTPUT_DIRECTORY before
> linking a DLL on Windows, CMake will link the DLL in the appropriate
> location as well as the incremental link files and manifests but not
> the DLL stub library
Why does CMake do this and how can I tell it to NOT replace semicolons
with spaces?
CMakeLists.txt:
set (FOO one;two;three)
add_custom_target (foo.exe ALL
myCmd -I${FOO}
VERBATIM)
CMake Output:
myCmd -Ione two three
Thanks,
Eric.
_
for declaring lists of strings.
> With quotes, FOO will be a single string instead.
>
> Sam
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Eric (Brad) Lemings
> Sent: Tuesday, October 21, 2008 2:01 PM
> To: cmake@cmake
Ah hah. Quotes alone don't do the trick but quotes with backslash
escape characters does do the trick. FYI.
Eric.
Eric (Brad) Lemings wrote:
> The `add_custom_target' command still transforms the semicolons into
> spaces. I don't the the VERBATIM option really means
Greetings,
I was wondering if the Makefile generators only generate rules for
compiling sources and linking libraries/objects into executables as
seperate targets or is there a rule/command for building executables by
compiling sources and linking libraries/objects in one command.
Something to th
>From the CMake FAQ:
"CMake does not generate a "make distclean" target. Why?
Some build trees created with GNU autotools have a "make distclean"
target that cleans the build and also removes Makefiles and other parts
of the generated build system. CMake does not generate a "make
distcle
Alexander Neundorf wrote:
> What would be the purpose of this ?
> What is the purpose of distclean anyway ?
>
These are conventional GNU cleaning targets that apply to virtually all
software that is built from source.
The various cleaning targets are specified here:
http://www.gnu.org/software/a
Michael Jackson wrote:
> Are you using a dedicated build directory or are you running cmake
> directly from your source directory? If the latter.. STOP.. don't do
> that. If you use a dedicated build directory then cleaning up from
> cmake is as simple as rm -rf Build/ and there are no worrie
Eric Noulard wrote:
> 2008/11/6 Michael Jackson <[EMAIL PROTECTED]>:
>
>> All this is asking is 2 extra commands.
>>
>
> You may perfectly do that with autotools too:
>
> mkdir build
> cd build
> /path/to/source/configure
> make
> make install
Right. And because with autotools, the build p
Consider the following:
C:\Users\myself\Test>type CMakeLists.txt
cmake_minimum_required(VERSION 2.6)
project (Test)
message (STATUS ENV{ProgramFiles}=$ENV{ProgramFiles})
C:\Users\myself\Test>set ProgramFiles
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Fi
--- Begin Message ---
We've started working some with CMake here, and I've just come across a
gotcha, I think.
In the qmake.conf files for all Visual Studio compilers later than VC6,
the flag /Zc:wchar- is included. I'm not at all sure why this is set -
someone asked this before and nobody seeme
18 matches
Mail list logo