quot;
This information is not correct. The client-side
CTEST_NIGHTLY_START_TIME apparently _is_ used to determine the revision
number when svn updating.
Luke
From: Luke Kucalaba
Sent: Tuesday, May 04, 2010 11:16 AM
To: cmake@cmake.org
Subject: CTest_
ne Nightly Start Time
Specified time: 00:00:00 EDT
New revision of repository is: 27054
Gathering version information (one . per revision):
Found 6 updated files
Any advice/suggestions you could offer would be greatly appreciated.
Thanks!
Sincerely,
Luke Kucalaba
Senio
Problem solved! I finally found some time today to checkout the CMake
source code and get setup for development. I started the build and found
the answer I was looking for in
cmLocalVisualStudio7Generator::OutputBuildTool() :
const char* tool = "VCLibrarianTool";
fout << "\t\t\t
Thank
Hi,
I would like to reopen issue #0006794 dealing with this linker warning
that is still present for MSVC 7.1 static library builds:
Linking CXX static library ..\build\MT-DLL\Util-SL.lib
XMLWriter.cpp.obj : warning LNK4218: non-native module found; restarting
I did some more investiga
pically the linker phase does not
even occur until the very end of the whole process when finally string
together static libraries to create an executable or dll.
Luke
-Original Message-
From: Simon Sasburg [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 11, 2008 7:20 PM
To: Luke Kucala
Correction, that email somehow got corrupted wrt the newlines. These
should be on two separate lines:
Set(EXE_DEF "somedef") #executable defs
Set(LIB_DEF "somedef") #library def overrides
Sorry about that,
Luke
-Original Message-
From: Luke Kucalaba
Sent: Friday
I posted an issue on the mantis bug tracker a while ago regarding supporting
the /LTCG option for the MSVC71 generator. The issue history indicates this
problem is fixed, but with CMake 2.6.2 the correct flags are still not being
generated for the MSVC71 project files and nmake makefiles. Fort
ke
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 12:42 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] Running cmake multiple times to resolve cache
variables
Luke Kucalaba wrote:
> I think the reason we need to run cmak
ing how the multiple passes of cmake works?
Luke
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 11:12 AM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] Running cmake multiple times to resolve cache
variables
Luke Kucalaba wrote:
I have a question about knowing when you have run cmake enough times to
resolve all the cache variables for a project. In the CMake explanation
on the main website, regarding generation using the cmake.exe program
from the command-line in non-interactive mode, it says "It can be
difficult to know
yback\src\nmake
\CMakeFiles 39
Looks like it is creating temp files in "Documents and Settings\Local
Settings\Temp" and running as a script.
Luke
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 10:23 AM
To: Luke Kucalaba
Cc: cm
What was the final resolution of this issue? Was this fixed in CMake
2.6.2? If not, will this fix be included in the future releases?
Thanks!
Luke
Summary
0005150: VERBOSE=1 does not print flags passed
Description
CMake CVS does not print out the flags passed to the cl.exe an
rad King [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 3:48 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2
Luke Kucalaba wrote:
> First problem is that you will still have
> build configurations in your MSVC project re
entually I'd like to move to the "preferred"
method of establishing MSVC build configurations (ie if "set target
properties" is the most recommended and best supported method then we
definitely want to use that in the long run). But at this point, the
"set target prope
Luke
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 2:58 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2
Luke Kucalaba wrote:
> The attachment was shot down. I renamed to .png
The attachment was shot down. I renamed to .png and reattached. So you
will have to rename from .png to .zip when you download it. Maybe this
will work? Any suggestions on how to post this project?
Luke
-Original Message-
From: Luke Kucalaba
Sent: Thursday, October 09, 2008 1:19 PM
Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 12:19 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2
Luke Kucalaba wrote:
> Our software team is having problems upgrading to CMake 2.6.2 from
That worked! Many Thanks. The quotes must have been messing up CMake
somehow. This issue is now resolved.
Luke
From: David Cole [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 12:34 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re
INDOWS;C:\WINDOWS\Sy
stem32\Wbem;C:\Program Files\Common Files\GTK\2.0\bin;C:\Program
Files\doxygen\bin;C:\Program Files\ATI Technologies\ATI
.ACE\Core-Static;C:\Documents and Settings\dsci\My Documents\Borland
Studio Projects\Bpl;C:\Program Files\CMake 2.6\bin;
Thanks
Luke
_______
Our software team is having problems upgrading to CMake 2.6.2 from our
current working build system that uses CMake 2.4.7. In particular, we
are using the "Visual Studio 7 .NET 2003", "NMake Makefiles", "Unix
Makefiles", and "CodeBlocks - Unix Makefiles" project/makefile
generators.
We are hav
t found. Please set
CMAKE_CXX_COMPILER to a valid compiler path or name.
* Configuring incomplete, errors occurred!
We did not encounter any problems like this when building MSVC71 NMake
makefiles with CMake 2.4.7. If anyone has any ideas or suggestions, it
would be greatly appreciated. I
21 matches
Mail list logo
