RESOLVED FIXED 90558
[CMake] Fix some CMake warnings
https://bugs.webkit.org/show_bug.cgi?id=90558
Summary [CMake] Fix some CMake warnings
Rob Buis
Reported 2012-07-04 08:36:27 PDT
CMake 2.8.5 reports warnings like this: Manually-specified variables were not used by the project: ENABLE_LINK_PRERENDER
Attachments
Patch (2.20 KB, patch)
2012-07-04 08:41 PDT, Rob Buis
no flags
Patch (2.77 KB, patch)
2012-07-04 14:51 PDT, Rob Buis
no flags
Patch (2.99 KB, patch)
2012-07-05 08:20 PDT, Rob Buis
dbates: review+
Rob Buis
Comment 1 2012-07-04 08:41:10 PDT
Raphael Kubo da Costa (:rakuco)
Comment 2 2012-07-04 14:18:23 PDT
Comment on attachment 150805 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=150805&action=review > ChangeLog:3 > + [BlackBerry] Fix some CMake warnings Shouldn't this rather have [CMake] instead of [BlackBerry] in the title? Other ports which use CMake have the same warnings.
Rob Buis
Comment 3 2012-07-04 14:20:41 PDT
Hi Raphael, (In reply to comment #2) > (From update of attachment 150805 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=150805&action=review > > > ChangeLog:3 > > + [BlackBerry] Fix some CMake warnings > > Shouldn't this rather have [CMake] instead of [BlackBerry] in the title? Other ports which use CMake have the same warnings. Yes, you are right, sorry! Do you feel like reviewing?
Raphael Kubo da Costa (:rakuco)
Comment 4 2012-07-04 14:37:45 PDT
Looks fine to me(In reply to comment #3) > Do you feel like reviewing? You probably also need to add the new flags to Source/cmakeconfig.h.cmake. I don't have reviewer superpowers, though :-(
Rob Buis
Comment 5 2012-07-04 14:51:12 PDT
Rob Buis
Comment 6 2012-07-04 14:52:18 PDT
Hi Raphael, (In reply to comment #4) > Looks fine to me(In reply to comment #3) > > Do you feel like reviewing? > > You probably also need to add the new flags to Source/cmakeconfig.h.cmake. I don't have reviewer superpowers, though :-( Thanks! I am not complete sure if our port needs the cmakeconfig.h.cmake addtion, but I did update it in my latest patch.
Raphael Kubo da Costa (:rakuco)
Comment 7 2012-07-04 16:34:47 PDT
(In reply to comment #6) > I am not complete sure if our port needs the cmakeconfig.h.cmake addtion, but I did update it in my latest patch. It might not need it now due to the features being disabled by default, but all CMake-based ports use that for the ENABLE() and USE() macros to work, otherwise the macro definitions will never be set. Shouldn't you set the WTF_* entries in cmakeconfig.h.cmake as well?
Rob Buis
Comment 8 2012-07-05 07:39:50 PDT
(In reply to comment #7) > (In reply to comment #6) > > I am not complete sure if our port needs the cmakeconfig.h.cmake addtion, but I did update it in my latest patch. > > It might not need it now due to the features being disabled by default, but all CMake-based ports use that for the ENABLE() and USE() macros to work, otherwise the macro definitions will never be set. Ok. > Shouldn't you set the WTF_* entries in cmakeconfig.h.cmake as well? You are right, however I do not see our port using these two in the near future. If you think your port will, I can add them?
Raphael Kubo da Costa (:rakuco)
Comment 9 2012-07-05 08:04:16 PDT
(In reply to comment #8) > > Shouldn't you set the WTF_* entries in cmakeconfig.h.cmake as well? > > You are right, however I do not see our port using these two in the near future. If you think your port will, I can add them? Right now it's mostly to make the patch consistent (otherwise even though the CMake warnings are fixed the other half of adding something to WebKitFeatures.cmake will not have been done).
Rob Buis
Comment 10 2012-07-05 08:20:42 PDT
Daniel Bates
Comment 11 2012-07-05 10:36:29 PDT
Comment on attachment 150943 [details] Patch r=me
Rob Buis
Comment 12 2012-07-05 11:13:25 PDT
Note You need to log in before you can comment on or make changes to this bug.