time to drop polink and adopt golink

jack · Post by **jack** » Wed Nov 15, 2006 11:11 pm

Pelle seem's to be missing in action, and frankly i am tired of these polink errors, i think gotools are a good option.

srod · Post by **srod** » Wed Nov 15, 2006 11:22 pm

The go-tools are excellent, very easy to use. Jeremy Gordon is a flaming genius!

However, the business of linking object files is a minefield anyhow, always has been - no matter which linker you use! What with the subtle differences between gcc and MS coff files etc. to name but one pitfall.

localmotion34 · Post by **localmotion34** » Wed Nov 15, 2006 11:26 pm

I have been playing with RADasm for a litlte while, and all the addins. let me tell you, GoLink, GoASM ect absolutely wont work if they are not in the C:\Golink directory.

they are terribly written, full of quirks, and just plain impossible to use.

That pretty much goes for most ASM compilers.

I am getting a PHD in Neuroscience, where i can record single ion channels in a cell membrane, re-write DNA sequences, image single cells in the brain, ect.

For the life of me i cannot figure out how to get RadASM and Golink, or Masm, or Fasm, or any of them to actually work.

srod · Post by **srod** » Wed Nov 15, 2006 11:31 pm

I use GoAsm and GoLink with RADasm without a hitch. Remember that RADasm isn't specifically for GoAsm as such so it does take a bit of 'persuading' before it behaves itself with GoAsm.

Once I had it configured properly though it's a very nice package.

Personally I love the syntax of GoAsm and just find it easier to get on with than Fasm, but it's all personal preference etc.

Dare · Post by **Dare** » Thu Nov 16, 2006 12:52 am

Last time I looked the GoAsm and associated packages had licencing issues that made it quite difficult to use them in any extensive way.

Or maybe I misinterpreted the rules?

Now if we had a cross-platform masm and associated tools life would be very sweet indeed ...

jack · Post by **jack** » Thu Nov 16, 2006 2:04 am

@Dare: from the manual

Legal stuff
Copyright
GoLink is copyright © Jeremy Gordon 2002/6 [MrDuck Software] - all rights reserved.
Licence and distribution
You may use GoLink free for any purpose. You may redistribute GoLink freely (but not for payment nor for use with a program or any material for which the user is asked to pay). You are not entitled to hide or deny my copyright.

this one part need a bit of clarification if it were to be packeged with PB

(but not for payment nor for use with a program or any material for which the user is asked to pay)

localmotion34 · Post by **localmotion34** » Thu Nov 16, 2006 2:17 am

srod wrote:I use GoAsm and GoLink with RADasm without a hitch. Remember that RADasm isn't specifically for GoAsm as such so it does take a bit of 'persuading' before it behaves itself with GoAsm.

Once I had it configured properly though it's a very nice package.

Personally I love the syntax of GoAsm and just find it easier to get on with than Fasm, but it's all personal preference etc.

well you show me how to setup RadASM to use MASm, GoASM, and FASM, then i might be able to compeltely evaluate it. otherwise, i just may forget about it because it is just too complicated and almost not worth the trouble.

whoever wrote these must have not had much contact with reality. i cant figure out the logic behind the interface, the menus and options, the command line parameters ect.

srod · Post by **srod** » Thu Nov 16, 2006 12:54 pm

I seem to remember the main problems were with the gfl.txt command file and the goasm.ini file in the RASasm folder, both of which I ended up editing manually. The goasm.ini file holds the assembly/link options etc. when assembling individual files and I could find no other way of setting these options other than manually. For projects, you can just set the project options through RADasm and everything is now 'ticketyboo'!

I agree that it is confusing though when trying to set the thing up!

Still, I love GoAsm.