vite:build-html EISDIR: illegal operation on a directory, read - github

`npm run build
hiddal.com#0.0.0 build
vite build
vite v4.1.1 building for production...
✓ 0 modules transformed.
[vite:build-html] EISDIR: illegal operation on a directory, read
file: C:/Users/hgale/alexanderhdev/Hiddal/hiddal.com/index.html
error during build:
Error: EISDIR: illegal operation on a directory, read
I still couldn't find solutions because I can't understand the error`

Related

I cannot initialize my project on Visual Studio Code using the PlatformIO

I am using Visual Studio Code and added the PlatformIO IDE extension along with c/c++ to code for my board, which is a uPesy ESP32 Wrovoer DevKit with a Espressif IoT Developement framework. Everything matches my but when I click finish I get an error message:
The current working directory C:\Users\brownme1\Documents\PlatformIO\Projects\my_project will be used for the project.
The next files/directories have been created in C:\Users\brownme1\Documents\PlatformIO\Projects\my_project
include - Put project header files here
lib - Put here project specific (private) libraries
src - Put project source files here
platformio.ini - Project Configuration File
Resolving upesy_wrover dependencies...
Already up-to-date.
Updating metadata for the vscode IDE...
Error: Processing upesy_wrover (platform: espressif32; board: upesy_wrover; framework: espidf)
--------------------------------------------------------------------------------
Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/upesy_wrover.html
PLATFORM: Espressif 32 (6.0.0) > uPesy ESP32 Wrover DevKit
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-espidf # 3.50000.0 (5.0.0)
- tool-cmake # 3.16.4
- tool-esptoolpy # 1.40400.0 (4.4.0)
- tool-idf # 1.0.1
- tool-mconf # 1.4060000.20190628 (406.0.0)
- tool-ninja # 1.9.0
- toolchain-esp32ulp # 1.23500.220830 (2.35.0)
- toolchain-xtensa-esp32 # 11.2.0+2022r1
Reading CMake configuration...
-- Could NOT find Git (missing: GIT_EXECUTABLE)
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/brownme1/.platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc.exe
-- Check for working C compiler: C:/Users/brownme1/.platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc.exe
-- Check for working C compiler: C:/Users/brownme1/.platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc.exe -- broken
-- Configuring incomplete, errors occurred!
See also "C:/Users/brownme1/Documents/PlatformIO/Projects/my_project/.pio/build/upesy_wrover/CMakeFiles/CMakeOutput.log".
See also "C:/Users/brownme1/Documents/PlatformIO/Projects/my_project/.pio/build/upesy_wrover/CMakeFiles/CMakeError.log".
CMake Warning at C:/Users/brownme1/.platformio/packages/framework-espidf/tools/cmake/git_submodules.cmake:4 (message):
Git executable was not found. Git submodule checks will not be executed.
If you have any build issues at all, start by adding git executable to the
PATH and rerun cmake to not see this warning again.
Call Stack (most recent call first):
C:/Users/brownme1/.platformio/packages/framework-espidf/tools/cmake/idf.cmake:41 (include)
C:/Users/brownme1/.platformio/packages/framework-espidf/tools/cmake/project.cmake:12 (include)
CMakeLists.txt:2 (include)
CMake Error at C:/Users/brownme1/.platformio/packages/tool-cmake/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
The C compiler
"C:/Users/brownme1/.platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc.exe"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: C:/Users/brownme1/Documents/PlatformIO/Projects/my_project/.pio/build/upesy_wrover/CMakeFiles/CMakeTmp
Run Build Command(s):C:/Users/brownme1/.platformio/packages/tool-ninja/ninja.exe cmTC_0ae29 && [1/2] Building C object CMakeFiles\cmTC_0ae29.dir\testCCompiler.c.obj
FAILED: CMakeFiles/cmTC_0ae29.dir/testCCompiler.c.obj
C:\Users\brownme1\.platformio\packages\toolchain-xtensa-esp32\bin\xtensa-esp32-elf-gcc.exe -mlongcalls -Wno-frame-address -o CMakeFiles\cmTC_0ae29.dir\testCCompiler.c.obj -c testCCompiler.c
xtensa-esp32-elf-gcc.exe: fatal error: cannot execute 'c:/users/brownme1/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/11.2.0/../../../../xtensa-esp32-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
C:/Users/brownme1/.platformio/packages/framework-espidf/tools/cmake/project.cmake:342 (__project)
CMakeLists.txt:3 (project)
========================== [FAILED] Took 4.21 seconds ==========================
Please try to read the error carefully. It says you're missing git.
Git executable was not found. Git submodule checks will not be executed.
If you have any build issues at all, start by adding git executable to the
PATH and rerun cmake to not see this warning again.

Not able to compile swift on Ubuntu 18.04

I installed swift toolchain using instructions from swift.org. While compiling helloworld code I am getting below error.
warning: 'helloworld': failed loading cached manifest for 'helloworld': disk I/O error
error: 'helloworld': Invalid manifest
<unknown>:0: error: unable to open output file '/usr2/xyz/.cache/clang/ModuleCache/IJ5GUC7XMAO5/SwiftShims-1TLN9ZL6HKTHR.pcm': 'No such file or directory'
<unknown>:0: error: could not build C module 'SwiftShims'
I tried removing '/usr2/xyz/.cache/clang/ModuleCache', but did not work. Please help in resolving this issue.

Exception: Gradle build failed to produce an .apk file. It's likely that this file was generated under C:\Users\airbu but the tool couldn't find it

Exception: Gradle build failed to produce an .apk file. It's likely that this file was generated under C:\Users\airbu\Desktop\KREAAPPS\hotel_booking_app\build, but the tool couldn't find it.

Yocto 2.4.2 failed to do_package_qa task

I am working with Yocto project version Rocko 2.4.2, Linux LTS4.4, cortexA15 ARM arch
When I bitbake weston package (v2.0), the error generated
ERROR: weston-2.0.0-r0 do_package_qa: QA Issue: /usr/lib/libweston-2/gl-renderer.so contained in package libweston-2 requires libGLESv2.so, but no providers found in RDEPENDS_libweston-2? [file-rdeps]
ERROR: weston-2.0.0-r0 do_package_qa: QA Issue: /usr/bin/weston-simple-egl contained in package weston-examples requires libGLESv2.so, but no providers found in RDEPENDS_weston-examples? [file-rdeps]
ERROR: weston-2.0.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: weston-2.0.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/server-build/RZG_YoctoProject/build/tmp/work/cortexa15hf-neon-poky-linux-gnueabi/weston/2.0.0-r0/temp/log.do_package_qa.8133
ERROR: Task (/home/server-build/RZG_YoctoProject/build/../poky/meta/recipes-graphics/wayland/weston_2.0.0.bb:do_package_qa) failed with exit code '1'
I tried to set "RDEPENDS_weston-examples = "libGLESv2" but it's still failed.
ERROR: Nothing RPROVIDES 'libGLESv2' (but /home/server-build/RZG_YoctoProject/build/../poky/meta/recipes-graphics/wayland/weston_2.0.0.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'libGLESv2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['libGLESv2']
ERROR: Required build target 'weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['weston', 'libGLESv2']
This error happened due to new structure and syntax of Yocto 2.4.2.
Anyone who is running into the same issue ?
Thanks for any help.

Intel XDK Google + google services plugin - build fails

I have developed a working hybrid application in which I am using "phonegap-googlemaps-plugin". This plugin needs as a dependency two other which downloads and installs automatically in the project. The dependencies are:
com.google.playservices and plugin.http.request
Using the Cordova-CLI, installing this plugin with the dependencies will fail building the project the 1st time because of a specific directory in the "playservices" plugin. To overcome this, I have to run "ant clean" in my project and also remove/rename that directory. Now, I am using Intel XDK and uploaded my app and installed most of my plugins successfully and run the application on my device. When I am trying to install the google play services plugin, it fails to build because of the reason I described above (I've run through the logs). How can I overcome this issue now?
I have attached the part of the log that shows the fail error
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[aapt] invalid resource directory name: .../App/platforms/android/com.google.playservices/google-play-services_lib/bin/res/crunch
BUILD FAILED
/Developer/android-sdk-linux/tools/ant/build.xml:653: The following error occurred while executing this line:
/Developer/android-sdk-linux/tools/ant/build.xml:698: null returned: 1
Total time: 5 seconds
Error code 1 for command: ant with args: release,-f,.../App/platforms /android/build.xml,-Dout.dir=ant-build,-Dgen.absolute.dir=ant-gen
Command finished with error code 2: .../App/platforms/android/cordova/build --release
Error: .../App/platforms/android/cordova/build: Command failed with exit code 2
at ChildProcess.whenDone (/Developer/cordova/3.5.0-0.2.7/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
Thanks in advance.