![]() Found Python3: /usr/lib64/libpython3.6m.so (found suitable version "3.6", minimum required is "3.2") found components: Development paraview, I get a message during the build: SET(VTK_MPI_NUMPROCS "10" CACHE STRING "")įind_program(PYTHON_EXECUTABLE "/home/tjim/anaconda3/envs/testenv/bin/python3.7")īut again, on running cmake -C./testenv.cmake -GNinja. SET(VTK_SMP_IMPLEMENTATION_TYPE "TBB" CACHE STRING "") SET(CMAKE_BUILD_TYPE "Release" CACHE STRING "") SET(VTK_PYTHON_VERSION 3 CACHE STRING "") SET(PARAVIEW_PYTHON_VERSION "3" CACHE STRING "") SET(PARAVIEW_USE_PYTHON ON CACHE BOOL "") SET(PARAVIEW_ENABLE_FFMPEG ON CACHE BOOL "") cmake file instead and using find_program: set(CMAKE_INSTALL_PREFIX "/opt/paraview/ParaView-5.8.1_testenv" CACHE PATH "") I saw this, but if the flags don’t exist anymore, what did they become? Manually-specified variables were not used by the project: DPARAVIEW_ENABLE_FFMPEG=ON -DPARAVIEW_USE_MPI=ONīut CMake defaults to the system python 3.6 and reports: CMake Warning: DCMAKE_INSTALL_PREFIX=/opt/paraview/ParaView-5.8.1_testenv DPYTHON_INCLUDE_DIR=/home/tjim/anaconda3/envs/testenv/include/python3.7m ![]() DPYTHON_EXECUTABLE=/home/tjim/anaconda3/envs/testenv/bin/python3.7 I want to compile a PV install to use a specific Python interpreter and environment but the system Python keeps getting picked up instead.Ĭompiling v5.8.1 on CentOS 8, I used: cmake -GNinja DCMAKE_TOOLCHAIN_FILE=/path/to/generated/toolchain.cmake,īecause we have to use the toolchain file generated by qitoolchain.Įnter search terms or a module, class or function name.Hi, the flags used to specify the Python interpreter to CMake don’t seem to be working for me at the moment - or maybe I’m missing something. append ( 'CMAKE_TOOLCHAIN_FILE= %s ' % toolchain_path )įor instance, because of the -release command line option, we haveĪnd because we are using the foo-sdk toolchain, we have to set user_cmake_flags ) # add the toolchain file: if toc. append ( "CMAKE_BUILD_TYPE= %s " % ( toc. update_project ( project, self ) # in qibuild.project def update_project ( project, toc ): # Handle custom global build directory containing all projects singlebdir = toc. update_projects () def update_projects ( self ): for project in self. # in qibuild.toc class Toc : def _init_ ( self, cmake_flags = None, cmake_generator = None ): self. Possibly overwrite these with command line options.Possibly overwrite these defaults from various config files (the global qibuild.xmlĬonfig file, the local.Have sane defaults (for instance ‘Unix Makefiles’ for the cmake_generator). ![]() Toc constructor does a lot of stuff (this comes from the fact that the Toc class is huge). Well, that’s an other story, so more on this later. You may wonder why we we set the toc.active_projects here and not it Toc ctor. This decouples the Toc initialization from the command line parsing, which is a good Note how the argparse.NameSpace object is exploded to become explicit keyword arguments cmake_flags toc = Toc ( work_tree, config = config, build_type = build_type, cmake_flags = cmake_flags, cmake_generator = cmake_generator, path_hints = path_hints, qibuild_cfg = qibuild_cfg ) ( active_projects, single ) = _projects_from_args ( toc, args ) toc. # in _open def toc_open ( worktree, args ): # Lots of code like: cmake_flags = list () if hasattr ( args, 'cmake_flags' ): cmake_flags = args.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |