Link external modules in Devpac

[Knocker]

In order to speed up assemble I'd like to pre-assemble a code module (Protracker player), but I can't get it to work.

Let's say I have an external module, ExternalModule.s, with a function like this:

	xdef ExternalFunction
ExternalFunction:
	moveq #5,d0
	rts

I want to call the function from my main, Main.s, module:

	xref ExternalFunction
Main:
	moveq #1,d0
	jsr ExternalFunction
	moveq #5,d0

This is what I've tried:

Open ExternalModule.s in Devpac 3.
In Settings->Assembler->Control change Format to Linkable and change output to ExternalModule.o with path the same as the .s files.
In Settings, check Assemble To Disk
Assemble (this creates ExternalModule.o)
Open Main.s
Change the two Settings back to their defaults
Assemble => Error undefined symbol at line 4 in file Main.s

Seems like I need to tell the assember/linker about ExternalModule.o somehow. Haven't tried linking them together from CLI using Blink, ideally I'd like to do it directly from the Devpac editor, by simply selecting Assemble.

Any ideas?

[phx]

Originally Posted by Knocker

Open Main.s
Change the two Settings back to their defaults
Assemble => Error undefined symbol at line 4 in file Main.s

Never really worked with the Devpac GUI, but you have to make sure that both are linkable object files, so don't reset the two settings here.

Seems like I need to tell the assember/linker about ExternalModule.o somehow.

You have to tell the linker. The assembler only needs to know which symbol is externally defined (XREF) or visible for the linker (XDEF).

Haven't tried linking them together from CLI using Blink, ideally I'd like to do it directly from the Devpac editor, by simply selecting Assemble.

I didn't know that the Devpac GUI contains a linker.

[Knocker]

Thanks phx. I guess I should state that I'm just assuming this is possible to do - it may not be. It would kind of suck, at least by modern standards , to have to leave the IDE and go to CLI to build/run programs consisting of multiple modules. I just want to do my regular Amiga-a to assemble and Amiga-x to run!

I didn't know that the Devpac GUI contains a linker.

Well, the manual seems to imply that it comes with Blink, but I can't find it. In fact I can't find it anywhere, maybe I should try your PhxLnk432? But again, having a separate step to link then run kind of defeats the purpose of building multiple modules for me.

[meynaf]

As your goal seems to speed up the assembly, perhaps another assembler could do the job - as devpac is clearly not among the fastest.
However if you really need an IDE then you're a little bit locked i'm afraid...

[modrobert]

Originally Posted by Knocker

Well, the manual seems to imply that it comes with Blink, but I can't find it. In fact I can't find it anywhere, maybe I should try your PhxLnk432? But again, having a separate step to link then run kind of defeats the purpose of building multiple modules for me.

You can find Blink here: http://aminet.net/package/dev/misc/blink67

After searching through Amiga TOSEC and other places, I can't find 'Blink' in the Devpac releases either, looks like two floppies are missing.

This is from the Devpac 3 manual.

Devpac 3 Disk Contents

Devpac Amiga is supplied on four 3.5" disks; the first set of two is intended for use under version 1.3 of the operating system whilst the second is for use with Release 2 to 3.1.

The files from the Devpac drawer mentioned in the manual which are missing as follows; BLink, FD2LVO, SRSplit.

Anyway, I can recommend vlink if you rather use a linker which is up to date.

[Knocker]

Thanks modrobert. I got it configured so the Execute option (Amiga-E) in Devpac runs a two line script that invokes Blink and then runs the program. Not sure if this is faster than just having one big source file though, since the linking is pretty slow. Btw, took forever to get Blink to work - my code had a "opt c-" line in it that somehow screwed up the case of xdefs so they couldn't be found...

[Lonewolf10]

Opt c- in Devpac turns off case sensitivity, likewise Opt c+ turns it on.


Personally, I always have case sensitivity on in my code.