How can I work with FPC from OmniPascal? - omnipascal

I tried this commands in VSCode on Windows
"omnipascal.delphiInstallationPath": "C:\\lazarus\\fpc"
"omnipascal.delphiInstallationPath": "C:\\lazarus\\fpc\\3.0.2\\source"
"omnipascal.freePascalSourcePath": "C:\\lazarus\\fpc"
"omnipascal.freePascalSourcePath": "C:\\lazarus\\fpc\\3.0.2\\source"
Also I tried same commands on Linux with usr/share/fpcsrc. But I can not work FPC from VSCode - OmniPascal.
How can I run it?

Related

i386-elf-gcc: Command not found

I am using ubuntu in windows by WSL. I have installed gnu gcc and various required files required to develop a basic Operating System.
Actually I have installed from this link.
But whenever I try to run command 'i386-elf-gcc', it shows command not found. Interestingly if I run export PATH="$PATH:/usr/local/i386elfgcc/bin" this command from that terminal and rerun 'i386-elf-gcc' it works correctly. This happens every time I try to run the command in a new terminal.
I need to get rid of this problem. What can I do?

Buildozer, WSL adb not finding device, adb in Powershell works

I have a python program using PySimpleGUI. It works on Windows, a pure Linux machine and it also works on the WSL. I'd like to use it on my phone(Pixel 7 pro). Buildozer makes the apk file but during the process 'buildozer android deploy run logcat' it runs the adb devices cmd and finds nothing. The adb devices from a PowerShell works fine. It probably has something to do with the virtual machine WSL provides. I've queried google and read pages of information and suggestions and nothing so far works.
Please let me know if I can provide anymore info that will help solve this.
I've tried running the adb in the build environment manually, outside build script of buildozer, with the same results, no devices found.
I'd like to move on the next step of trying or troubleshooting the app on my phone.
Thanks in advance, Craig

NodeJs terminal configuration in VScode

How do I configure details of nodeJS terminal? ( using- windows 10 & VScode )
Its bothers me that when I type commands in split screen mode, the line gets split up because it ran out of space. If possible, id like the terminal to display:
$
when awaiting commands.

please use the remote wsl extension for windows subsystem for linux
for ubuntu terminal in vs code use extension Ubuntu pastebin for vs code

VSCode with WSL - How to use Bash for the launch configurations?

I use Visual Studio Code to develop a TypeScript Node application on Windows 10, with WSL enabled.
Thanks to other threads, I'm almost able to run a VSCode task with Bash on Ubuntu on Windows.
But now I try to do the same with a launch configuration. How can I make a launch configuration to use the node executable installed in WSL instead of the one installed on Windows?
If I run this command directly in the integrated terminal, with Bash, it works :
node src/start.js
But when I press "[F5]" and start a launch configuration that runs this same file, I get an error : "Error: %1 is not a valid Win32 application". This is because the oracledb library is used and has been compiled in Bash, not in Windows.
How can I make a launch configuration use Bash to run Node?
UPDATE : I opened an issue about that on VSCode's GitHub page.

Not if sure you still need help.
open bash outside of the vs code.
then run the following command, to install node.
sudo apt install nodejs-legacy
and you should be able to run node with bash in vs code.

Can't launch Visual Studio Code on Ubuntu

I'm running a VM in Azure with Ubuntu 14.04. I've installed XFCE and use X2GO to remote desktop to the machine.
I've downloaded the VS Code and unzipped the files. When I run Code from a terminal I get the following error:
WouterDeKort#UbuntuDev:~/tools/web/visual-studio-code$ ./Code
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
WouterDeKort#UbuntuDev:~/tools/web/visual-studio-code$ [ , [Error: channel closed] ]
Any idea what I'm doing wrong?
DISCLAIMER ;-) I'm a total Linux newby. I've just installed Linux for the first time today and I have no idea what I'm doing ;-)

The work-a-round is in issue 3451. After running this, I was able to launch it from Debian Jessie with LXDE over X2Go.
sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' /usr/lib/x86_64-linux-gnu/libxcb.so.1

I have the same problem using X2GO and LXDE. Works okay (but slowly) using MobaXterm so apparently this is a problem specific to X2GO.

For anyone who still wonder what is the best choice if you want to start Visual Studio Code on a headless Ubuntu - the winning combination is:
Ubuntu Server + xfce + nomachine remote desktop
VS Code starts immediately without any hacks, you can set your resolution however you like, and nomachine is blazingly fast.

Resources