在这里，我们将给大家分享关于如何在Windows上将GoogleTestvariablesGTEST_LIBRARYGTEST_INCLUDE_DIR和GTEST_MAIN_LIBRARY设置为CMa

在这里，我们将给大家分享关于如何在Windows上将GoogleTestvariablesGTEST_LIBRARY GTEST_INCLUDE_DIR和GTEST_MAIN_LIBRARY设置为CMake？的知识，同时也会涉及到如何更有效地10 Interesting JavaScript and CSS Libraries for February 2020、c – cmake：我必须以哪种顺序指定TARGET_LINK_LIBRARIES、cmake find_package 中，include_directories，target_link_libraries 的值怎么知道？、cmake set_target_properties INCLUDE_DIRECTORIES在linux上被忽略的内容。

• 如何在Windows上将GoogleTestvariablesGTEST_LIBRARY GTEST_INCLUDE_DIR和GTEST_MAIN_LIBRARY设置为CMake？
• 10 Interesting JavaScript and CSS Libraries for February 2020
• c – cmake：我必须以哪种顺序指定TARGET_LINK_LIBRARIES
• cmake find_package 中，include_directories，target_link_libraries 的值怎么知道？
• cmake set_target_properties INCLUDE_DIRECTORIES在linux上被忽略

如何在Windows上将GoogleTestvariablesGTEST_LIBRARY GTEST_INCLUDE_DIR和GTEST_MAIN_LIBRARY设置为CMake？

有一个为Linux环境开发的项目。 现在我正试图在使用CMake的Windows上构build它。

我一直试图build立该项目，总是得到这个错误：

CMake Error at C:/Program Files(x86)/CMake/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:148 (message): Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY) Call Stack (most recent call first): C:/Program Files(x86)/CMake/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE) C:/Program Files(x86)/CMake/share/cmake-3.3/Modules/FindGTest.cmake:204 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) C:/Users/awy9/git/cmake_modules/modules/SigeoGTest.cmake:21 (find_package) C:/Users/awy9/git/cmake_modules/modules/SigeoInit.cmake:29 (include) CMakeLists.txt:12 (include)

我怎样才能设置这些variables现在在Windows上的这个项目上工作？

如何将C ++变体转换为JSON？

如何在linux内核空间获取当前小时（一天中的时间）

GUID的唯一性

如何使Qt Widget填充父窗口小部件？

在Mac OS X上安装第三方C库

从Windows服务获取用户根目录

如何locking并强制用户重新input自己的Windows密码？

错误：在我的Makefile中“混合隐式和静态模式规则”

如何使脚本在Linux使用我的interpteter和工作？ （＃！）

使用MinGW生成在64位系统上编译一个32位的exe文件 – 编译一个32位的exe文件，但链接到64位的dll

UPDATE

@Tsyvarev帮我解决了第一个问题，我引用他的话：

这是标准的CMake消息，当没有找到请求的包（GTest在你的情况下）。 您应该在配置您的项目之前安装GTest。 或者，如果您已经将其安装到非标准位置，请通过GTEST_ROOT变量传递此位置：cmake -DGTEST_ROOT = …

作为cmake传递变量的替代方法，可以设置环境变量：set GTEST_ROOT =

这解决了与GTEST_INCLUDE_DIR的值的问题 ，但我仍然有这些错误：

CMake错误在C：/ Program Files（x86）/CMake/share/cmake-3.3/modulees/FindPackageH andleStandardArgs.cmake：148（消息）：无法找到GTest（缺少：GTEST_LIBRARY GTEST_MAIN_LIBRARY）

解

我认为，在Windows环境下，一些价值观与手册所说的不同。

编译Gtest后，我得到了两个库：gtest.lib和gtest_main.lib然后，我设置这些文件路径变量：

GTEST_LIBRARY = C： Users awy9 Softwares Gtest gtest-1.7.0 Debug gtest.lib GTEST_MAIN_LIBRARY = C： Users awy9 Softwares Gtest gtest-1.7.0 Debug gtest_main.lib

现在一切正常！

谢谢

10 Interesting JavaScript and CSS Libraries for February 2020

https://tutorialzine.com/2020/02/10-interesting-javascript-and-css-libraries-for-february-2020

Our mission at Tutorialzine is to keep you up to date with the latest and coolest trends in web development. That’s why every month we release a handpicked collection of some of the best resources that we’ve stumbled upon and deemed worthy of your attention.

If you enjoy these articles, make sure to subscribe to Dev Awesome. It is our biweekly newsletter where we share cool new libraries, articles, and free design resources!

A-Frame

A-frame is one of the most popular and feature-packed VR frameworks out there. It''s based on web technologies like HTML and JS, so it''s super easy to get into, while at the same time offering support for most major VR platforms like Vive and Rift. It recently had its official v1.0.0 release and is better than ever.

React Nice Dates

Touch-friendly datepicker for React with a beautiful design. The library is fully modular, consisting of separate components and utilities which can be mix-and-matched to create the perfect date picker for your needs.

Snowpack

Revolutionary new tool for bundling JavaScript dependencies. Unlike Webpack and other bundlers, which recompile your assets after every file change, Snowpack does only an initial setup. After everything is compiled, any new changes to your code will be instantly available without a build step.

Craft.js

Great React framework that helps you create user-friendly page editors. It makes it possible to change the content of a web page using drag & drop, detailed text controls, media embeds, and more. Perfect for building content management systems and WYSIWYG apps.

Yarn 2

Yarn offers an excellent alternative to NPM with a number of great features like module caching for using it offline and "flat mode" that works great to reduce duplicating packages. The project just released a new major update so make sure to check it out.

Playwright

Playrwight is an awesome node library by the Microsoft team for building automated write-once-run-everywhere UI tests. It covers most browsers that are based on Chromium, WebKit and Firefox, as well as all the major operating systems. The API is really clean and easy to work with, so that you can quickly open pages, manipulate them, and take screenshots.

VoxelSpace

Interesting GitHub repo for an infinite terrain generator created from scratch. The source code has plenty of comments and is easy to follow, plus the rendering algorithm itself is very well explained in the readme. You can check out the demo here.

Web Extension Starter

This is a really handy starter kit for creating multi-browser web extensions. It makes it super easy to build web addons for Chrome, Firefox and Opera out of the same code base. The kit covers browser specific APIs, manifests, and build files, to make sure your plugin works everywhere.

Mirage

Powerful API mocking library for writing tests without having an actual backend. Mirage can be configured to recreate complex dynamic scenarios, typically only possible when using a real production server. The setup can then be shared with the rest of your codebase so that the tests run on all teammates'' machines.

Panzoom

As the name suggests, Panzoom is a framework for handling pan and zoom actions in your apps. It works great on mobile, supports both DOM elements and SVGs, and offers plenty of customization options.

c – cmake：我必须以哪种顺序指定TARGET_LINK_LIBRARIES

libA depends on boost
libB depends on postgresql and libA (and therefore on boost)
myTarget uses libA,libB and boost directly (and through libB depends on postgresql)

TARGET_LINK_LIBRARIES(${ApplicationName}  

libboost_program_options.a 
libboost_system.a 
libboost_filesystem.a 
libboost_date_time.a 
libboost_regex.a 

# Should include all boost libraries but strangely some libs (the ones above)
# need to be specified "by hand"???
${Boost_LIBRARIES} 

# Postgresql stuff
libpq.a
libsoci_core.a
libsoci_postgresql.a
libpq.so

# My libs
libB.a
libA.a

${CMAKE_THREAD_LIBS_INIT} # pthreads,needed by boost
${CMAKE_DL_LIBS} # For libdl.so etc.
)

SET(Boost_USE_STATIC_LIBS ON)

TARGET_LINK_LIBRARIES(${ApplicationName}  
libB.a
libA.a

# Postgresql stuff
libpq.a
libsoci_core.a
libsoci_postgresql.a
libpq.so

# Boost
libboost_program_options.a 
libboost_system.a 
libboost_log.a 
libboost_filesystem.a 
libboost_date_time.a 
libboost_regex.a 
# Should include all boost libraries but strangely some libs (the ones above)
# need to be specified "by hand"???
${Boost_LIBRARIES} 

# Lowlevel needed by boost
${CMAKE_THREAD_LIBS_INIT} # pthreads,needed by boost
${CMAKE_DL_LIBS} # For libdl.so etc.
)

find_package(Boost COMPONENTS date_time filesystem system ...)
find_package(Postgresql required)
IF(Boost_FOUND AND Postgresql_FOUND)
  INCLUDE_DIRECTORIES(${Boost_INCLUDE_Dirs})
  INCLUDE_DIRECTORIES(${Postgresql_INCLUDE_Dirs})

  # ApplicationName -> your_application
  # LIB_A_TARGET -> libA
  # LIB_B_TARGET -> libB

  SET(LIB_A_ALL_DEPS ${Boost_LIBRARIES})
  SET(LIB_B_ALL_DEPS ${LIB_A_ALL_DEPS} ${Postgresql_LIBRARIES})

  SET(EXTRA_APP_DEPS  ) # here all your extra libs that they aren't in boost or postgre

  SET(YOUR_APP_ALL_DEPS ${LIB_A_ALL_DEPS} ${LIB_B_ALL_DEPS} ${EXTRA_APP_DEPS})

  # Here'll be all your ADD_EXECUTABLE,ADD_LIBRARY code

  TARGET_LINK_LIBRARIES(${LIB_A_TARGET} ${LIB_A_ALL_DEPS})
  ADD_DEPENDENCIES(${LIB_A_TARGET} ${LIB_A_ALL_DEPS})

  TARGET_LINK_LIBRARIES(${LIB_B_TARGET} ${LIB_B_ALL_DEPS})
  ADD_DEPENDENCIES(${LIB_B_TARGET} ${LIB_B_ALL_DEPS})

  TARGET_LINK_LIBRARIES(${ApplicationName} ${YOUR_APP_ALL_DEPS})
  ADD_DEPENDENCIES(${ApplicationName} ${YOUR_APP_ALL_DEPS})
ENDIF()

cmake find_package 中，include_directories，target_link_libraries 的值怎么知道？

拿 Sophus 库为例：

find_package(Sophus REQUIRED)

include_directories(${Sophus_INCLUDE_DIRS})

target_link_libraries(useSophus ${Sophus_LIBRARIES})

我们怎么知道要连接 Sophus_INCLUDE_DIRS，Sophus_LIBRARIES，而不是 SOPHUS_INCLUDE_DIRS，SOPHUS_LIBRARIES 或其他，其实

find_package 主要是找到.cmake 文件，然后这些变量在.cmake 里面定义了，我们看 Sophus/SophusConfig.cmake：

# Sophus source dir

set( Sophus_SOURCE_DIR "/home/xxx/slamcode/ch4/Sophus")

################################################################################

# Sophus build dir

set( Sophus_DIR "/home/xxx/slamcode/ch4/Sophus")

################################################################################

set( Sophus_INCLUDE_DIR  "/home/xxx/slamcode/ch4/Sophus;/usr/include/eigen3" )

set( Sophus_INCLUDE_DIRS  "/home/xxx/slamcode/ch4/Sophus;/usr/include/eigen3" )

set( Sophus_LIBRARIES    "/home/xxx/slamcode/ch4/Sophus/libSophus.so" )

set( Sophus_LIBRARY      "/home/xxx/slamcode/ch4/Sophus/libSophus.so" )

set( Sophus_LIBRARY_DIR  "/home/xxx/slamcode/ch4/Sophus" )

set( Sophus_LIBRARY_DIRS "/home/xxx/slamcode/ch4/Sophus" )

然后就知道那些变量可以用了吧

cmake set_target_properties INCLUDE_DIRECTORIES在linux上被忽略