If you do need a recursive ninja call for some reason (you should try to not need this, really), then try giving that its own build directory (-C flag), then this specific problem should go away. That way, parallelism will work better, progress output will be correct, ninja can make better scheduling decisions, etc. Ideally, you'd manage to do things in that setup. ![]() Ninja isn't designed to be used in "recursive" mode - it's designed to load the whole build graph at startup, and to have a single ninja process in charge of everything. We're somewhat careful about this, and the two ninja processes shouldn't corrupt each other's state and nothing should crash (this used to be not true in older versions), but I'm guessing that there's some OS file locking thing going on here. ninja_deps), and the outer and inner ninjas will fight for writing to these files. In that setup the two ninjas share one build directory, right? That probably won't work very well: Ninja puts some files to keep state into the build dir (.ninja_log and. " terminated with exit code: 1.Ooooh I see, you're saying you're creating a cmake project that has a target that runs ninja, and then you call that via ninja! The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1. See also "G:/Test Projects/VS examples/blink/build/CMakeFiles/CMakeOutput.log". Configuring incomplete, errors occurred! Error 1Ĭ:/Users/djosh/esp/esp-idf/tools/cmake/build.cmake:528 (_kconfig_generate_config)Ĭ:/Users/djosh/esp/esp-idf/tools/cmake/project.cmake:378 (idf_build_process) > wrote: Hello, I installed the Visual Studio 2019 and still the same. ![]() Projects/VS examples/blink/sdkconfig -defaults G:/Test Projects/VSĮxamples/blink/faults -env-file G:/Test Projects/VSĮxamples/blink/build/config.env). Comments (1) CMake executable is cmake - ERROR: Failed building wheel for. (C:/Users/djosh/.espressif/python_env/idf4.4_p圓.8_env/Scripts/python.exe C:/Users/djosh/esp/esp-idf/tools/kconfig_new/confgen.py -kconfig C:/Users/djosh/esp/esp-idf/Kconfig -sdkconfig-rename C:/Users/djosh/esp/esp-idf/sdkconfig.rename -config G:/Test Kconfiglib._KconfigIOError: G:/Test Projects/VS examples/blink/build/kconfigs_projbuild.in:6: Could not open 'G:/Test' (in 'source "G:/Test"') (EACCES: Permission denied)ĬMake Error at C:/Users/djosh/esp/esp-idf/tools/cmake/kconfig.cmake:266 (message): Prev = self._parse_block(None, parent, prev)įile "C:\Users\djosh\.espressif\python_env\idf4.4_p圓.8_env\lib\site-packages\kconfiglib.py", line 2981, in _parse_blockįile "C:\Users\djosh\.espressif\python_env\idf4.4_p圓.8_env\lib\site-packages\kconfiglib.py", line 2190, in _enter_file ![]() Self._parse_block(None, self.top_node, self.top_node).next = Noneįile "C:\Users\djosh\.espressif\python_env\idf4.4_p圓.8_env\lib\site-packages\kconfiglib.py", line 2982, in _parse_block ![]() Self._init(filename, warn, warn_to_stderr, encoding)įile "C:\Users\djosh\.espressif\python_env\idf4.4_p圓.8_env\lib\site-packages\kconfiglib.py", line 1085, in _init įile "C:/Users/djosh/esp/esp-idf/tools/kconfig_new/confgen.py", line 260, in mainĬonfig = kconfiglib.Kconfig(args.kconfig)įile "C:\Users\djosh\.espressif\python_env\idf4.4_p圓.8_env\lib\site-packages\kconfiglib.py", line 947, in _init_ Here /97e63 is the non-writable file, which is clearly a bogus path. zip unpacked somewhere, launching cmake-gui via its full path, while the current working dir is the prj (build) root. Executing task: cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1. I'm running the CMake GUI from their (presumably 'portable').
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |