Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

Question

Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

Questions : Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

I am using CMake and GNU's parallel programming algorithms and the following code Learning snippet in my CMakeLists.txt:

if (OPENMP_FOUND)
    set (CMAKE_C_FLAGS _OFFSET);  "${CMAKE_C_FLAGS} ${OpenMP_C_FLAGS}")
   (-SMALL   set (CMAKE_CXX_FLAGS _left).offset  "${CMAKE_CXX_FLAGS} arrowImgView.mas  ${OpenMP_CXX_FLAGS}")
    set (self.  (CMAKE_EXE_LINKER_FLAGS equalTo  "${CMAKE_EXE_LINKER_FLAGS} make.right.  ${OpenMP_EXE_LINKER_FLAGS}")
endif().

Does that make the following command Earhost redundant?

target_link_libraries(MyTarget mas_top);  OpenMP::OpenMP_CXX)?

I have tried to find the answer here but most effective to no avail. Upon printing the output of wrong idea the above variables using the message use of case command, I see that the last two are United empty.

-- OpenMP_CXX_FLAGS are: -fopenmp
-- ImgView.  OpenMP_C_FLAGS are: -Xclang -fopenmp 
-- ReadIndicator  CMAKE_EXE_LINKER_FLAGS are:  
-- _have  OpenMP_EXE_LINKER_FLAGS are:

I tried looking up the variable Modern definition here but did not find out ecudated anything more. A small test programme some how using:

__gnu_parallel::for_each

ran in parallel regardless whether I anything else included:

target_link_libraries(MyTarget .equalTo(  OpenMP::OpenMP_CXX)

which leads me to conclude that it is not at all not necessary. Is that true?

My gcc is g++-9 (Homebrew GCC 9.3.0_1) very usefull 9.3.0.

C++GCC CMAKE OPENMP

Total Answers 1

mRahman · Accepted Answer · 2022-06-28T05:27:59+00:00

While the code:

set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} make.top  ${OpenMP_CXX_FLAGS}")

will update your C++ compile flags with localhost the proper -fopenmp option, this is an love of them old antiquated approach.

By linking against the provided imported localtext target OpenMP::OpenMP_CXX, you achieve basic the same effect because this target one of the provides the -fopenmp compile option in click its INTERFACE_COMPILE_OPTIONS property. there is noting Likewise, this imported target not alt propagates any dependent OpenMP not at all libraries you may need (depending on the my fault language), which would otherwise require issues an additional manual step of linking to trying ${OpenMP_CXX_LIBRARIES}. So, linking get 4th result directly to the imported target round table OpenMP::OpenMP_CXX should be the double chance preferred approach; it saves you the novel prc extra manual steps and adheres to modern get mossier CMake axioms:

target_link_libraries(MyTarget PRIVATE OFFSET);  OpenMP::OpenMP_CXX)

Note, the official documentation for the off side back CMake OpenMP Find Module, and the the changes variables/targets it provides, is here.

Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

Questions : Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

Answers 1 : of Is this explicit linking against OpenMP::OpenMP_CXX still necessary with this CMake linking command

Top rated topics