![]() ![]() I might be jumping the gun, but maybe my Windows journey is near the end: ![]() I am still looking for what is different between that plugin and, for example, smtkProjectManagerPlugin. The new smtkACE3PPlugin does not show up in the Plugin Manager, instead, the user has to find it the first time.So maybe we need an alternate I/O scheme for this reason as well. #PARAVIEW SUPERBUILD CODE#It seems as though sometimes the messages make it back to c code and sometimes they don’t. Related to that, I have observed inconsistency when writing to Operator::log() from python scripts.If this is a feature, I’ll need to come up with some alternate way to get logger data from scripts. Not a deal-breaker, but this will make debugging export scripts aot more difficult. In fact, the sys.stdout object is null (I presume sys.stderr is too). The Output Messages panel doesn’t display any text printed by python code running in operators.No such problem on linux, and I have not tried on macOS. When first creating a project, the model resource doesn’t get added to rendering pipeline.Oh, and for completeness, I want to add the other issues with the current windows build The command 'powershell -NoLogo -NoProfile -Command cd C:/Users/ContainerUser/build/cmb-superbuild/superbuild/smtk/build make -j6 install' returned a non-zero code: 1 Building CXX object smtk/CMakeFiles/smtkCore.dir/common/Ĭ:/Users/ContainerUser/build/cmb-superbuild/install/include/boost-1_71\boost/system/detail/system_category_win32.hpp(52): error C2039: '_snprintf': is not a member of 'std'Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\5\include\array(18): note: see declaration of 'std' Otherwise, if it is just intractable, I’ll go another way (even more klugy). If anyone knows the fix for this, please pass it along. #PARAVIEW SUPERBUILD PLUS#I tried the usual fix plus a few others that google suggested, but absolutely no way. The error message is for good old _snprintf. ![]() It builds no problem on linux but, of course, no way on windows. So I tried adding logger messages to PythonInterpreter.cxx to see what paths are getting added. Another increment today – I modified smtk to print out the python exception that occurs when importing python modules (with thanks to TJ): ImportPythonOperation.cxx:155 No module named 'smtk' ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |