VS Code Amiga assembly extension and vasm+vlink

hooverphonique · 26 February 2024, 23:18

I don't know if it was always like this, but the mentioned extension builds using vasm+vlink, i.e. it assembles the source files using "vasmm68k_mot -m68000 -Fhunk -linedebug" (or whatever you configure) and then links the resulting .o files using "vlink -bamigahunk -Bstatic".

Now, I'm having some crash problems when launching an emulator (using F5) when there's multiple sources involved, and I suspect some of it has to do with where the resulting executable's entry point is.

Is this defined by the order of the objects listed for vlink? and if so, how does the vs code extension know which one has the entry point?

Nightshft · 27 February 2024, 04:57

That's a good question.
In the few cases I tried linking, I assumed it would take the file I have currently open in the editor, when pressing F5 as the first object file passed to vasm.
But maybe that was just pure luck, because when I give it a try now, it looks like it calls vasm with the .o files in alphabetical order.

JoeJoe · 27 February 2024, 10:00

You can certainly specify the entry point if you have several sources. This is always the case in my projects.

Simply set the entry point in the task.json under vlink. Example

hooverphonique · 27 February 2024, 18:08

Quote:

Originally Posted by JoeJoe

You can certainly specify the entry point if you have several sources. This is always the case in my projects.

Simply set the entry point in the task.json under vlink. Example

Thanks for the tip, that seems to have done the trick

26 February 2024, 23:18	#1
hooverphonique ex. demoscener "Bigmama" Join Date: Jun 2012 Location: Fyn / Denmark Posts: 1,630	VS Code Amiga assembly extension and vasm+vlink I don't know if it was always like this, but the mentioned extension builds using vasm+vlink, i.e. it assembles the source files using "vasmm68k_mot -m68000 -Fhunk -linedebug" (or whatever you configure) and then links the resulting .o files using "vlink -bamigahunk -Bstatic". Now, I'm having some crash problems when launching an emulator (using F5) when there's multiple sources involved, and I suspect some of it has to do with where the resulting executable's entry point is. Is this defined by the order of the objects listed for vlink? and if so, how does the vs code extension know which one has the entry point?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Amiga Assembly extension for Visual Studio Code	prb28	Coders. Asm / Hardware	342	15 December 2023 21:22
Amiga Assembly VSCode extension v1.0	prb28	Coders. Releases	3	28 November 2021 17:00
vasm / vlink undefined symbol	zeGouky	Coders. General	2	02 January 2019 08:49
Features requests for vscode amiga assembly extension ?	prb28	Coders. General	0	27 December 2018 16:19
Trying out vlink and vasm	cla	Coders. General	2	30 September 2016 20:30

27 February 2024, 04:57	#2
Nightshft Registered User Join Date: Mar 2018 Location: Austria Posts: 617	That's a good question. In the few cases I tried linking, I assumed it would take the file I have currently open in the editor, when pressing F5 as the first object file passed to vasm. But maybe that was just pure luck, because when I give it a try now, it looks like it calls vasm with the .o files in alphabetical order.

27 February 2024, 10:00	#3
JoeJoe Registered User Join Date: Feb 2020 Location: Germany Posts: 188	You can certainly specify the entry point if you have several sources. This is always the case in my projects. Simply set the entry point in the task.json under vlink. Example

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)