Re: [CMake] CMake in Vim
On Sat September 28 2013 9.50.30 PM Magnus Therning wrote: > On Thu, Sep 26, 2013 at 04:39:06PM -0400, Jacky Alciné wrote: > > Hey all, > > > > I've been working on a Vim plug-in for Cmake. It provides a bit of > > support but it's on the rise and I'd love to hear from the Vim + > > Cmake users about it. > > > > http://jalcine.github.io/cmake.vim/ > > This is excellent to hear. At the moment I'm not working on any > project that uses CMake, but that's likely to change as soon as I can > make it happen ;-) I'll make sure to try your plugin out properly > then. For now here are some things that impressed me: > > 1. The initial quote on http://jalcine.github.io/cmake.vim/ is a >lovely way to set the stage for the introduction of the plugin :) > > 2. My first thought when reading your email in here was "I wonder if I >can install it via Vundle", and reading the section on installation >brought joy. > > Sorry for not being able to actually take it for a proper spin at the > moment, but hopefully you don't find my email a complete waste of bits > > :) > > /M Haha, love to hear it! I’m working to change the README to a bit more meaningful and provide some insight into what it does exactly. -- Jacky Alciné - 0x201999FC - http://jalcine.me "The human race has one really effective weapon, and that is laughter." - Mark Twain signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake in Vim
On Sat September 28 2013 8.15.05 PM Clifford Yapp wrote: > On Thu, Sep 26, 2013 at 4:39 PM, Jacky Alciné wrote: > > Hey all, > > > > I’ve been working on a Vim plug-in for Cmake. It provides a bit of support > > but it’s on the rise and I’d love to hear from the Vim + Cmake users > > about it. > > > > http://jalcine.github.io/cmake.vim/ > > > > Cheers! > > So we can put this in context, how does the functionality of this > plugin relate to the functionality from these files? > > http://www.cmake.org/CMakeDocs/cmake-syntax.vim > http://www.cmake.org/CMakeDocs/cmake-indent.vim > > I.e. is it complementary, is it intended to replace the above two files, > etc. > > Thanks, > CY > -- Hey CY, So it’s not meant to replace those two files. However, now that you point them out; I could add them into the plug-in to provide them if not already found. Thanks for pointing these two gems out! -- Jacky Alciné - 0x201999FC - http://jalcine.me "The human race has one really effective weapon, and that is laughter." - Mark Twain signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problems with auto-generated sources
On Monday 30 September 2013, Jakub Schmidtke wrote: > The workaround I found so far is to add a custom target that depends on the > targets I want to build. > So if I add this: > add_custom_target(test12 DEPENDS test1 test2) > > to my CMake file, and instead of running 'make -j test1 test2' I run 'make > -j test12' everything seems to be fine... IIRC, this is a known issue and you are using the recommended way to deal with it. Is that a limitation of make ? Alex -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Possible Bug in Cmake
On Mon, Sep 30, 2013 at 11:04 AM, Dan Kegel wrote: > If CMake is going to only > behave properly when an argument is given in uppercase, it should > abort if the argument is given in lowercase. Throw the users a bone! > There is *no excuse* for forcing users to guess. > > I thought there was a bug opened for this Better than that, it seems to be fixed: CMake Warning (dev) at CMakeLists.txt:1 (if): given arguments: "Linux" "matches" "Linux" Unknown arguments specified So I'm happy in that case. Are there other cases where the error is not detected? I think there are -- I've run into once recently -- but I forget what it was. - Dan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [PATCH] SunStudio 12 regex for CheckCCompilerFlags.cmake
On Sep 30, 2013, at 10:14 AM, Rolf Eike Beer wrote: > Am Montag, 30. September 2013, 16:15:07 schrieb William Orr: >> This macro currently doesn't properly match warnings emitted by SunStudio >> 12. This patch fixes that. > > I guess this also applies to the C++ compiler? Please rebase this change on > the cxx-flags topic on stage where the handling of those flags was reworked. > > Eike-- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake git can't find a cxx-flags branch, nor can I see one on gitweb signature.asc Description: Message signed with OpenPGP using GPGMail -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Possible Bug in Cmake
On Mon, Sep 30, 2013 at 10:29 AM, Williams, Norman K wrote: > I don't know why that is scary. It is the way CMake works, something that > one must accomodate in order to use CMake. I find it scary, annoying, and difficult to learn. If CMake is going to only behave properly when an argument is given in uppercase, it should abort if the argument is given in lowercase. Throw the users a bone! There is *no excuse* for forcing users to guess. I thought there was a bug opened for this, but I couldn't find it in a quick search. - Dan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Possible Bug in Cmake
I don't know why that is scary. It is the way CMake works, something that
one must accomodate in order to use CMake.
Obviously, if the Kitware people had it to do all over again, they
probably would do some things differently. But CMake has evolved (a lot!)
over the years, and it has some syntactic quirks.
Once you understand what they are, it's a very powerful tool for managing
large build systems.
--
Kent Williams norman-k-willi...@uiowa.edu
On 9/30/13 12:13 PM, "Sumit Adhikari" wrote:
>Thanks. This is scary :(
>
>
>Regards, Sumit
>
>
>
>On Mon, Sep 30, 2013 at 10:32 PM, Williams, Norman K
> wrote:
>
>It might be confusing -- well it is confusing! -- but CMake built-in
>commands, functions and macro names are case insensitive. CMake command
>keywords are case sensitive.
>
>The first is a legal CMake command. The second is a fatal CMake error:
>
>CMake Error at CMakeLists.txt:13 (if):
> if given arguments:
>
>"Darwin" "matches" "Linux"
>
> Unknown arguments specified
>
>
>
>--
>Kent Williams norman-k-willi...@uiowa.edu
>
>
>
>
>
>
>On 9/30/13 11:36 AM, "Sumit Adhikari" wrote:
>
>>Dear All,
>>
>>
>>if(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
>>
>>
>>differs from
>>
>>
>>if(${CMAKE_SYSTEM_NAME} matches "Linux")
>>
>>
>>
>>Is this behavior expected ?
>>
>>
>>Regards, Sumit
>>
>>
>>
>>
>>--
>>Sumit Adhikari,
>>Senior Architect - Product Development,
>>Synphony Teleca
>>
>>
>
>
>
>
>
>
>Notice: This UI Health Care e-mail (including attachments) is covered by
>the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
>confidential and may be legally privileged. If you are not the intended
>recipient, you are hereby notified that any
> retention, dissemination, distribution, or copying of this communication
>is strictly prohibited. Please reply to the sender that you have
>received the message in error, then delete it. Thank you.
>
>
>
>
>
>
>
>
>--
>Sumit Adhikari,
>Senior Architect - Product Development,
>Synphony Teleca
>
>
Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and
may be legally privileged. If you are not the intended recipient, you are
hereby notified that any retention, dissemination, distribution, or copying of
this communication is strictly prohibited. Please reply to the sender that you
have received the message in error, then delete it. Thank you.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problems with auto-generated sources
Actually I see the problem now -- it works fine if you build with one job,
but if you run 2 jobs, it for some reason runs the custom command and the
library build command twice.
Which is weird, and probably a bug. Without digging into the generated
Makefiles, it seems like the custom command throws off the normal course
of events in make. Make should see that test1 and test2 both depend on
LibFile, and build LibFile once, then build test1 and test2 in parallel.
You should log this as a CMake bug.
--
Kent Williams norman-k-willi...@uiowa.edu
On 9/30/13 12:19 PM, "Williams, Norman K"
wrote:
>I don't see the problem you're having.
>
>I re-wrote your CMakeLists.txt slightly to not use Unix commands:
>
>
>cmake_minimum_required(VERSION 2.8)
>project(Test)
>
>add_custom_command(OUTPUT file.c
>COMMAND echo "GENERATING FILE"
>COMMAND ${CMAKE_COMMAND} -E remove file.c
>COMMAND ${CMAKE_COMMAND} -E copy ${CMAKE_CURRENT_SOURCE_DIR}/org.c
>file.c
>DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/org.c
> )
>add_library(LibFile file.c)
>
>add_executable(test1 test.c)
>target_link_libraries(test1 LibFile)
>
>add_executable(test2 test.c)
>target_link_libraries(test2 LibFile)
>
>
>
>
>I only see GENERATING FILE once, even after the touch command.
>
>Could you be using an old version of CMake? I tested with the current
>development head, i.e. post-2.8.11.2
>
>
>developer 116% cmake ../src
>-- The C compiler identification is Clang 4.2.0
>-- The CXX compiler identification is Clang 4.2.0
>-- Check for working C compiler: /usr/bin/cc
>-- Check for working C compiler: /usr/bin/cc -- works
>-- Detecting C compiler ABI info
>-- Detecting C compiler ABI info - done
>-- 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: /scratch/kent/cmake/test/build
>developer 117% make
>[ 25%] Generating file.c
>GENERATING FILE
>Scanning dependencies of target LibFile
>[ 50%] Building C object CMakeFiles/LibFile.dir/file.c.o
>Linking C static library libLibFile.a
>/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
>/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
>/usr/bin/ranlib: warning for library: libLibFile.a the table of contents
>is empty (no object file members in the library define global symbols)
>[ 50%] Built target LibFile
>Scanning dependencies of target test1
>[ 75%] Building C object CMakeFiles/test1.dir/test.c.o
>Linking C executable test1
>[ 75%] Built target test1
>Scanning dependencies of target test2
>[100%] Building C object CMakeFiles/test2.dir/test.c.o
>Linking C executable test2
>[100%] Built target test2
>developer 123% touch ../src/org.c
>developer 124% make
>[ 25%] Generating file.c
>GENERATING FILE
>Scanning dependencies of target LibFile
>[ 50%] Building C object CMakeFiles/LibFile.dir/file.c.o
>Linking C static library libLibFile.a
>/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
>/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
>/usr/bin/ranlib: warning for library: libLibFile.a the table of contents
>is empty (no object file members in the library define global symbols)
>[ 50%] Built target LibFile
>Linking C executable test1
>[ 75%] Built target test1
>Linking C executable test2
>[100%] Built target test2
>
>
>
>
>
>--
>Kent Williams norman-k-willi...@uiowa.edu
>
>
>
>
>Notice: This UI Health Care e-mail (including attachments) is covered by
>the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
>confidential and may be legally privileged. If you are not the intended
>recipient, you are hereby notified that any retention, dissemination,
>distribution, or copying of this communication is strictly prohibited.
>Please reply to the sender that you have received the message in error,
>then delete it. Thank you.
>
>--
>
>Powered by www.kitware.com
>
>Please keep messages on-topic and check the CMake FAQ at:
>http://www.cmake.org/Wiki/CMake_FAQ
>
>Kitware offers various services to support the CMake community. For more
>information on each offering, please visit:
>
>CMake Support: http://cmake.org/cmake/help/support.html
>CMake Consulting: http://cmake.org/cmake/help/consulting.html
>CMake Training Courses: http://cmake.org/cmake/help/training.html
>
>Visit other Kitware open-source projects at
>http://www.kitware.com/opensource/opensource.html
>
>Follow this link to subscribe/unsubscribe:
>http://www.cmake.org/mailman/listinfo/cmake
Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and
may be l
Re: [CMake] Possible Bug in Cmake
Furthermore gvim adds more confusion to it
On Mon, Sep 30, 2013 at 10:43 PM, Sumit Adhikari
wrote:
> Thanks. This is scary :(
>
> Regards, Sumit
>
>
> On Mon, Sep 30, 2013 at 10:32 PM, Williams, Norman K <
> norman-k-willi...@uiowa.edu> wrote:
>
>> It might be confusing -- well it is confusing! -- but CMake built-in
>> commands, functions and macro names are case insensitive. CMake command
>> keywords are case sensitive.
>>
>> The first is a legal CMake command. The second is a fatal CMake error:
>>
>> CMake Error at CMakeLists.txt:13 (if):
>> if given arguments:
>>
>> "Darwin" "matches" "Linux"
>>
>> Unknown arguments specified
>>
>>
>>
>> --
>> Kent Williams norman-k-willi...@uiowa.edu
>>
>>
>>
>>
>>
>>
>> On 9/30/13 11:36 AM, "Sumit Adhikari" wrote:
>>
>> >Dear All,
>> >
>> >
>> >if(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
>> >
>> >
>> >differs from
>> >
>> >
>> >if(${CMAKE_SYSTEM_NAME} matches "Linux")
>> >
>> >
>> >
>> >Is this behavior expected ?
>> >
>> >
>> >Regards, Sumit
>> >
>> >
>> >
>> >
>> >--
>> >Sumit Adhikari,
>> >Senior Architect - Product Development,
>> >Synphony Teleca
>> >
>> >
>>
>>
>>
>>
>> Notice: This UI Health Care e-mail (including attachments) is covered by
>> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
>> confidential and may be legally privileged. If you are not the intended
>> recipient, you are hereby notified that any retention, dissemination,
>> distribution, or copying of this communication is strictly prohibited.
>> Please reply to the sender that you have received the message in error,
>> then delete it. Thank you.
>>
>>
>
>
>
> --
> Sumit Adhikari,
> Senior Architect - Product Development,
> Synphony Teleca
>
--
Sumit Adhikari,
Senior Architect - Product Development,
Symphony Teleca
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problems with auto-generated sources
I don't see the problem you're having.
I re-wrote your CMakeLists.txt slightly to not use Unix commands:
cmake_minimum_required(VERSION 2.8)
project(Test)
add_custom_command(OUTPUT file.c
COMMAND echo "GENERATING FILE"
COMMAND ${CMAKE_COMMAND} -E remove file.c
COMMAND ${CMAKE_COMMAND} -E copy ${CMAKE_CURRENT_SOURCE_DIR}/org.c
file.c
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/org.c
)
add_library(LibFile file.c)
add_executable(test1 test.c)
target_link_libraries(test1 LibFile)
add_executable(test2 test.c)
target_link_libraries(test2 LibFile)
I only see GENERATING FILE once, even after the touch command.
Could you be using an old version of CMake? I tested with the current
development head, i.e. post-2.8.11.2
developer 116% cmake ../src
-- The C compiler identification is Clang 4.2.0
-- The CXX compiler identification is Clang 4.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- 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: /scratch/kent/cmake/test/build
developer 117% make
[ 25%] Generating file.c
GENERATING FILE
Scanning dependencies of target LibFile
[ 50%] Building C object CMakeFiles/LibFile.dir/file.c.o
Linking C static library libLibFile.a
/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
/usr/bin/ranlib: warning for library: libLibFile.a the table of contents
is empty (no object file members in the library define global symbols)
[ 50%] Built target LibFile
Scanning dependencies of target test1
[ 75%] Building C object CMakeFiles/test1.dir/test.c.o
Linking C executable test1
[ 75%] Built target test1
Scanning dependencies of target test2
[100%] Building C object CMakeFiles/test2.dir/test.c.o
Linking C executable test2
[100%] Built target test2
developer 123% touch ../src/org.c
developer 124% make
[ 25%] Generating file.c
GENERATING FILE
Scanning dependencies of target LibFile
[ 50%] Building C object CMakeFiles/LibFile.dir/file.c.o
Linking C static library libLibFile.a
/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
/usr/bin/ranlib: file: libLibFile.a(file.c.o) has no symbols
/usr/bin/ranlib: warning for library: libLibFile.a the table of contents
is empty (no object file members in the library define global symbols)
[ 50%] Built target LibFile
Linking C executable test1
[ 75%] Built target test1
Linking C executable test2
[100%] Built target test2
--
Kent Williams norman-k-willi...@uiowa.edu
Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and
may be legally privileged. If you are not the intended recipient, you are
hereby notified that any retention, dissemination, distribution, or copying of
this communication is strictly prohibited. Please reply to the sender that you
have received the message in error, then delete it. Thank you.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problems with auto-generated sources
The workaround I found so far is to add a custom target that depends on the
targets I want to build.
So if I add this:
add_custom_target(test12 DEPENDS test1 test2)
to my CMake file, and instead of running 'make -j test1 test2' I run 'make
-j test12' everything seems to be fine...
On Mon, Sep 30, 2013 at 1:07 PM, Rolf Eike Beer wrote:
> Am Montag, 30. September 2013, 12:58:40 schrieb Jakub Schmidtke:
> > Hi,
> >
> > I am trying to get dependencies right in a project that uses
> auto-generated
> > sources.
> > I have a library, that uses auto-generated files, and other executables
> > that use that library.
> > I created a set of CMakeLists.txt files that show the problem.
> >
> > To run it you need test.c and org.c in the source directory, and one of
> > them should contain int main(void) { return 0; } in it,
> > the other can be empty. First try - the simplest approach:
> >
> > project(Test)
> >
> > add_custom_command(OUTPUT file.c
> > COMMAND echo "GENERATING FILE"
> > COMMAND rm -f file.c
> > COMMAND cp -i ${CMAKE_CURRENT_SOURCE_DIR}/org.c file.c
> > DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/org.c
> > )
> > add_library(LibFile file.c)
> >
> > add_executable(test1 test.c)
> > target_link_libraries(test1 LibFile)
> >
> > add_executable(test2 test.c)
> > target_link_libraries(test2 LibFile)
> >
> > When I build it with 'make' it builds just fine.
> > However, if (from the build/) directory I run: touch ../org.c; make -j
> > test1 test2 it sometimes gives me this:
> >
> > [ 25%] [ 25%] Generating file.c
> > Generating file.c
> > GENERATING FILE
> > GENERATING FILE
> > cp: overwrite ‘file.c’? [ 25%] [ 25%] Built target gen_file
> > Built target gen_file
>
> What a coincidence ;) I recently updated my CMake sources. I decided to do
> a
> partial rebuild as the executables themselves were in use and I wanted to
> avoid any hassle. So I typed
>
> make -j 10 CMakeLib CPackLib CTestLib
>
> And that resulted in basically the same problem: make tried to link
> CMakeLib
> three times in parallel, obviously failing. So the problem here is not
> limited
> to generated files I think.
>
> Eike
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Possible Bug in Cmake
Thanks. This is scary :(
Regards, Sumit
On Mon, Sep 30, 2013 at 10:32 PM, Williams, Norman K <
norman-k-willi...@uiowa.edu> wrote:
> It might be confusing -- well it is confusing! -- but CMake built-in
> commands, functions and macro names are case insensitive. CMake command
> keywords are case sensitive.
>
> The first is a legal CMake command. The second is a fatal CMake error:
>
> CMake Error at CMakeLists.txt:13 (if):
> if given arguments:
>
> "Darwin" "matches" "Linux"
>
> Unknown arguments specified
>
>
>
> --
> Kent Williams norman-k-willi...@uiowa.edu
>
>
>
>
>
>
> On 9/30/13 11:36 AM, "Sumit Adhikari" wrote:
>
> >Dear All,
> >
> >
> >if(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
> >
> >
> >differs from
> >
> >
> >if(${CMAKE_SYSTEM_NAME} matches "Linux")
> >
> >
> >
> >Is this behavior expected ?
> >
> >
> >Regards, Sumit
> >
> >
> >
> >
> >--
> >Sumit Adhikari,
> >Senior Architect - Product Development,
> >Synphony Teleca
> >
> >
>
>
>
>
> Notice: This UI Health Care e-mail (including attachments) is covered by
> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
> confidential and may be legally privileged. If you are not the intended
> recipient, you are hereby notified that any retention, dissemination,
> distribution, or copying of this communication is strictly prohibited.
> Please reply to the sender that you have received the message in error,
> then delete it. Thank you.
>
>
--
Sumit Adhikari,
Senior Architect - Product Development,
Synphony Teleca
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] [PATCH] SunStudio 12 regex for CheckCCompilerFlags.cmake
Am Montag, 30. September 2013, 16:15:07 schrieb William Orr: > This macro currently doesn't properly match warnings emitted by SunStudio > 12. This patch fixes that. I guess this also applies to the C++ compiler? Please rebase this change on the cxx-flags topic on stage where the handling of those flags was reworked. Eike signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Problems with auto-generated sources
Am Montag, 30. September 2013, 12:58:40 schrieb Jakub Schmidtke:
> Hi,
>
> I am trying to get dependencies right in a project that uses auto-generated
> sources.
> I have a library, that uses auto-generated files, and other executables
> that use that library.
> I created a set of CMakeLists.txt files that show the problem.
>
> To run it you need test.c and org.c in the source directory, and one of
> them should contain int main(void) { return 0; } in it,
> the other can be empty. First try - the simplest approach:
>
> project(Test)
>
> add_custom_command(OUTPUT file.c
> COMMAND echo "GENERATING FILE"
> COMMAND rm -f file.c
> COMMAND cp -i ${CMAKE_CURRENT_SOURCE_DIR}/org.c file.c
> DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/org.c
> )
> add_library(LibFile file.c)
>
> add_executable(test1 test.c)
> target_link_libraries(test1 LibFile)
>
> add_executable(test2 test.c)
> target_link_libraries(test2 LibFile)
>
> When I build it with 'make' it builds just fine.
> However, if (from the build/) directory I run: touch ../org.c; make -j
> test1 test2 it sometimes gives me this:
>
> [ 25%] [ 25%] Generating file.c
> Generating file.c
> GENERATING FILE
> GENERATING FILE
> cp: overwrite ‘file.c’? [ 25%] [ 25%] Built target gen_file
> Built target gen_file
What a coincidence ;) I recently updated my CMake sources. I decided to do a
partial rebuild as the executables themselves were in use and I wanted to
avoid any hassle. So I typed
make -j 10 CMakeLib CPackLib CTestLib
And that resulted in basically the same problem: make tried to link CMakeLib
three times in parallel, obviously failing. So the problem here is not limited
to generated files I think.
Eike
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Possible Bug in Cmake
It might be confusing -- well it is confusing! -- but CMake built-in
commands, functions and macro names are case insensitive. CMake command
keywords are case sensitive.
The first is a legal CMake command. The second is a fatal CMake error:
CMake Error at CMakeLists.txt:13 (if):
if given arguments:
"Darwin" "matches" "Linux"
Unknown arguments specified
--
Kent Williams norman-k-willi...@uiowa.edu
On 9/30/13 11:36 AM, "Sumit Adhikari" wrote:
>Dear All,
>
>
>if(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
>
>
>differs from
>
>
>if(${CMAKE_SYSTEM_NAME} matches "Linux")
>
>
>
>Is this behavior expected ?
>
>
>Regards, Sumit
>
>
>
>
>--
>Sumit Adhikari,
>Senior Architect - Product Development,
>Synphony Teleca
>
>
Notice: This UI Health Care e-mail (including attachments) is covered by the
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and
may be legally privileged. If you are not the intended recipient, you are
hereby notified that any retention, dissemination, distribution, or copying of
this communication is strictly prohibited. Please reply to the sender that you
have received the message in error, then delete it. Thank you.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Need HP-UX dashboards for CMake (HP-UX B.11.31)
On 9/30/2013 12:26 PM, Amul Shah wrote: Hi Bill, What's involved in the dashboard? Does the server pull and build or is the build pushed? thanks, Amul You setup a cronjob and pull from us. The server does not have any access to your machine. Basically, a ctest script is run that pulls from CMake git, does a build, and then pushes up some xml files. http://www.cmake.org/cmake/resources/testing.html It would be great if you could help out. Thanks. -Bill -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Problems with auto-generated sources
Hi,
I am trying to get dependencies right in a project that uses auto-generated
sources.
I have a library, that uses auto-generated files, and other executables
that use that library.
I created a set of CMakeLists.txt files that show the problem.
To run it you need test.c and org.c in the source directory, and one of
them should contain int main(void) { return 0; } in it,
the other can be empty. First try - the simplest approach:
project(Test)
add_custom_command(OUTPUT file.c
COMMAND echo "GENERATING FILE"
COMMAND rm -f file.c
COMMAND cp -i ${CMAKE_CURRENT_SOURCE_DIR}/org.c file.c
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/org.c
)
add_library(LibFile file.c)
add_executable(test1 test.c)
target_link_libraries(test1 LibFile)
add_executable(test2 test.c)
target_link_libraries(test2 LibFile)
When I build it with 'make' it builds just fine.
However, if (from the build/) directory I run: touch ../org.c; make -j
test1 test2 it sometimes gives me this:
[ 25%] [ 25%] Generating file.c
Generating file.c
GENERATING FILE
GENERATING FILE
cp: overwrite ‘file.c’? [ 25%] [ 25%] Built target gen_file
Built target gen_file
Scanning dependencies of target LibFile
Scanning dependencies of target LibFile
[ 50%] [ 50%] Building C object CMakeFiles/LibFile.dir/file.o
Building C object CMakeFiles/LibFile.dir/file.o
Linking C static library libLibFile.a
Linking C static library libLibFile.a
[ 75%] [ 75%] Built target LibFile
Built target LibFile
Linking C executable test1
Linking C executable test2
[125%] [125%] Built target test2
Built target test1
It builds (because it isn't very sophisticated example), but it clearly
tries to generate 'file.c' twice.
I tried several other options and they all have the same problem:
(the add_custom_command is exactly the same in all cases)
2.
add_library(LibFile file.c)
add_executable(test1 test.c)
target_link_libraries(test1 LibFile)
add_dependencies(test1 LibFile)
add_executable(test2 test.c)
target_link_libraries(test2 LibFile)
add_dependencies(test2 LibFile)
3.
add_custom_target(gen_file DEPENDS file.c)
add_library(LibFile file.c)
add_dependencies(LibFile gen_file)
add_executable(test1 test.c)
target_link_libraries(test1 LibFile)
add_dependencies(test1 LibFile)
add_executable(test2 test.c)
target_link_libraries(test2 LibFile)
add_dependencies(test2 LibFile)
4.
add_custom_target(gen_file DEPENDS file.c)
add_library(LibFile file.c)
add_dependencies(LibFile gen_file)
add_executable(test1 test.c)
target_link_libraries(test1 LibFile)
add_dependencies(test1 LibFile gen_file)
add_executable(test2 test.c)
target_link_libraries(test2 LibFile)
add_dependencies(test2 LibFile gen_file)
What am I doing wrong? Is it a problem with CMake?
How to solve this?
Thanks!
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Need HP-UX dashboards for CMake (HP-UX B.11.31)
Hi Bill, What's involved in the dashboard? Does the server pull and build or is the build pushed? thanks, Amul On 09/30/13 11:12, Bill Hoffman wrote: Hi all, Does anyone have access to a HP-UX B.11.31 machine that can run nightly CMake dashboards? Thanks. -Bill _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Possible Bug in Cmake
Dear All,
if(${CMAKE_SYSTEM_NAME} MATCHES "Linux")
differs from
if(${CMAKE_SYSTEM_NAME} matches "Linux")
Is this behavior expected ?
Regards, Sumit
--
Sumit Adhikari,
Senior Architect - Product Development,
Synphony Teleca
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] [PATCH] SunStudio 12 regex for CheckCCompilerFlags.cmake
This macro currently doesn't properly match warnings emitted by SunStudio 12. This patch fixes that. 0001-Added-SunStudio-12-regex-for-CheckCCompilerFlag.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] error on Mac while creating a fortran library
Hi, I am attempting to compile a library (Dakota) on my Mac workstation, but the process exits while attempting to create a library from fortran code in order to test the fortran compiler installation. The .o file is built without problems, but at the stage when it is supposed to run the "ar" command like this: ar cr libVerifyFortran.a CMakeFiles/VerifyFortran.dir/VerifyFortran.f.o it appears as "" cr libVerifyFortran.a CMakeFiles/VerifyFortran.dir/VerifyFortran.f.o It appears that cmake is unable to find the archive command "ar". I am using cmake and fortran from macports. Does this seem to be an error with my cmake installation or some missing cmake value that I need to set? Any help will be appreciated. Thanks, Manav -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Need HP-UX dashboards for CMake (HP-UX B.11.31)
Hi all, Does anyone have access to a HP-UX B.11.31 machine that can run nightly CMake dashboards? Thanks. -Bill -- 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 Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] add_custom_command, TARGET_LINKER_FILE and CMAKE_BUILD_TYPE
Hello everyonne,
I try to build my lybrary in debug and release mode in only one command.
The purpose is to create a package with the minimum files (library in
debug and release mode and headers) inside it.
Actually, I do something like this:
add_custom_command(OUTPUT build_release_debug_lib
POST_BUILD
COMMAND ${CMAKE_COMMAND} -E
copy $ ${CMAKE_CURRENT_BINARY_DIR}/lib)
I don't know how to add a new command to specify the CMAKE_BUILD_TYPE.
Is it possible?
Thank you!
Regards,
Romain
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Difficulties with component search by "FindBoost"
> Perhaps, all headers-only libraries could be handled by the FindBoost module I would appreciate if corresponding CMake scripts will consider a better handling for such software. > and then reported by CMake: > "Spirit is headers-only, shall not be specified with COMPONENTS" I would prefer a different feedback. Can the specification of "non-binary components" be also tolerated there? Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Difficulties with component search by "FindBoost"
On 30 September 2013 13:58, SF Markus Elfring wrote: > >> It might be not obvious from the manual [1], but COMPONENTS is dedicated >> to request lookup for the Boost libraries which are built as binary >> components. > > Can this documentation be improved? I'm sure it can, I presume patches for docs should be accepted. >> [1] http://cmake.org/cmake/help/v2.8.11/cmake.html#module:FindBoost > > Should this interface know when an error message is unnecessary in my use > case? The error in your original case was necessary, because specifying COMPONENTS spirit leads to lookup for non-existent binary library. Perhaps, all headers-only libraries could be handled by the FindBoost module and then reported by CMake: "Spirit is headers-only, shall not be specified with COMPONENTS" Best regards, -- Mateusz Loskot, http://mateusz.loskot.net "Participation in this whole process is a form of torture" ~~ Szalony -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Difficulties with component search by "FindBoost"
> Boost.Spirit is headers-only library, so there is no binary library supplied. Thanks for your response. > It might be not obvious from the manual [1], but COMPONENTS is dedicated > to request lookup for the Boost libraries which are built as binary > components. Can this documentation be improved? > [1] http://cmake.org/cmake/help/v2.8.11/cmake.html#module:FindBoost Should this interface know when an error message is unnecessary in my use case? Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Difficulties with component search by "FindBoost"
On 30 September 2013 12:00, SF Markus Elfring wrote: > Hello, > > I try to use a macro call like "find_package(Boost 1.49 REQUIRED COMPONENTS > spirit)". Boost.Spirit is headers-only library, so there is no binary library supplied. It might be not obvious from the manual [1], but COMPONENTS is dedicated to request lookup for the Boost libraries which are built as binary components. For the Spirit, you just need to check if you have Boost headers available: find_package(Boost 1.49 REQUIRED) [1] http://cmake.org/cmake/help/v2.8.11/cmake.html#module:FindBoost Best regards, -- Mateusz Loskot, http://mateusz.loskot.net "Participation in this whole process is a form of torture" ~~ Szalony -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Difficulties with component search by "FindBoost"
Hello, I try to use a macro call like "find_package(Boost 1.49 REQUIRED COMPONENTS spirit)". But I get surprised by the following messages despite of a complete installation from the current source files of this software library. elfring@Sonne:~/Projekte/Bau/boot_parameters/boost> cmake . -DBoost_DEBUG=ON -- [ /usr/share/cmake/Modules/FindBoost.cmake:476 ] _boost_TEST_VERSIONS = 1.56.0;1.56;1.55.0;1.55;1.54.0;1.54;1.53.0;1.53;1.52.0;1.52;1.51.0;1.51;1.50.0;1.50;1.49.0;1.49 -- [ /usr/share/cmake/Modules/FindBoost.cmake:478 ] Boost_USE_MULTITHREADED = TRUE -- [ /usr/share/cmake/Modules/FindBoost.cmake:480 ] Boost_USE_STATIC_LIBS = -- [ /usr/share/cmake/Modules/FindBoost.cmake:482 ] Boost_USE_STATIC_RUNTIME = -- [ /usr/share/cmake/Modules/FindBoost.cmake:484 ] Boost_ADDITIONAL_VERSIONS = -- [ /usr/share/cmake/Modules/FindBoost.cmake:486 ] Boost_NO_SYSTEM_PATHS = -- [ /usr/share/cmake/Modules/FindBoost.cmake:538 ] Declared as CMake or Environmental Variables: -- [ /usr/share/cmake/Modules/FindBoost.cmake:540 ] BOOST_ROOT = -- [ /usr/share/cmake/Modules/FindBoost.cmake:542 ] BOOST_INCLUDEDIR = -- [ /usr/share/cmake/Modules/FindBoost.cmake:544 ] BOOST_LIBRARYDIR = -- [ /usr/share/cmake/Modules/FindBoost.cmake:546 ] _boost_TEST_VERSIONS = 1.56.0;1.56;1.55.0;1.55;1.54.0;1.54;1.53.0;1.53;1.52.0;1.52;1.51.0;1.51;1.50.0;1.50;1.49.0;1.49 -- [ /usr/share/cmake/Modules/FindBoost.cmake:639 ] location of version.hpp: /usr/local/include/boost/version.hpp -- [ /usr/share/cmake/Modules/FindBoost.cmake:663 ] version.hpp reveals boost 1.54.0 -- [ /usr/share/cmake/Modules/FindBoost.cmake:739 ] guessed _boost_COMPILER = -gcc48 -- [ /usr/share/cmake/Modules/FindBoost.cmake:749 ] _boost_MULTITHREADED = -mt -- [ /usr/share/cmake/Modules/FindBoost.cmake:792 ] _boost_RELEASE_ABI_TAG = - -- [ /usr/share/cmake/Modules/FindBoost.cmake:794 ] _boost_DEBUG_ABI_TAG = -d -- [ /usr/share/cmake/Modules/FindBoost.cmake:842 ] _boost_LIBRARY_SEARCH_DIRS = /usr/local/include/lib;/usr/local/include/../lib;/usr/local/include/stage/lib;PATHS;C:/boost/lib;C:/boost;/sw/local/lib -- [ /usr/share/cmake/Modules/FindBoost.cmake:930 ] Searching for SPIRIT_LIBRARY_RELEASE: boost_spirit-gcc48-mt-1_54;boost_spirit-gcc48-mt;boost_spirit-mt-1_54;boost_spirit-mt;boost_spirit -- [ /usr/share/cmake/Modules/FindBoost.cmake:966 ] Searching for SPIRIT_LIBRARY_DEBUG: boost_spirit-gcc48-mt-d-1_54;boost_spirit-gcc48-mt-d;boost_spirit-mt-d-1_54;boost_spirit-mt-d;boost_spirit-mt;boost_spirit -- [ /usr/share/cmake/Modules/FindBoost.cmake:1017 ] Boost_FOUND = 1 CMake Error at /usr/share/cmake/Modules/FindBoost.cmake:1106 (message): Unable to find the requested Boost libraries. Boost version: 1.54.0 Boost include path: /usr/local/include The following Boost libraries could not be found: boost_spirit No Boost libraries were found. You may need to set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost. Call Stack (most recent call first): CMakeLists.txt:7 (find_package) I would appreciate your advices. Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] can start menu content depend on what components selected for install
I can't figure out how to generate a start menu that reflects my selection of installed components. This is for installation on windows using cmake, cpack and nsis. Is it possible to do? Regards Lars -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
