|
Post by Abe on May 30, 2023 21:46:09 GMT
I just installed the qb64 extension for Visual Studio Code.
I'm on an intel Mac and after reading up and watching videos' I got it to work but I noticed my programs were not launching on their own. The programs would only run in visual studio after a compile.
I found the problem. It is in the launch Json file. For Mac there is a ".run" added to the executable. I removed the two instances of ".run" both on the same line and it worked perfectly.
Like I said I'm on an intel Mac. I don't know if .run works on the SOC M1 M2 versions but it didn't work on my computer.
Hope this helps further development with Visual Studio Code.
|
|
dualbrain
Junior Member
The only bug free code is code that is no longer used.
Posts: 51
|
Post by dualbrain on Jun 3, 2023 14:53:44 GMT
I've forwarded this information to the main dev on the extension (via discord); I'd also suggest that you create an issue over on the github repo found at github.com/QB64Official/vscode
|
|
grymmjack
New Member
I am a friendly old nerd
Posts: 2
|
Post by grymmjack on Jun 3, 2023 18:24:21 GMT
I just installed the qb64 extension for Visual Studio Code. I'm on an intel Mac and after reading up and watching videos' I got it to work but I noticed my programs were not launching on their own. The programs would only run in visual studio after a compile. I found the problem. It is in the launch Json file. For Mac there is a ".run" added to the executable. I removed the two instances of ".run" both on the same line and it worked perfectly. Like I said I'm on an intel Mac. I don't know if .run works on the SOC M1 M2 versions but it didn't work on my computer. Hope this helps further development with Visual Studio Code. Hey
I don't have Apple Silicon, so I can't 100% confirm this. However it might help to explain a few things?
We added the .run extension to allow the binaries to be ignored from your work. You do not want to commit a binary (at least I don't) to your repo.
Since a file with no extension is impossible to ignore since the file name would vary, depending on what your program.bas was called each time, the .run is the way we can ignore the compiled binaries.
Can you please explain what you were doing to try and "launch the program on it's own"?
You can launch any executable from a terminal using ./program.run there is also a program.start_command which calls in turn the .run file. So if you are trying to run the program use the program.start_command and see if that works.
Thanks
Were you using the Finder or a terminal? And if you were using a terminal, was it the built-in vscode terminal or the one provided by MacOS?
|
|
abram
New Member
Posts: 44
|
Post by abram on Jun 11, 2023 3:10:52 GMT
I went to the folder and double clicked on the binary.run file and that didn't work so I renamed the file to binary and double clicked it then (that worked). I looked into it further and found the .run in the vscode files. I don't know what a repo is or git, but I do consider myself good with computers. I just never researched git development because it looked like an end of the road type technology.
|
|
dualbrain
Junior Member
The only bug free code is code that is no longer used.
Posts: 51
|
Post by dualbrain on Sept 21, 2023 1:01:27 GMT
|
|