Re: [CMake] Bug fix requests for the *next* release of CMake...
http://public.kitware.com/Bug/view.php?id=12373 -- 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 when $ is in the directory path
The offending line is this. /tmp/$/build$ grep -H -n '/tmp/$/src/tutorial.cpp' CMakeFiles/tutorial.exe.dir/build.make CMakeFiles/tutorial.exe.dir/build.make:53:CMakeFiles/tutorial.exe.dir/tutorial.cpp.o: /tmp/$/src/tutorial.cpp This is obviously a bug in cmake but not a bug in make, as special treatment must be done for '$' in Makefile (see the following example). I hope that it is helpful to the development of cmake by providing this kind of corner case test. ~/linux/test/gnu/make/$$ cat Makefile .PHONY: all all: ../$$/out.txt ../$$/out.txt: ../$$/in.txt cp $< $@ clean: $(RM) ../$$/out.txt ~/linux/test/gnu/make/$$ make clean rm -f ../$/out.txt Just in case my make and cmake are not the newest. And the bug has been fixed in later version. Here are my make and cmake versions. ~/linux/test/gnu/make/$$ make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-apple-darwin10.0 ~/linux/test/gnu/make/$$ cmake --version cmake version 2.8.8 > First of all, this is not a bugtracker. If you want your bug fixed, > you should file it in the kitware bugtracker. It is nonetheless helpful to discuss it here. Obviously, you did not think it is a bug. There are also previous bug discussions on this mailing list. -- 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
Re: [CMake] CMake is unable to find QtCore!
Did you make the mistake of relocating your Qt installation? You could run qmake -query to see the paths it prints out, to make sure it matches your installation. Clint On Aug 12, 2012, at 12:59 PM, Toronto Andrew wrote: > 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 -- 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 when $ is in the directory path
> andreas@warnemuende /tmp/$/foo % cat main.cpp
> int main()
> {
> return 0;
> }
>
> andreas@warnemuende /tmp/$/foo % cat CMakeLists.txt
> add_executable(foo main.cpp)
>
> Can you try that on your side to see wether it works?
The error still exits.
/tmp/$/foo_build$ cmake ../foo
-- 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/$/foo_build
/tmp/$/foo_build$ make
Scanning dependencies of target foo
make[2]: *** No rule to make target `/tmp/foo/main.cpp', needed by
`CMakeFiles/foo.dir/main.cpp.o'. Stop.
make[1]: *** [CMakeFiles/foo.dir/all] Error 2
make: *** [all] Error 2
/tmp/$/foo_build$ cat.sh ../foo/
CMakeLists.txt main.cpp
/tmp/$/foo_build$ cat.sh ../foo/*
==> ../foo/CMakeLists.txt <==
add_executable(foo main.cpp)
==> ../foo/main.cpp <==
int main()
{
return 0;
}
--
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
Re: [CMake] CMake is unable to find QtCore!
Haha spot on mate. I did so. To rectify, I reinstalled VTK and CMake, fixed the PATH var and the QTDIR. FindQt4 now actually finds 4.8.2 as opposed to 4.8.0, however some flags like QT_USE_FILE and QT_QTGUI_LIBRARY seem to still point at 4.8.0 prompting some linker issues during the build. http://cmake.3232098.n2.nabble.com/file/n7581165/8Mj17.png Just for reference, the CMakeLists is found http://pastie.org/4466367 here if need be. -- View this message in context: http://cmake.3232098.n2.nabble.com/CMake-is-unable-to-find-QtCore-tp7581149p7581165.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
[CMake] cmake manpage in pdf with section (subsection, etc) bookmarks and hyperlinks?
Hi, I use the following command to generate the pdf file from cmake manpage. But the pdf file does not have bookmarks. Does anybody know a way to generated the manual in pdf with bookmarks and possibly hyperlinks? man -t "$f" | ps2pdf - > $f.pdf -- 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
Re: [CMake] cmake manpage in pdf with section (subsection, etc) bookmarks and hyperlinks?
2012/8/13 Peng Yu : > Hi, > > I use the following command to generate the pdf file from cmake > manpage. But the pdf file does not have bookmarks. Does anybody know a > way to generated the manual in pdf with bookmarks and possibly > hyperlinks? > > man -t "$f" | ps2pdf - > $f.pdf If you want to generate a single pdf, cmake itself can already generate: html: $ cmake --help-full cmake-help.html docbook: $ cmake --help-full cmake-help.docbook Then you may try: $ htmldoc -f cmake-help.pdf --webpage cmake-help.html or $ docbook2pdf cmake-help.docbook the docbook version is upsetting my docbook processor (openjade) with a lot of syntax error. I don't really use docbook so I don't know who is the culprit between openjade and the cmake generated docbook document. The html version is processed correctly your have proper hyperlinks, but you don't get PDF bookmarks. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- 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 manpage in pdf with section (subsection, etc) bookmarks and hyperlinks?
On 08/13/2012 04:18 PM, Peng Yu wrote: > Hi, > > I use the following command to generate the pdf file from cmake > manpage. But the pdf file does not have bookmarks. Does anybody know a > way to generated the manual in pdf with bookmarks and possibly > hyperlinks? > > man -t "$f" | ps2pdf - > $f.pdf > > Install dblatex and then run cmake --help-full cmake-doc.docbook to generate DocBook XML output which you then can process with your favourite tool-chain (e.g. dblatex or the xmlto convenience wrapper). However, it seems that the XML output does not validate (at least with CMake 2.8.6 that is...). xmllint really chokes badly on it. Michael -- 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...
On Friday 10 August 2012, David Cole wrote: > Hi all, > > Replies requested. Short replies only. Read on. Just a short reply > with bug numbers or links to the bugs is all we need here. > > Example one-line reply: > > http://public.kitware.com/Bug/view.php?id=13463 Personally I would prefer this link together with the title of the bug - makes it much faster to see what the bug is about: http://public.kitware.com/Bug/view.php?id=12621 - "Compatibility with Xcode 4.3" Alex -- 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 manpage in pdf with section (subsection, etc) bookmarks and hyperlinks?
> $ docbook2pdf cmake-help.docbook I got error message like the following on ubuntu. openjade:/home/pengy/cmake-help.docbook:13:14:E: end tag for "itemizedlist" which is not finished openjade:/home/pengy/cmake-help.docbook:21:14:E: end tag for "itemizedlist" which is not finished openjade:/home/pengy/cmake-help.docbook:30:14:E: end tag for "itemizedlist" which is not finished ... cmake version 2.8.5 -- 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
Re: [CMake] Bug fix requests for the *next* release of CMake...
On Mon, Aug 13, 2012 at 12:07 PM, Alexander Neundorf wrote: > On Friday 10 August 2012, David Cole wrote: > >> Hi all, > >> > >> Replies requested. Short replies only. Read on. Just a short reply > >> with bug numbers or links to the bugs is all we need here. > >> > >> Example one-line reply: > >> > >> http://public.kitware.com/Bug/view.php?id=13463 > > Personally I would prefer this link together with the title of the bug - > makes it much faster to see what the bug is about: > > http://public.kitware.com/Bug/view.php?id=12621 - "Compatibility with Xcode > 4.3" > > Alex Adding the title would be fine with me. Although that does introduce some data duplication. Even in this context, that's a little bit evil. In the case of people making typos in the bug number or the title, please clarify which one they're talking about before adding to the roadmap. :-) -- 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] Help with Windows SDK .lib files and headers. Trying to find winsock elements
Hey All,
I'm trying to work my way through some windows configuration and running
into problems. I'm trying a few things: looking for headers, looking for
lib files, and looking for functions/symbols in them. I'm particularly
interested in Winsock stuff right now.
I have a couple things hard coded for the moment just to get this working.
Here's what I have so far:
if(PLATFORM_WINDOWS)
set(WINDOWS_SDK_LIBRARIES "C:/Program Files (x86)/Windows
Kits/8.0/Lib/win8/um/x86")
set(WINDOWS_SDK_INCLUDES "C:/Program Files (x86)/Windows
Kits/8.0/Include/um")
set(CMAKE_LIBRARY_PATH ${WINDOWS_SDK_LIBRARIES})
set(CMAKE_INCLUDE_PATH ${WINDOWS_SDK_INCLUDES})
check_include_file(Windows.h HAVE_WINDOWS_H)
check_include_file(WinSock2.h HAVE_WINSOCK2_H)
check_include_file(WS2tcpip.h HAVE_WS2TCPIP_H)
check_include_file(IPHlpApi.h HAVE_IPHLPAPI_H)
set(_REQUIRED_INCLUDES Winsock2.h)
set(_REQUIRED_LIBRARIES WS2_32.lib WSock32.lib)
set(CMAKE_REQUIRED_INCLUDES ${_REQUIRED_INCLUDES})
set(CMAKE_REQUIRED_LIBRARIES ${_REQUIRED_LIBRARIES})
check_library_exists(WS2_32 select WINDOWS_SDK_LIBRARIES HAVE_WS2_32_lib)
check_library_exists(WSock32 select WINDOWS_SDK_LIBRARIES HAVE_WSOCK32_lib)
//tried these too
//check_library_exists(WS2_32.lib select WINDOWS_SDK_LIBRARIES
HAVE_WS2_32_lib)
//check_library_exists(WSock32.lib select WINDOWS_SDK_LIBRARIES
HAVE_WSOCK32_lib)
endif()
And here's the output:
Looking for Windows.h
Looking for Windows.h - found
Looking for WinSock2.h
Looking for WinSock2.h - found
Looking for WS2tcpip.h
Looking for WS2tcpip.h - found
Looking for IPHlpApi.h
Looking for IPHlpApi.h - not found
Looking for select in WS2_32
Looking for select in WS2_32 - not found
Looking for select in WSock32
Looking for select in WSock32 - not found
A few interesting things about the results:
-IPHlpApi.h header, it says not found but it clearly exists in C:\Program
Files (x86)\Windows Kits\8.0\Include\um\IPHlpApi.h
-WS2_32.lib, it says not found but it exists at C:/Program Files
(x86)/Windows Kits/8.0/Lib/win8/um/x86/WS2_32.lib
-WSock32.lib, it says not found but it exists at C:/Program Files
(x86)/Windows Kits/8.0/Lib/win8/um/x86/WSock32.lib
-I'm checking for the "select" function which according to MSDN exists in
WS2_32.lib
Is there a way to check for .lib files without required a function?
Wondering if that's the issue with finding the winsock lib files. If so,
then how would I make sure select exists? I could probably just assume it
exists after finding the lib files, but I need successful tests first.
Any help is much appreciated.
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] cmake manpage in pdf with section (subsection, etc) bookmarks and hyperlinks?
2012/8/13 Peng Yu : >> $ docbook2pdf cmake-help.docbook > > I got error message like the following on ubuntu. > > openjade:/home/pengy/cmake-help.docbook:13:14:E: end tag for > "itemizedlist" which is not finished > openjade:/home/pengy/cmake-help.docbook:21:14:E: end tag for > "itemizedlist" which is not finished > openjade:/home/pengy/cmake-help.docbook:30:14:E: end tag for > "itemizedlist" which is not finished Yes it looks like an itemizedlist should at least contain one "itemlist": http://www.docbook.org/tdg/en/html/itemizedlist.html When I manually fix this I get plenty more errors. -- Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org -- 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!
Hi, On Mon, Aug 13, 2012 at 4:16 PM, Toronto Andrew wrote: > Haha spot on mate. > > I did so. To rectify, I reinstalled VTK and CMake, fixed the PATH var and > the QTDIR. Relocating Qt requires either patching the qmake binary or installing a qt.conf file to help qmake find the libs in the new position. The absolute include/lib dirs are hardcoded into qmake when its being built. See http://doc.qt.nokia.com/4.7/qt-conf.html for the file-format > FindQt4 now actually finds 4.8.2 as opposed to 4.8.0, however > some flags like QT_USE_FILE and QT_QTGUI_LIBRARY seem to still point at > 4.8.0 prompting some linker issues during the build. Does that mean you didn't move Qt this time? > http://cmake.3232098.n2.nabble.com/file/n7581165/8Mj17.png > > Just for reference, the CMakeLists is found http://pastie.org/4466367 here > if need be. Did you start with a clean cache? The screenshot suggests you're trying to mix debug and release Qt libraries, thats a very bad idea anyways (QtOpenGLdd and QtGui4 are mentioned). So maybe things are still not picked up as you think they are? The cache-file should have more information. And you should get rid of LINK_DIRECTORIES, thats not a good idea and almost always the wrong fix to whatever linking problems you have. CMake find-modules are supposed to setup the absolute path to libraries in the variables they 'export', which can be used with target_link_libraries directly. Same goes for the 'link_libraries' call for MacOSX I'd say. Andreas -- 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] Mastering CMake 6th edition?
Bump. On Mon, Jul 30, 2012 at 3:59 PM, Xu Wang wrote: > Hi, > > I'm curious as to whether there will be a 6th edition of this wonderful > book. If so, any (rough?) estimate on when it will be published? > > Thanks so much! > > Xu > -- 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] How to suppress output like "-- Checking whether C ", etc.?
Hi,
I just want "Hello World!" to be shown and everything else be
suppressed. "-Wno-dev" seems not relevant. I don't find other options
seem to be useful in the manual. In case I miss anything in the
manual, is there an option to suppress these messages? Thanks!
~/linux/test/cmake/lang/command/message/build$ cat ../src1/CMakeLists.txt
message("Hello World!")
~/linux/test/cmake/lang/command/message/build$ rm -rf *
~/linux/test/cmake/lang/command/message/build$ cmake ../src1/
-- 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
Hello World!
-- Configuring done
-- Generating done
-- Build files have been written to:
/Users/pengy/linux/test/cmake/lang/command/message/build
--
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] How to force cmake to run on a different source directory?
Hi, The following directory has 'cmake ../src1' run before. I get the following error when I run the following command. One way to solve the problem is to run "rm -rf *", but I'm wondering if there is a way to force cmake to run even when the source directory changes. I don't see such a command line option in the manual. Thanks! ~/linux/test/cmake/lang/command/message/build$ cmake ../src/ CMake Error: The source "/Users/pengy/linux/test/cmake/lang/command/message/src/CMakeLists.txt" does not match the source "/Users/pengy/linux/test/cmake/lang/command/message/src1/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory. -- 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
Re: [CMake] CMake is unable to find QtCore!
Andreas Pakulat-2 wrote > > Hi, > > Relocating Qt requires either patching the qmake binary or installing > a qt.conf file to help qmake find the libs in the new position. The > absolute include/lib dirs are hardcoded into qmake when its being > built. See http://doc.qt.nokia.com/4.7/qt-conf.html for the > file-format > > -> *First off, I really appreciate you looking at my build errors. > > Patching the qmake binary? I reinstalled the 4.8.2 binary, why is this not > enough? Of course, I will write a qt-conf file I am unable to correct my > building environment.* > >> FindQt4 now actually finds 4.8.2 as opposed to 4.8.0, however >> some flags like QT_USE_FILE and QT_QTGUI_LIBRARY seem to still point at >> 4.8.0 prompting some linker issues during the build. > > Does that mean you didn't move Qt this time? > > -> *Well, I have both Qt versions withing the same directory (C:/Qt/4.8.0 > as well as C:/Qt/4.8.2), and while qmake seems to be configured properly > for 4.8.2, I feel like it is the flags I mentioned earlier that point at > 4.8.0, however, I could be mistaken. I figured this out > * >> http://cmake.3232098.n2.nabble.com/file/n7581165/8Mj17.png >> >> Just for reference, the CMakeLists is found http://pastie.org/4466367 >> here >> if need be. > > Did you start with a clean cache? The screenshot suggests you're > trying to mix debug and release Qt libraries, thats a very bad idea > anyways (QtOpenGLdd and QtGui4 are mentioned). So maybe things are > still not picked up as you think they are? The cache-file should have > more information. > > And you should get rid of LINK_DIRECTORIES, thats not a good idea and > almost always the wrong fix to whatever linking problems you have. > CMake find-modules are supposed to setup the absolute path to > libraries in the variables they 'export', which can be used with > target_link_libraries directly. Same goes for the 'link_libraries' > call for MacOSX I'd say. > > Andreas > > *I did start with a clean cache. I see what is happening with the > debug/release libraries, but do you know what might have caused this? > There is nothing in the CMakeLists file that seems like it may be causing > it. Could it be a way the other libraries are built (VTK ?) > > I will avoid using LINK_DIRECTORIES and optimize the CMakeLists file, will > post back if there is progress. * > -- > > 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 > -- View this message in context: http://cmake.3232098.n2.nabble.com/CMake-is-unable-to-find-QtCore-tp7581149p7581176.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] How to force cmake to run on a different source directory?
Hi, On Mon, Aug 13, 2012 at 9:48 PM, Peng Yu wrote: > Hi, > > The following directory has 'cmake ../src1' run before. I get the > following error when I run the following command. One way to solve the > problem is to run "rm -rf *", but I'm wondering if there is a way to > force cmake to run even when the source directory changes. I don't see > such a command line option in the manual. Thanks! There is no such way, the correct way is to rm -rf *. Andreas -- 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] How to suppress output like "-- Checking whether C ", etc.?
Hi,
you can't tell cmake to do this and usually you don't want to either.
These are status messages indicating what cmake is using so you can
easily spot if cmake chose the wrong compiler or found a library in a
place where you didn't expect it.
To suppress all non-error output you can do:
cmake ../ >/dev/null
on *nix systems. That way only errors in your cmake files are being shown.
Andreas
On Mon, Aug 13, 2012 at 9:42 PM, Peng Yu wrote:
> Hi,
>
> I just want "Hello World!" to be shown and everything else be
> suppressed. "-Wno-dev" seems not relevant. I don't find other options
> seem to be useful in the manual. In case I miss anything in the
> manual, is there an option to suppress these messages? Thanks!
>
> ~/linux/test/cmake/lang/command/message/build$ cat ../src1/CMakeLists.txt
> message("Hello World!")
> ~/linux/test/cmake/lang/command/message/build$ rm -rf *
> ~/linux/test/cmake/lang/command/message/build$ cmake ../src1/
> -- 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
> Hello World!
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /Users/pengy/linux/test/cmake/lang/command/message/build
>
>
> --
> 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
--
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
On 8/12/2012 1:25 PM, Michael Jackson wrote: 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. I don't think that is true. Xcode does install them, it just does not put them in the PATH... -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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
On 8/11/2012 5:43 PM, Jerry Krinock wrote: 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. Yes, sure. 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. But, if you use the Xcode generator with cmake it would work just fine. So, as long as you only use cmake -GXcode then this is not an issue. -Bill -- 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!
Hi, On Mon, Aug 13, 2012 at 9:40 PM, Toronto Andrew wrote: > > Andreas Pakulat-2 wrote >> >> Relocating Qt requires either patching the qmake binary or installing >> a qt.conf file to help qmake find the libs in the new position. The >> absolute include/lib dirs are hardcoded into qmake when its being >> built. See http://doc.qt.nokia.com/4.7/qt-conf.html for the >> file-format >> >> -> *First off, I really appreciate you looking at my build errors. >> >> Patching the qmake binary? I reinstalled the 4.8.2 binary, why is this not >> enough? Well, patching the qmake binary is exactly what happens when you use Nokia's binary installer for Qt and it patches qmake to the install location you chose during the installation. The patching/qt.conf file is only necessary if you then move Qt again to another location. >>> FindQt4 now actually finds 4.8.2 as opposed to 4.8.0, however >>> some flags like QT_USE_FILE and QT_QTGUI_LIBRARY seem to still point at >>> 4.8.0 prompting some linker issues during the build. >> >> Does that mean you didn't move Qt this time? >> >> -> *Well, I have both Qt versions withing the same directory (C:/Qt/4.8.0 >> as well as C:/Qt/4.8.2), and while qmake seems to be configured properly >> for 4.8.2, I feel like it is the flags I mentioned earlier that point at >> 4.8.0, however, I could be mistaken. You can actually find out how cmake gets qt libs etc. from qmake: qmake -query produces a list of paths. CMake will use these with find_library/find_file and prefers them over the standard lookup paths of those functions (by using them as HINTS). So if qmake produced QT_INSTALL_LIBS:C:\Qt\4.8.2 then CMake should find all Qt libraries in that location. >>> Just for reference, the CMakeLists is found http://pastie.org/4466367 >>> here >>> if need be. >> >> Did you start with a clean cache? The screenshot suggests you're >> trying to mix debug and release Qt libraries, thats a very bad idea >> anyways (QtOpenGLdd and QtGui4 are mentioned). So maybe things are >> still not picked up as you think they are? The cache-file should have >> more information. >> >> And you should get rid of LINK_DIRECTORIES, thats not a good idea and >> almost always the wrong fix to whatever linking problems you have. >> CMake find-modules are supposed to setup the absolute path to >> libraries in the variables they 'export', which can be used with >> target_link_libraries directly. Same goes for the 'link_libraries' >> call for MacOSX I'd say. >> >> Andreas >> >> *I did start with a clean cache. I see what is happening with the >> debug/release libraries, but do you know what might have caused this? Not without seeing the cmake cache or some output what the various cmake variables you're using actually contain. >> There is nothing in the CMakeLists file that seems like it may be causing >> it. Could it be a way the other libraries are built (VTK ?) Could be, if the other cmake variables contain Qt debug libs, since you use them with link_directories and link_libraries they could influence the sample-target. Andreas -- 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] How to suppress output like "-- Checking whether C ", etc.?
On Mon, Aug 13, 2012 at 3:37 PM, Andreas Pakulat wrote:
> Hi,
>
> you can't tell cmake to do this and usually you don't want to either.
> These are status messages indicating what cmake is using so you can
According to the common linux philosophy, mostly status messages like
this are suppressed in other tools unless otherwise instructed.
Therefore, I think that it may be better to suppress these messages by
default and add an option in cmake to enable them when users want
these messages. After all, when cmake runs successfully, these
messages are useless and just make the output look ugly.
> easily spot if cmake chose the wrong compiler or found a library in a
> place where you didn't expect it.
>
> To suppress all non-error output you can do:
>
> cmake ../ >/dev/null
>
> on *nix systems. That way only errors in your cmake files are being shown.
>
> Andreas
>
> On Mon, Aug 13, 2012 at 9:42 PM, Peng Yu wrote:
>> Hi,
>>
>> I just want "Hello World!" to be shown and everything else be
>> suppressed. "-Wno-dev" seems not relevant. I don't find other options
>> seem to be useful in the manual. In case I miss anything in the
>> manual, is there an option to suppress these messages? Thanks!
>>
>> ~/linux/test/cmake/lang/command/message/build$ cat ../src1/CMakeLists.txt
>> message("Hello World!")
>> ~/linux/test/cmake/lang/command/message/build$ rm -rf *
>> ~/linux/test/cmake/lang/command/message/build$ cmake ../src1/
>> -- 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
>> Hello World!
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to:
>> /Users/pengy/linux/test/cmake/lang/command/message/build
>>
>>
>> --
>> 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
--
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
Re: [CMake] How to suppress output like "-- Checking whether C ", etc.?
On 8/13/2012 5:38 PM, Peng Yu wrote: According to the common linux philosophy, mostly status messages like this are suppressed in other tools unless otherwise instructed. Therefore, I think that it may be better to suppress these messages by default and add an option in cmake to enable them when users want these messages. After all, when cmake runs successfully, these messages are useless and just make the output look ugly. This is really modeled after autoconf and its generated configure scripts. I don't think there is a way to disable the output of a configure script as it does checks. I think this is very common to linux users doing builds. Also, the information is useful as it gives a progress to the user, and something to report to developers when something goes wrong. -Bill -- 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] How to build only when file contents are actually changed?
Hi,
The following command output shows that when I touch a source without
changing the content, the source are compiled and linked, which is a
waste.
This post shows how to use the checksum to decide whether a file is
changed or not, if changed then update target. This feature seems to
be missing in cmake. In case that I miss something in the document,
could anybody let me know if this is the case?
http://blog.jgc.org/2006/04/rebuilding-when-hash-has-changed-not.html
~/linux/test/cmake/lang/command/target_link_libraries/src$ cat.sh *
==> CMakeLists.txt <==
cmake_minimum_required(VERSION 2.8)
add_library(print print.cpp)
#include_directories(${HELLO_SOURCE_DIR})
add_executable(main main.cpp)
target_link_libraries(main print)
==> main.cpp <==
#include "print.hpp"
int main() {
print();
}
==> print.cpp <==
#include "print.hpp"
#include
using namespace std;
void print() {
cout << "Hello, World!" << endl;
}
==> print.hpp <==
#ifndef _hello_h
#define _hello_h
void print();
#endif
~/linux/test/cmake/lang/command/target_link_libraries/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:
/Users/pengy/linux/test/cmake/lang/command/target_link_libraries/build
~/linux/test/cmake/lang/command/target_link_libraries/build$ make
Scanning dependencies of target print
[ 50%] Building CXX object CMakeFiles/print.dir/print.cpp.o
Linking CXX static library libprint.a
[ 50%] Built target print
Scanning dependencies of target main
[100%] Building CXX object CMakeFiles/main.dir/main.cpp.o
Linking CXX executable main
[100%] Built target main
~/linux/test/cmake/lang/command/target_link_libraries/build$ touch
../src/print.hpp
~/linux/test/cmake/lang/command/target_link_libraries/build$ make
Scanning dependencies of target print
[ 50%] Building CXX object CMakeFiles/print.dir/print.cpp.o
Linking CXX static library libprint.a
[ 50%] Built target print
Scanning dependencies of target main
[100%] Building CXX object CMakeFiles/main.dir/main.cpp.o
Linking CXX executable main
[100%] Built target main
--
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
Re: [CMake] How to build only when file contents are actually changed?
CMake really leaves the decision when to recompile something to the
backend, i.e. GNU Make, Xcode, Visual Studio, ninja etc. It merely
defines dependencies and then lets the actual build tool handle the
rest, and most of them choose to use simple time-stamps instead of
hashes. Also note that computing the hash might also incur considerable
overhead, in particular for very large projects with thousands of files.
You can alleviate the situation a bit by using e.g. ccache to speed up
unnecessary recompilations. E.g. on a system that has ccache installed
in /usr/lib/ccache (Ubuntu, Debian,...)
mkdir build
cd build
rm -rf *
PATH=/usr/lib/cchace:$PATH cmake ..
will build using ccache instead the normal compilers.
HTH
Michael
On 08/14/2012 05:22 AM, Peng Yu wrote:
> Hi,
>
> The following command output shows that when I touch a source without
> changing the content, the source are compiled and linked, which is a
> waste.
>
> This post shows how to use the checksum to decide whether a file is
> changed or not, if changed then update target. This feature seems to
> be missing in cmake. In case that I miss something in the document,
> could anybody let me know if this is the case?
>
> http://blog.jgc.org/2006/04/rebuilding-when-hash-has-changed-not.html
>
> ~/linux/test/cmake/lang/command/target_link_libraries/src$ cat.sh *
> ==> CMakeLists.txt <==
> cmake_minimum_required(VERSION 2.8)
> add_library(print print.cpp)
> #include_directories(${HELLO_SOURCE_DIR})
> add_executable(main main.cpp)
> target_link_libraries(main print)
>
> ==> main.cpp <==
> #include "print.hpp"
> int main() {
> print();
> }
>
> ==> print.cpp <==
> #include "print.hpp"
> #include
> using namespace std;
> void print() {
> cout << "Hello, World!" << endl;
> }
>
> ==> print.hpp <==
> #ifndef _hello_h
> #define _hello_h
> void print();
> #endif
>
> ~/linux/test/cmake/lang/command/target_link_libraries/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:
> /Users/pengy/linux/test/cmake/lang/command/target_link_libraries/build
> ~/linux/test/cmake/lang/command/target_link_libraries/build$ make
> Scanning dependencies of target print
> [ 50%] Building CXX object CMakeFiles/print.dir/print.cpp.o
> Linking CXX static library libprint.a
> [ 50%] Built target print
> Scanning dependencies of target main
> [100%] Building CXX object CMakeFiles/main.dir/main.cpp.o
> Linking CXX executable main
> [100%] Built target main
> ~/linux/test/cmake/lang/command/target_link_libraries/build$ touch
> ../src/print.hpp
> ~/linux/test/cmake/lang/command/target_link_libraries/build$ make
> Scanning dependencies of target print
> [ 50%] Building CXX object CMakeFiles/print.dir/print.cpp.o
> Linking CXX static library libprint.a
> [ 50%] Built target print
> Scanning dependencies of target main
> [100%] Building CXX object CMakeFiles/main.dir/main.cpp.o
> Linking CXX executable main
> [100%] Built target main
>
>
>
>
--
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
