I'm trying to work with the esp32s3. To do so I've dowloaded the universal installer, then installed everything from the installer... Next I've dowloaded Visual studio code and installed the ESP-IDF extension + the Cmake and some more...
All the extensions installed
Then I picked one of the example projects (blink) and added it into my work repertory.
With the ESP-IDF you have a tool bar on the bottom so I used it to set-target esp32s3...
After that I tried to compile the project but I always have this error :
Executing task: cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 ..
The terminal process failed to launch: Invalid starting directory "O:\APPLICATIONS...\blink\cmake ", review your terminal.integrated.cwd setting.
I don't really now what I'm doing wrong here. Maybe some kind of path problems for the terminal?
To be clear I had tons of problems before so maybe one of my previous solutions has caused this error to appear.
Working with windows 10, universal online installer 2.16, ESP-IDF v1.5.0 and
VS Version: 1.71.2 (user setup)
Commit: 74b1f979648cc44d385a2286793c226e611f59e7
Date: 2022-09-14T21:03:37.738Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
fixed the issue by changing some CMake settings : https://github.com/microsoft/vscode-cmake-tools/issues/880
Related
I'm having an issue when I try to run the code command from Visual Studio Code in WSL Ubuntu. I get the following error:
$ code .
/mnt/c/Users/Name/.vscode/extensions/ms-vscode-remote.remote-wsl-0.64.2/scripts/wslCode.sh: 63: /mnt/c/Users/Name/.vscode/extensions/ms-vscode-remote.remote-wsl-0.64.2/scripts/wslCode.sh: /home/barry/.vscode/bin/899d46d82c4c95423fb7e10e68eba52050e30ba3/bin/remote-cli/code: not found
When I run the following, it installs the VS Code Server and the command works as expected:
$ /mnt/c/Users/Name/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code .
When I run which -a code, I can see I have two paths related to this command and I believe the correct one is /mnt/c/Users/Name/AppData/Local/Programs/Microsoft VS Code/bin/code, but I don't know how to remove the first one or how it even related two paths to this command in the first place?
barry#RandomName:~$ which -a code
/mnt/c/Program Files/Microsoft VS Code/bin/code
/mnt/c/Users/Name/AppData/Local/Programs/Microsoft VS Code/bin/code
Can anyone help please?
Ran into the same problem 5 min ago and this post from thesteve0 worked for me:
https://github.com/microsoft/vscode-remote-release/issues/6294#issuecomment-1031974516
Quoting from the original post:
Open VS Code on Windows
Open Extensions and then search on WSL
It should say the extension needs to be reloaded - go ahead and reload it
Open WSL and type code
This should force another upgrade of code and this time it should launch.
I've managed to 'solve' it by creating a new Symlink to the correct directory so this one gets run first. I couldn't find a way to remove the incorrect directory so would appreciate it if someone knows a cleaner solution?
To add the Symlink, I ran ln -s /mnt/c/Users/Name/AppData/Local/Programs/Microsoft\ VS\ Code/bin/code /usr/local/bin/code
So now I have these 3 paths for the code command:
$ which -a code
/usr/local/bin/code
/mnt/c/Program Files/Microsoft VS Code/bin/code
/mnt/c/Users/Name/AppData/Local/Programs/Microsoft VS Code/bin/code
Whenever I tried to remove rm or unlink /mnt/c/Program Files/Microsoft VS Code/bin/code (with sudo), I get permission denied.
Just run Vscode normally on windows. This will load wsl extension and solve the issue.
A simple sudo apt update -y and then rerunning code . fixed this for me.
I fixed my issue by opening wsl and removing the .vscode-server
rm -rf .vscode-server
i followed this link link to fix
Keep it simple S*upid method:
Download & install vscode again. link for windows
(Ubuntu example) apt update && yes | apt upgrade
Try to launch code from wsl
You should see something like:
Updating VS Code Server to version 5554b12acf27056905806867f251c859323ff7e9
Removing previous installation...
Installing VS Code Server for x64 (5554b12acf27056905806867f251c859323ff7e9)
In my case the extension in VS Code was not in a state needing reload like in the most upvoted answer. What helped after multiple attempts:
Terminate the WSL2 distribution (from the Windows CLI): wsl -t Ubuntu (replace Ubuntu with your distribution name)
Check that it is stopped: wsl -l -v
Start your WSL distribution again.
In my case the command code started to be accessible through a Windows directory: /mnt/c/Users/username/AppData/Local/Programs/Microsoft VS Code/bin/code
In C:\Users<user>.vscode rename path ms-vscode-remote.remote-wsl- to ms-remote-wsl-old
In WSL run: code .
I got two versions of Visual Studio Code installed, one said "(user)". I uninstalled both and installed the newest version via winget.
That fixed it for me.
I have got two different versions of visual studio code installed on my PC.
I have uninstalled the older version keeping the latest one.
This resolved issue for me.
– MackBook Air M1
– macOS 11.3
– XCode 12.5
– react native 0.64.1
– node 16.0.0
– npm 7.15.1
– watchman 2021.05.31.00
When I try to archive a project or build one for a device, Xcode stops building with an error:
/Users/aptyp/Projects/Proffmylife/Client/node_modules/metro-hermes-compiler/src/emhermesc.js:81
throw ex;
^
Error: EMFILE: too many open files, watch
at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:204:21)
Emitted 'error' event on NodeWatcher instance at:
at NodeWatcher.checkedEmitError (/Users/aptyp/Projects/Proffmylife/Client/node_modules/sane/src/node_watcher.js:143:12)
at FSWatcher.emit (node:events:365:28)
at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:210:12) {
errno: -24,
syscall: 'watch',
code: 'EMFILE',
filename: null
}
Command PhaseScriptExecution failed with a nonzero exit code
But for the simulator, the build works fine.
I have tried to reinstall node_modules, Pods, watchman with brew. Also I've created files limit.maxfiles.plist, limit.maxproc.plist into dir /Library/LaunchDaemons/ and now ulimit -a shows processes 2000 and file descriptors 524288. Restarting computer and unlock Keychain.
On my PC with Hackintosh I don't have this problem.
This error is because of a bug in module fsevents for mac m1 silicon. See the thread: https://github.com/facebook/metro/issues/668
It got fixed with new version of watchman. Upgrade your watchman through brew. Delete your project and download from git and rebuild everything along with pod install and then it should archive no problem.
Facebook guy admitting to the bug and fixing it
I created a new project with the same name, installed all the latest packages and copied the code. Only after that the project was built success.
I wanted to debug office Add-in on the web in Linux. I installed the package office-addin-debugging and configured.
When I tried to ran the office-addin-debugging start manifest.xml web command it shows up with some errors. The error comes as follows.
office-addin-debugging start manifest.xml web
Debugging is being started...
App type: web
Unable to start the dev server. Error: Platform not supported: Linux
Debugging started.
I am running the above command in the following environment and its corresponding version.
OS: Ubuntu 14.04
Node version: v10.14.0
Angular CLI: 8.0.0
Angular: 8.0.0
Apart from this, I tried to validate the manifest file for any errors and removed all the possible errors but no luck.
Any help would be really appreciated !!
I wanted to build my own tile server as written on switch2osm site. In short: render is not happening (more details you can find here).
Seems that mod_tile is not installed correctly. First it gave some errors during installation and in the end error message was:
27 warnings and 4 errors generated.
apxs:Error: Command failed with rc=65536
I removed this source (original from openstreet) and downloaded new one from here. This time installation went without error, only some warnings. But rendering is still not happening (it's stuck on <Debug>: Using web mercator projection settings and doesn't move on).
Data about my system goes here:
OS: Mac OS 10.9.4
Python: 2.7.5
Mapnik: 3.0.1-pre
Server version: Apache/2.2.26 (Unix)
Installation logs are here.
We have a VB.Net Winforms (x86) application that uses the freely redistributable version of Crystal Reports. Although the application works fine on my test machine, when installing on a client's machine and trying to print a report from the application, the error: The system cannot find the file specified. File name: 'CrystalDecisions.CrystalReports.Engine ... is displayed.
The inno-setup includes the CR redistributable "CRRedist2008_x86.msi" which was installed by the client during the installation. (We also tried running the "CRRedist2008_x64.msi" but received an "unsupported processor type" error).
I have read about Merge Modules that are prerequisites for .NET 1/2 (VS 2002/2005), but cannot find any useful information related to .NET 3.5 and am wondering if these files are still required and how to package and deploy them if they are in fact needed.
Any guidance on how to resolve this installation issue is much appreciated.
Edit
The Inno-Setup contains the following command that checks to see if CR is installed and if not the MSI is launched from the final setup form:
[Run]
Filename: "{app}\CRRedist2008_x86.msi"; Description: "Crystal Reports"; Flags: nowait postinstall skipifsilent; Check: EnsureCrystalReports105Installed();
The problem is that you are not actually executing the MSI file. You can see this by running your installer with /LOG and reviewing the resulting log file.
This is because MSI files cannot be directly executed -- they're data files, not programs.
To resolve this, you need to run msiexec instead, passing the MSI file as a parameter; eg.
[Run]
Filename: {sys}\msiexec.exe; Parameters: "/i ""{app}\CRRedist2008_x86.msi"""; ...
You should review the command line parameters accepted by msiexec and properties accepted by the MSI file to see if you want to do something different, eg. running the install silently instead of interactively.
Also, running it as postinstall is fine if this component is optional for your application and it can gracefully handle it not being installed. If this is not the case then you should treat it as a prerequisite instead and always install it via PrepareToInstall.