One-stop VS Code Extension to compile, debug and profile Amiga C/C++ programs compiled by the bundled gcc 12.2 with the bundled WinUAE/FS-UAE. This fork provides support for libraries
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Standard Amiga libraries are available (you need to specify a Workbench floppy disk or hard disk; see below).
MUI is also included on the compilation side (SDK v3.9) and on the execution side (libraries v3.8).
Custom libraries can be declared through the setting of assigns.
The bsdsocket.library of UAE can also be enabled.
Quick-start
Install the extension from the Visual Studio Code Marketplace
Create a new empty project folder with File > Open Folder...
From the command palette Ctrl+Shift+P select Amiga: Init Project With Libs
Open .vscode/launch.json and make "kickstart" point to your Kickstart 3.1 ROM and "workbench" to your Workbench 3.1 floppy (.adf)
Hit F5 to build and run a minimal sample project (you should see the MUI app of the above screen shot)
How-to-use
In .vscode/launch.json, you can also make "workbench" point to a hard file (.hdf) containing Workbench 3.1; in this case, for WinUAE, you need to specify at the end of its path its number of sectors, number of surfaces,
number of reserved blocks, and block size (e.g. "workbench": "C:/Path to hard file/A1200.hdf,32,1,2,512") as they appear in the settings window of WinUAE (see picture below). For FS-UAE, just specify the path to the .hdf file
(e.g. "workbench": "C:/Path to hard file/A1200.hdf").
Still in .vscode/launch.json, you can specify with "assigns" a list of assigns (separated by commas) which will be translated in the startup-sequence; for example "assigns":"MUI: DH2:MUI,LIBS: DH2:LIBS DH2:MUI/Libs" will
add at the end of the startup-sequence:
assign MUI: DH2:MUI
assign LIBS: DH2:LIBS DH2:MUI/Libs
The purpose is to add the ability to declare your own libraries residing on your hard file. This latest is defined as DH2: (DH0: is a directory virtual hard drive, used for booting and where the startup-sequence is located,
and DH1: is the directory virtual hard drive containing your compiled program). Thus, the content of DH2: is never modified.
At last, "bsdSocket" can be set to true (e.g. "bsdSocket":true) to enable the bsdsocket.library of UAE.
How does it work?
This fork has the MUI libraries included in the disk DH0: which is already used by the original vscode-amiga-debug extension to store the startup-sequence and to boot the Amiga.
It adds the needed definitions to the UAE configuration file to declare your "workbench" pointing to a floppy or a hard file and to enable optionally the bsdsocket.library.
It also adds the following instruction to the startup-sequence (when "workbench" points to a hard file; for a floppy disk, just replace DH2: by DF0:):
DH2:C/assign C: DH2:C
C:assign SYS: DH2:
C:assign S: DH2:S
C:assign LIBS: DH2:LIBS DH0:MUI/Libs
C:assign DEVS: DH2:Devs
C:assign FONTS: DH2:Fonts
C:assign L: DH2:L
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:assign T: RAM:T
C:assign CLIPS: RAM:Clipboards
C:assign ENV: RAM:ENV
C:assign LOCALE: DH2:Locale dh0:MUI/Locale
C:assign PRINTERS: DEVS:Printers
At last, when you define "assigns", it adds your assigns at the end of the startup-sequence (see above for an example).
