Hmm, having trouble emailing the list. Full question is here:
http://pastebin.com/riWe6zX7
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org
Looking at the mail archive it appears that my message was cut off. The
remainder:
>From a compile standpoint, there is no problem -- the codegen is built with
-DCODEGEN so it won't include the generated file, which of course wouldn't
even exist on the first pass. But since CMake doesn't preproc
Hi,
I'm having issues with the way CMake scans for dependencies. It's causing
unpredictable rebuilds of my project which means I need to run 'make'
multiple times (until nothing rebuilds) before I can 'sudo make install'.
The project incorporates a code generator. It parses all C++ header files
Yeah, seems silly, I know. But ctest and cmake both need to know about
it, and we didn't (and still don't) want to introduce a dependency of
reading the CMakeCache file from ctest.
Let us know if there's still an issue after you do that.
On Wed, Oct 3, 2012 at 1:56 PM, Julien Malik wrote:
> OK
OK I did not understand I needed *both*.
Reading the blog article again, I feel stupid. I swear I've read it
several times ;)...
That must be it.
Thanks for hint,
Julien
Le 03/10/2012 19:25, David Cole a écrit :
http://www.kitware.com/blog/home/post/11
Did you try setting CTEST_USE_LAUNCHE
I am invoking cmake as part of a jenkins script and am using "cmake --build
." to kick off the build. This works but does not do the equivalent of
"make -j4" to take advantage of all 4 cores when run on a linux machine.
When run on a windows machine the building in parallel is already taken
care o
I have some weird logic for the download. If the file is NOT on the
server, that is not an error -- it simply means we do not have
includes, or do not have binaries (either is not erroneous, as not
every library will have or need both). So I've had to write custom
logic for each protocol to handle
On Wed, Oct 3, 2012 at 12:58 PM, Julien Malik wrote:
> Hi again,
>
> I'm still looking for an idea about where to look.
>
> For the nightly build dir where CTEST_USE_LAUNCHERS is set in the ctest
> script but the dashboard behaves like it wasn't, I can see in VERBOSE mode :
>
> [ 59%] Building CXX
Hi again,
I'm still looking for an idea about where to look.
For the nightly build dir where CTEST_USE_LAUNCHERS is set in the ctest
script but the dashboard behaves like it wasn't, I can see in VERBOSE mode :
[ 59%] Building CXX object
Code/Learning/CMakeFiles/OTBLearning.dir/otbChangeProfi
On Wed, Oct 3, 2012 at 8:36 AM, Pere Mato Vila wrote:
>
> On Oct 3, 2012, at 1:36 PM, David Cole wrote:
>
>> The mismatch problem should be fixed in the builds of CMake 2.8.10-rc1
>> that we released yesterday. Give that a try and see if the default
>> compiler selection is better here -- it shoul
I've just checked my C:/Windows/SysWOW64 directory and it does not contain
a driver_root directory. It would have been a good catch if that was the
cause.
On 27 September 2012 19:20, Andreas Schenk
wrote:
> I had the same problem recently. Do you have a *driver_root* directory in*
> **C:/Windo
On Oct 3, 2012, at 1:36 PM, David Cole wrote:
> The mismatch problem should be fixed in the builds of CMake 2.8.10-rc1
> that we released yesterday. Give that a try and see if the default
> compiler selection is better here -- it should be.
>
> Let us know if there's still an issue...
Yes., I
On Wed, Oct 3, 2012 at 3:49 AM, Nick Overdijk wrote:
> I'm not sure where it was, but CMake prefers gcc over cc, and cxx over g++.
> You can force it by setting CC=clang.
>
> On 2012-03-10, at 09:27:28 , Pere Mato Vila wrote:
>
>> In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by defau
Thanks for the tip. I'll see how I can adapt this to my scenario.
Petr
On Tue, Oct 2, 2012 at 12:49 PM, David Cole wrote:
> CMake has code like this using the TEST_INCLUDE_FILE directory property to
> deal with this situation:
>
>
> # In the main CMakeLists.txt:
> # Set up test-time configurati
I'm not sure where it was, but CMake prefers gcc over cc, and cxx over g++. You
can force it by setting CC=clang.
On 2012-03-10, at 09:27:28 , Pere Mato Vila wrote:
> In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by default the GNU
> compiler for C and Clang for C++. This posses pro
In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by default the GNU
compiler for C and Clang for C++. This posses problems later when building my
package. The package can be built correctly either with Clang or with GCC but
not in a mixed mode. See the cmake output:
-- The C compile
16 matches
Mail list logo
