Re: [cmake-developers] [CMake] Bug fix requests for the *next* release of CMake...
I would like if this Bug Report is not longer on backlog: http://public.kitware.com/Bug/view.php?id=9188 I have uploaded a patch ready for integration. Claus -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] ReactOS: Important filed bug reports went to backlog en masse
Just idly, I wonder how practical it would be to automatically close bugs older than XXX time that haven't been touched or assigned. If nothing else it'd generate a notification to the submitter of the bug that either the bug was over looked or not considered important and deserves some discussion if they want it fixed. I've read a few articles online about doing this sort of thing to clear the 'fog' of irrelevant issues that clogs up bug trackers, esp. public ones. ~ Doug. On Sun, Aug 12, 2012 at 8:10 PM, David Cole david.c...@kitware.com wrote: I certainly did not mean to offend anyone with my en masse move of issues to 'backlog' -- thanks for speaking up. I would like to make sure that you guys can continue to use CMake for ReactOS. I've got to run right now, but I will reply again tomorrow when I have some more time. Do you have time for a quick phone call or Google+ hangout this week sometime, so I can understand better what your issues are? (And why nobody adopted them when they appeared on the mailing list in the form of your bug reports...) Thanks, David Cole On Sat, Aug 11, 2012 at 9:42 PM, Amine Khaldi amine.kha...@reactos.org wrote: Hello folks, I would like to mention that many (if not all) the bugs coming from us (ReactOS) got into backlog. We're an operating system project, we try to file bug report only for issues that block us, so we do not tend to file trivial bugs. It would be great if the CMake folks tried to pay the attention that our issues deserve.. after all, we started using CMake because we read many positive reviews about the excellent support. Unfortunately, we're not able to use the VS generators due to the lack of support for ASM preprocessed files. We're not able to pass flags to C/C++ source files without affecting the rc (resource) files. We're forced to do many ugly workarounds for the latter, and we found no solution for the former, and these are just examples. All these mentioned issues got into the backlog, so basically we're left off, without any help to get them solved. I'm writing this hopefully as a call to the CMake folks/community to address our issues, that we've been waiting release after release to get them fixed, only to find out that they ended up in backlog now. I'm writing this in the hopes of finding a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing. Regards, Amine. -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[CMake] CMake is unable to find QtCore!
I get the following errors when trying to build my Qt project: CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindQt4.cmake:595 (MESSAGE): Could NOT find QtCore. Check And I need to manually point the CMake gui in the direction of qmake.exe; additionally, I receive these flags: QT_QTCORE_LIBRARY_DEBUG-NOTFOUND, QT_QTCORE_LIBRARY_RELEASE-NOTFOUND and QT_MKSPECS_DIR-NOTFOUND, and I am unsure about how to get FindQt4.cmake to work properly. Thanks in advance! -- View this message in context: http://cmake.3232098.n2.nabble.com/CMake-is-unable-to-find-QtCore-tp7581149.html Sent from the CMake mailing list archive at Nabble.com. -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake is unable to find QtCore!
On Sun, Aug 12, 2012 at 10:30 AM, Toronto Andrew andrew.loui...@gmail.com wrote: I get the following errors when trying to build my Qt project: CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindQt4.cmake:595 (MESSAGE): Could NOT find QtCore. Check And I need to manually point the CMake gui in the direction of qmake.exe; additionally, I receive these flags: QT_QTCORE_LIBRARY_DEBUG-NOTFOUND, QT_QTCORE_LIBRARY_RELEASE-NOTFOUND and QT_MKSPECS_DIR-NOTFOUND, and I am unsure about how to get FindQt4.cmake to work properly. Thanks in advance! Did you point cmake-gui to the location of qmake? John -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake is unable to find QtCore!
On Sun, Aug 12, 2012 at 10:33 AM, John Drescher dresche...@gmail.com wrote: On Sun, Aug 12, 2012 at 10:30 AM, Toronto Andrew andrew.loui...@gmail.com wrote: I get the following errors when trying to build my Qt project: CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindQt4.cmake:595 (MESSAGE): Could NOT find QtCore. Check And I need to manually point the CMake gui in the direction of qmake.exe; additionally, I receive these flags: QT_QTCORE_LIBRARY_DEBUG-NOTFOUND, QT_QTCORE_LIBRARY_RELEASE-NOTFOUND and QT_MKSPECS_DIR-NOTFOUND, and I am unsure about how to get FindQt4.cmake to work properly. Thanks in advance! Did you point cmake-gui to the location of qmake? Are all the Qt dlls in the same folder as qmake.exe? This should be the bin folder inside of the Qt build. -- John M. Drescher -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Bug 12424
Hello, I am emailing in regards to this bug http://cmake.org/Bug/view.php?id=12424 as I have found a possible workaround. Though I have not found another website talking about it, there appears to be a bug in Visual Studio 10 when using the /Zm1000 option without pre-compiled headers. This combination causes the error c1 : fatal error C1060: compiler is out of heap space even though the /Zm option is supposed to increase the heap space. I found that changing /Zm to /Zm200 is working on my system. Fortunately, users can simply change all occurrences of /Zm1000 to /Zm200 in C:\Program Files\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake to resolve the problem. Hopefully others will find this useful. Thank you, Marshall Galbraith -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.8 : Reproducible Crash in Mac OS X 10.8
I think you can actually download the Command line tools and install them _without_ installing Xcode. Have not tried but this is what I am led to believe. _ Mike Jackson mike.jack...@bluequartz.net On Sat, Aug 11, 2012 at 5:43 PM, Jerry Krinock je...@sheepsystems.com wrote: On 2012 Aug 10, at 10:55, Bill Hoffman bill.hoff...@kitware.com wrote: Just curious what would an autotools or makefile based project do on a new mac? I am guessing it will not print anything other than, there is no compiler found. That said we will try to make cmake print a helpful message or work out of the box. I am just wondering how other projects are handling the sudden disappearance of the compiler from the command line... (it has been there since the very first OSX Mac…) That's a good question, Bill. The answer is that, starting with recent versions, Xcode 4.3 or 4.4 I think, the Xcode Command-Line Tools are not installed with Xcode, but are a separate download which must be installed after installing Xcode. So you see I had been using the Xcode for a couple weeks, happily compiling other projects. But then I found that cmake wouldn't work. -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake is unable to find QtCore!
Yes to both John, I did point the CMake gui to the position of the qmake.exe within the bin, and it does come with whatever DLLs the source comes with. I am using Qt 4.8.0 and the latest CMake gui for Windows (x86). Some other things to get out of the way: QTDIR is set to C:/Qt/4.8.0/bin, and this directory has been added to the list of PATH variables... -- View this message in context: http://cmake.3232098.n2.nabble.com/CMake-is-unable-to-find-QtCore-tp7581149p7581154.html Sent from the CMake mailing list archive at Nabble.com. -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Issues with Library Dependency while building OpenCV Static
Correction, the dynamic library was not linking, it simply wouldn't fail when it couldn't find libraries, which is why I had errors importing. I was able to fix this by forcing an include of /opt/local/lib in CMakeList.txt with: LINK_DIRECTORIES(/opt/local/lib) I am still confused why the abundance of '/opt/local/lib' in the CMakeCache.txt file did not cause make to add -L/opt/local/lib to the gcc command. GCC command below. Can someone please shed some light? thanks /usr/bin/c++-fPIC -W -Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -fdiagnostics-show-option -pthread -fomit-frame-pointer -msse -msse2 -O3 -DNDEBUG -DNDEBUG -arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/opencv_perf_core.dir/perf/perf_abs.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_addWeighted.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_arithm.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_bitwise.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_compare.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_convertTo.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_dft.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_dot.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_inRange.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_main.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_math.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_merge.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_minmaxloc.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_norm.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_precomp.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_reduce.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_split.cpp.o CMakeFiles/opencv_perf_core.dir/perf/perf_stat.cpp.o -o ../../bin/opencv_perf_core ../../lib/libopencv_core.a ../../lib/libopencv_ts.a ../../lib/libopencv_highgui.a -lstdc++ ../../lib/libopencv_imgproc.a ../../lib/libopencv_core.a -lstdc++ ../../3rdparty/lib/liblibjpeg.a ../../3rdparty/lib/liblibpng.a ../../3rdparty/lib/liblibtiff.a ../../3rdparty/lib/libzlib.a ../../3rdparty/lib/liblibjasper.a /opt/local/lib/libImath.dylib /opt/local/lib/libIlmImf.dylib /opt/local/lib/libIex.dylib /opt/local/lib/libHalf.dylib /opt/local/lib/libIlmThread.dylib -ldc1394 -lavcodec -lavformat -lavutil -lswscale /opt/local/include/../lib/libavcodec.a /opt/local/include/../lib/libavformat.a /opt/local/include/../lib/libavutil.a /opt/local/include/../lib/libswscale.a -framework Cocoa /usr/lib/libbz2.dylib -framework VideoDecodeAcceleration -lbz2 -framework QTKit -framework QuartzCore -framework AppKit -- View this message in context: http://cmake.3232098.n2.nabble.com/Issues-with-Library-Dependency-while-building-OpenCV-Static-tp7581059p7581155.html Sent from the CMake mailing list archive at Nabble.com. -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Bug fix requests for the *next* release of CMake...
http://www.cmake.org/Bug/view.php?id=13204 http://www.cmake.org/Bug/view.php?id=13162 -- Dave Abrahams BoostPro Computing Software DevelopmentTraining http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Bug when $ is in the directory path
Hi,
I have the following example copied from the cmake Tests/Tutorial
directory. cmake works fine.
/tmp/xxx/src$ cat.sh *
== CMakeLists.txt ==
cmake_minimum_required (VERSION 2.6)
project (Tutorial)
# The version number.
set (Tutorial_VERSION_MAJOR 1)
set (Tutorial_VERSION_MINOR 0)
# configure a header file to pass some of the CMake settings
# to the source code
configure_file (
${PROJECT_SOURCE_DIR}/TutorialConfig.h.in
${PROJECT_BINARY_DIR}/TutorialConfig.h
)
# add the binary tree to the search path for include files
# so that we will find TutorialConfig.h
include_directories(${PROJECT_BINARY_DIR})
# add the executable
add_executable(tutorial.exe tutorial.cpp)
== TutorialConfig.h.in ==
// the configured options and settings for Tutorial
#define Tutorial_VERSION_MAJOR ${Tutorial_VERSION_MAJOR}
#define Tutorial_VERSION_MINOR ${Tutorial_VERSION_MINOR}
== tutorial.cpp ==
// A simple program that computes the square root of a number
#include stdio.h
#include TutorialConfig.h
int main (int argc, char *argv[])
{
fprintf(stdout,%s Version %d.%d\n,
argv[0],
Tutorial_VERSION_MAJOR,
Tutorial_VERSION_MINOR);
return 0;
}
When I mv xxx to '$'
/tmp/$$ dir
build src
I get the following error. This is must be due to a bug in cmake such
that it can not handle directory path with '$' in it. Could anybody
fix it? Thanks!
/tmp/$/build$ cmake ../src/
-- The C compiler identification is GNU 4.2.1
-- The CXX compiler identification is GNU 4.2.1
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/$/build
/tmp/$/build$ dir
CMakeCache.txt CMakeFiles Makefile TutorialConfig.h cmake_install.cmake
/tmp/$/build$ make
Scanning dependencies of target tutorial.exe
make[2]: *** No rule to make target `/tmp/src/tutorial.cpp', needed by
`CMakeFiles/tutorial.exe.dir/tutorial.cpp.o'. Stop.
make[1]: *** [CMakeFiles/tutorial.exe.dir/all] Error 2
make: *** [all] Error 2
--
Regards,
Peng
--
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/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Windows: Finding stdint.h header succeeds, but finding int8_t type fails
Hey All, First off I'm loving cmake, This thing makes my life so easy. Thank you! I'm working on porting some code to Windows at the moment. I'm putting in configure checks for stdint.h and it's types. The strange thing is that finding the header works, but then finding the type fails. check_include_file(stdint.h HAVE_STDINT_H) - works check_type_size(int8_t HAVE_int8_t) - fails check_symbol_exists(int8_t stdint.h HAVE_int8_t) - fails I'm looking at stdint.h in C:\Program Files (x86)\Microsoft Visual Studio 11\VC\include\stdint.h and it clearly defines int8_t: typedef signed charint8_t; I've also tried running cmake-gui from the commandline and first setting: set CMAKE_INCLUDE_PATH=C:\Program Files (x86)\Microsoft Visual Studio 11\VC\include\ cmake-gui What am I missing? Windows is certainly strange but there has to be a way to get cmake finding it correctly. Any ideas? Thanks! -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] UTILITY library?
But it would be great if one can override msproject target type. It could be used properly in generator commands and test afterwards without any problems with configurations. (E.g. if you have test runner or kind of code generator written in C# or VB). On Wed, Aug 8, 2012 at 4:49 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: I apparently fixed the problem by using add_dependencies() instead of target_link_libraries() ... Klaim / Joel Lamotte -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- 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/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
