Building CXX object CMakeFiles/arguments.dir/Tests/Ĭ:\Users\nimajneb.000\Dropbox\CS5310\arguments\main.cpp: In function 'int main(int, char**)':Ĭ:\Users\nimajneb.000\Dropbox\CS5310\arguments\main.cpp:6:20: warning: ignoring return value of 'int RUN_ALL_TESTS()', declared with attribute warn_unused_result Building CXX object CMakeFiles/arguments.dir/ Scanning dependencies of target arguments "C:\Program Files\JetBrains\CLion 2017.1.1\bin\cmake\bin\cmake.exe" -build C:\Users\nimajneb.000\Dropbox\CS5310\arguments\cmake-build-debug -target arguments -j 8 What I don't understand is why the linker can't seem to find the library files for gtest and gtest_main. The shared DLLs are not being found when I attempt to exe the project binaries from the command line instead of running from Clion. The static linking is due to some path issues with the WinBuilds install. # "C:/Users\nimajneb.000/Dropbox/CS5310/googletest/google-distribution/lib/libgtest_main.dll.") # "C:/Users\nimajneb.000/Dropbox/CS5310/googletest/google-distribution/lib/" Target_link_libraries( arguments gtest gtest_main) Set( CMAKE_EXE_LINKER_FLAGS " $ Tests/ClassName.h Tests/test.cpp) Set( CMAKE_STATIC " -static-libgcc -static-libstdc++ -static") I've then attempted to add the external library to my test project with the following modifications to the CMakeLists.txt: cmake_minimum_required( VERSION 3.7) To that end, I've downloaded googletest from github, built it externally to Clion via CMake and mingw (64bit), and setup a google-distribution directory, containing the includes and lib files. I'm attempting to get gtest up and running so that I can unit test my projects. How to update Python version from 3.67 to 3.I'm something of a CMake and CLion newb, so bare with me.How to update Slicer's Python version from 3.6.7 to 3.7?.See a static build of Qt 5.15.2 for macOS. Transition the macOS continuous integration from TravisCI to GitHub Actionsįixed an issue happening when building the launcher against Qt >= 5.14. This is consistent with the Slicer macOS deployment target being 10.13. Updated the deployment target of the pre-build macOS binary package from 10.6 (Snow Leopard, released in 2009) to 10.13 (High Sierra, release in 2017). Last, note that the plan is to contribute this changes updating the existing pull request ( PR-535 - Add cmake configuration files) To address this, we now have a fork of the project adding CMake support. To address this in Slicer, we added two modules generated by SuperBuild/python_configure_python_launcher.cmake:Īdditionally, since starting with CPython 3.7 on Linux, and CPython 3.8 on Windows, the LibFFI dependencies is not included anymore in CPython sources anymore. (Contributed by Steve Dower in bpo-36085.) Note that Windows 7 users will need to ensure that Windows Update KB2533623 has been installed (this is also verified by the installer). If your application relies on these mechanisms, you should check for add_dll_directory() and if it exists, use it to add your DLLs directory while loading your library. Specifically, PATH and the current working directory are no longer used, and modifications to these will no longer have any effect on normal DLL resolution. Only the system paths, the directory containing the DLL or PYD file, and directories added with add_dll_directory() are searched for load-time dependencies. This snippet from the porting notes is particularly relevant:ĭLL dependencies for extension modules and DLLs loaded with ctypes on Windows are now resolved more securely. Starting with CPython 3.8, the directories associated with dependencies of compiled python modules are expected to be added using the os.add_dll_directory function from the CPython standard library. BUG: Fix compiled python module import on windows
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |