From: Daniel <bad...@ya...> - 2008-06-08 20:45:06
|
All: I had to update to CMake 2.6 because the Mandriva RPM of CMake 2.4 doesn't come with Modules/FindPackageHandleStandardArgs.cmake, which is called by FindEXPAT.cmake. Now, when I generate using CMake 2.6, I get some warnings that tell me to type the following command: cmake --help-policy CMP0004 for details. Doing so yields the following: CMP0004 Libraries linked may not have leading or trailing whitespace. CMake versions 2.4 and below silently removed leading and trailing whitespace from libraries linked with code like target_link_libraries(myexe " A ") This could lead to subtle errors in user projects. The OLD behavior for this policy is to silently remove leading and trailing whitespace. The NEW behavior for this policy is to diagnose the existence of such whitespace as an error. The setting for this policy used when checking the library names is that in effect when the target is created by an add_executable or add_library command. This policy was introduced in CMake version 2.6.0. CMake version 2.6 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly. So ... can I just assume that these are harmless warnings due to sloppy CMakeLists.txt files, and that CMake and make will eventually do the right thing? Or should I be worried about so-called "subtle errors in user projects?" Please advise. Thanks, Dan P.S. It appears the Mandriva RPM for CMake 2.6 has no cmake_policy command either. Is there an XML file somewhere I can hand edit to suppress these warnings in the future? |
From: Peter V. <pet...@ya...> - 2008-06-09 21:36:35
|
> CMake versions 2.4 and below silently removed leading and trailing > whitespace from libraries linked with code like > target_link_libraries(myexe " A ") The good news is that vxl has no leading or trailing blanks in any of its target_link_libraries. (Actually, there are even no quotes in any of the target_link_libraries). So nothing to worry about. -- Peter. __________________________________________________________ Går det långsamt? Skaffa dig en snabbare bredbandsuppkoppling. Sök och jämför hos Yahoo! Shopping. http://shopping.yahoo.se/c-100015813-bredband.html?partnerId=96914325 |
From: Amitha P. <ami...@us...> - 2008-06-10 13:47:06
|
Peter Vanroose wrote: > The good news is that vxl has no leading or trailing blanks in any of its target_link_libraries. (Actually, there are even no quotes in any of the target_link_libraries). > So nothing to worry about. Daniel: given this, does the warnings you get point out line numbers? My guess is that the warnings are being introduced through external libraries, and it'd be good to find out whether there is something we can do about it. (Most likely we'll just set the policy to the new way.) Amitha. |
From: Daniel <bad...@ya...> - 2008-06-11 05:50:10
|
Dopey me for not posting these in the first place. CMake Warning (dev) at core/vgui/CMakeLists.txt:477 (ADD_LIBRARY) Policy CMP0004 is not set: Libraries linked may not have leading or trailing whitespace. And also CMake Warning (dev) at core/vgl/examples/CMakeLists.txt:7 (ADD_EXECUTABLE) and CMake Warning (dev) at core/vgui/examples/CMakeLists.txt:7 (ADD_EXECUTABLE) I'm not sure what my CMake 2.6 rpm is smoking this week, because I don't see any quoted whitespace in any of these lines. So I'll take Peter's advice and ignore these warnings. They probably go away when I find and install the next Mandriva update to their rpm of CMake 2.6. Thanks, Dan --- On Tue, 6/10/08, Amitha Perera <ami...@us...> wrote: > From: Amitha Perera <ami...@us...> > Subject: Re: [Vxl-users] Whitespace warnings configuring with CMake 2.6 > To: p.v...@ie... > Cc: "Daniel" <bad...@ya...>, vxl...@li... > Date: Tuesday, June 10, 2008, 6:46 AM > Peter Vanroose wrote: > > The good news is that vxl has no leading or trailing > blanks in any of its target_link_libraries. (Actually, > there are even no quotes in any of the > target_link_libraries). > > So nothing to worry about. > > Daniel: given this, does the warnings you get point out > line numbers? > My guess is that the warnings are being introduced through > external > libraries, and it'd be good to find out whether there > is something we > can do about it. (Most likely we'll just set the > policy to the new way.) > > Amitha. |
From: Amitha P. <ami...@us...> - 2008-06-11 13:55:30
|
Thanks for the warning line numbers. Daniel wrote: > So I'll take Peter's advice and ignore these warnings. They probably go away when I find and install the next Mandriva update to their rpm of CMake 2.6. Okay. Let us know if that does magically solve the issue. I'll try to look into it more when I get the chance, but it'll be a very low priority for me, unfortunately. Amitha. |
From: Amitha P. <ami...@us...> - 2008-06-09 21:56:49
|
Daniel wrote: > I had to update to CMake 2.6 because the Mandriva RPM of CMake 2.4 doesn't come with Modules/FindPackageHandleStandardArgs.cmake, which is called by FindEXPAT.cmake. Odd. At least one dashboard build is done with CMake 2.4.7. What is the patch number of CMake 2.4 that you had? > Now, when I generate using CMake 2.6, I get some warnings that tell me to type the following command: > > cmake --help-policy CMP0004 > > for details. Again, odd, because many of our dashboard builds use CMake 2.6. Are you getting this error on vxl itself, or on your CMakeLists.txt files? What is the patch level of your CMake 2.6? (Run "cmake --version".) > P.S. It appears the Mandriva RPM for CMake 2.6 has no cmake_policy command either. That's hard to believe: cmake 2.6 introduced the cmake_policy command. Is there some dual installation of CMake 2.4 and CMake 2.6 going on? Amitha. |
From: Daniel <bad...@ya...> - 2008-06-09 22:25:18
|
--- On Mon, 6/9/08, Amitha Perera <ami...@us...> wrote: > From: Amitha Perera <ami...@us...> > Subject: Re: [Vxl-users] Whitespace warnings configuring with CMake 2.6 > To: "Daniel" <bad...@ya...> > Cc: vxl...@li... > Date: Monday, June 9, 2008, 2:56 PM > Daniel wrote: > > I had to update to CMake 2.6 because the Mandriva RPM > of CMake 2.4 doesn't come with > Modules/FindPackageHandleStandardArgs.cmake, which is > called by FindEXPAT.cmake. > > Odd. At least one dashboard build is done with CMake > 2.4.7. What is > the patch number of CMake 2.4 that you had? The official Mandriva release is up to CMake 2.4.8. This could be just an omission by whoever packaged up the Mandriva RPM. > > > Now, when I generate using CMake 2.6, I get some > warnings that tell me to type the following command: > > > > cmake --help-policy CMP0004 > > > > for details. > > Again, odd, because many of our dashboard builds use CMake > 2.6. Are you > getting this error on vxl itself, or on your CMakeLists.txt > files? What > is the patch level of your CMake 2.6? (Run "cmake > --version".) I don't understand the difference between 'getting this error on vxl itself', and 'on your CMakeLists.txt files'. The only CMakeLists.txt files I am dealing with come from vxl itself. I have not touched or modified them from the CVS checkout. Is that what you are asking? cmake version 2.6-patch 0 > > > P.S. It appears the Mandriva RPM for CMake 2.6 has no > cmake_policy command either. > > That's hard to believe: cmake 2.6 introduced the > cmake_policy command. > Is there some dual installation of CMake 2.4 and CMake 2.6 > going on? I believe I can answer this one. When I first read that warning message, I assumed that 'cmake_policy' was a *command line* program. I saw another warning message (CMP0003) that seemed to indicate cmake_policy is really a directive you put in your CMakeLists.txt file. I would try it, except suppressing warnings is generally a Bad Idea(tm). Thanks, Dan > > Amitha. |
From: Amitha P. <ami...@us...> - 2008-06-10 13:46:34
|
Daniel wrote: > The official Mandriva release is up to CMake 2.4.8. This could be just an omission by whoever packaged up the Mandriva RPM. Okay. Since you installed CMake 2.6, let's skip this issue for now. > I don't understand the difference between 'getting this error on vxl itself', and 'on your CMakeLists.txt files'. The only CMakeLists.txt files I am dealing with come from vxl itself. I have not touched or modified them from the CVS checkout. Is that what you are asking? That is what I'm asking. So, the error is coming from vxl's CMakeLists.txt files. Are you using a CVS checkout, or the last release? Amitha. |
From: Daniel <bad...@ya...> - 2008-06-11 02:25:49
|
It was a checkout from the day I posted the first message. I will grab a new one tonight and try building from that. It looks like the Brown people have been busy lately ... Thanks, Dan --- On Tue, 6/10/08, Amitha Perera <ami...@us...> wrote: > From: Amitha Perera <ami...@us...> > Subject: Re: [Vxl-users] Whitespace warnings configuring with CMake 2.6 > To: "Daniel" <bad...@ya...> > Cc: vxl...@li... > Date: Tuesday, June 10, 2008, 6:42 AM > Daniel wrote: > > The official Mandriva release is up to CMake 2.4.8. > This could be just an omission by whoever packaged up the > Mandriva RPM. > > Okay. Since you installed CMake 2.6, let's skip this > issue for now. > > > I don't understand the difference between > 'getting this error on vxl itself', and 'on > your CMakeLists.txt files'. The only CMakeLists.txt > files I am dealing with come from vxl itself. I have not > touched or modified them from the CVS checkout. Is that > what you are asking? > > That is what I'm asking. So, the error is coming from > vxl's > CMakeLists.txt files. Are you using a CVS checkout, or the > last release? > > Amitha. |