Latest Win32 VASM Build? - Page 4

jotd · 15 May 2016, 22:38

BTW found another bug: If I define a macro, the IFD on this macro name fails (not defined).
Using Barfly for instance, the IFD on a macro name is true.

phx · 16 May 2016, 14:34

I don't think this is a bug. A macro is a macro and not a symbol definition. Devpac and A68k behave like vasm, and even Barfly has a special ifmacrod directive to check if a macro exists. So I guess this is just a side effect.

jotd · 16 May 2016, 20:26

Ok then whdload includes should be adapted. Thanks

jotd · 29 June 2016, 23:01

BTW I just tried that IFMACROD with VASM and got

vasm 1.7e (c) in 2002-2016 Volker Barthelmann
...
error 2 in line 1321 of "kickfs.s": unknown mnemonic <IFMACROD>

phx · 01 July 2016, 11:29

Quote:

Originally Posted by jotd

error 2 in line 1321 of "kickfs.s": unknown mnemonic <IFMACROD>

I never said that vasm supports IFMACROD. I might implement it for the next version, though...

jotd · 01 July 2016, 17:57

that would be good. I can build most of whdload slaves, but in some special cases I have to revert to Barfly because of that IFD behaviour difference. Thanks.

phx · 05 July 2016, 15:26

Ok, implemented ifmacrod and ifmacrond. Please try tomorrow's snapshot.

guy lateur · 10 July 2017, 16:43

Sorry for the slight necro, but I'm having trouble compiling the latest version of vasm for windows. I'm using a Visual Studio 2010 command prompt, and do 'nmake CPU=m68k SYNTAX=mot'. I get this error:

Code:

        link obj_win32/m68k_mot_vasm.o obj_win32/m68k_mot_atom.o obj_win32/m68k_
mot_expr.o obj_win32/m68k_mot_symtab.o obj_win32/m68k_mot_symbol.o  obj_win32/m6
8k_mot_error.o obj_win32/m68k_mot_parse.o obj_win32/m68k_mot_reloc.o obj_win32/m
68k_mot_hugeint.o  obj_win32/m68k_mot_cond.o obj_win32/m68k_mot_supp.o obj_win32
/m68k_mot_cpu.o obj_win32/m68k_mot_syntax.o  obj_win32/m68k_mot_output_test.o ob
j_win32/m68k_mot_output_elf.o obj_win32/m68k_mot_output_bin.o  obj_win32/m68k_mo
t_output_vobj.o obj_win32/m68k_mot_output_hunk.o obj_win32/m68k_mot_output_aout.
o  obj_win32/m68k_mot_output_tos.o obj_win32/m68k_mot_output_srec.o /NOLOGO  /OU
T:vasmm68k_mot_win32.exe
m68k_mot_syntax.o : error LNK2019: unresolved external symbol _snprintf referenc
ed in function _expand_macro
vasmm68k_mot_win32.exe : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0
\VC\BIN\link.EXE"' : return code '0x460'
Stop.

Any ideas on how to solve this? TIA!

Leffmann · 10 July 2017, 19:19

Try adding

/D snprintf=_snprintf

to COPTS in the makefile.

guy lateur · 10 July 2017, 19:26

Quote:

Originally Posted by Leffmann

Try adding

/D snprintf=_snprintf

to COPTS in the makefile.

Thanks for the tip, but that doesn't seem to solve the problem, unfortunately. I get the same error.

Leffmann · 10 July 2017, 20:08

No idea why it fails then, because snprintf is available as _snprintf according to Microsoft's own documentation and I've built vasm like this in the past.

If you're willing to install the free VS 2017 Community edition's CLI tools, then you can use the attached solution to build vasm. Extract vasm into src/vasm and run:

msbuild vbcc.sln /m /p:Configuration=Release;Platform=x86

alkis · 10 July 2017, 20:28

On vs2017 builds cleanly with
nmake CPU=m68k SYNTAX=mot -f makefile.win32

(Had to mkdir obj_win32 first though)

guy lateur · 10 July 2017, 22:02

Quote:

Originally Posted by Leffmann

No idea why it fails then, because snprintf is available as _snprintf according to Microsoft's own documentation and I've built vasm like this in the past.

If you're willing to install the free VS 2017 Community edition's CLI tools, then you can use the attached solution to build vasm. Extract vasm into src/vasm and run:

msbuild vbcc.sln /m /p:Configuration=Release;Platform=x86

Alright, I've installed VS2017 CE and the Powershell Tools, and this is what I get:

Code:

 
 C:\Users\Guy Lateur\Downloads\vasm18sln>msbuild vbcc.sln /m /p:Configuration=Rel
ease;Platform=x86
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.
 Build started 10/07/2017 21:47:01.
     1>Project "C:\Users\Guy Lateur\Downloads\vasm18sln\vbcc.sln" on node 1 (de
       fault targets).
     1>ValidateSolutionConfiguration:
         Building solution configuration "Release|x86".
     1>Project "C:\Users\Guy Lateur\Downloads\vasm18sln\vbcc.sln" (1) is buildi
       ng "C:\Users\Guy Lateur\Downloads\vasm18sln\vasmm68k_mot\vasmm68k_mot.vc
       xproj" (2) on node 1 (default targets).
     2>C:\Users\Guy Lateur\Downloads\vasm18sln\vasmm68k_mot\vasmm68k_mot.vcxpro
       j(27,3): error MSB4019: The imported project "C:\Program Files (x86)\Mic
       rosoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.C
       pp.Default.props" was not found. Confirm that the path in the <Import> d
       eclaration is correct, and that the file exists on disk.
     2>Done Building Project "C:\Users\Guy Lateur\Downloads\vasm18sln\vasmm68k_
       mot\vasmm68k_mot.vcxproj" (default targets) -- FAILED.
     1>Done Building Project "C:\Users\Guy Lateur\Downloads\vasm18sln\vbcc.sln"
        (default targets) -- FAILED.
 Build FAILED.
        "C:\Users\Guy Lateur\Downloads\vasm18sln\vbcc.sln" (default target) (1)
       ->
       "C:\Users\Guy Lateur\Downloads\vasm18sln\vasmm68k_mot\vasmm68k_mot.vcxpr
       oj" (default target) (2) ->
         C:\Users\Guy Lateur\Downloads\vasm18sln\vasmm68k_mot\vasmm68k_mot.vcxp
       roj(27,3): error MSB4019: The imported project "C:\Program Files (x86)\M
       icrosoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft
       .Cpp.Default.props" was not found. Confirm that the path in the <Import>
        declaration is correct, and that the file exists on disk.
     0 Warning(s)
    1 Error(s)
 Time Elapsed 00:00:01.25

What to do, what to do..

Leffmann · 11 July 2017, 13:06

The makefile works fine with VS 2017 for both Alkis and myself. Otherwise, the solution needs the Windows 8.1 SDK and the Windows XP platform toolset, maybe you need to install those first, or you can edit the solution to ditch the resource scripts and use the regular Windows 10 toolset.

I also have an installer in this thread: http://eab.abime.net/showthread.php?t=83113 and if you don't need the whole thing then you can open the installer in 7-zip and just extract the executables you need.

EDIT: attached GNU Make 4.1, vbcc 0.9f, vasm 1.8, and vlink 0.16

guy lateur · 11 July 2017, 13:19

Quote:

Originally Posted by Leffmann

The makefile works fine with VS 2017 for both Alkis and myself. Otherwise, the solution needs the Windows 8.1 SDK and the Windows XP platform toolset, maybe you need to install those first, or you can edit the solution to ditch the resource scripts and use the regular Windows 10 toolset.

I also have an installer in this thread: http://eab.abime.net/showthread.php?t=83113 and if you don't need the whole thing then you can open the installer in 7-zip and just extract the executables you need.

I'll happily grab your installer, thank you!

guy lateur · 11 July 2017, 17:37

I've just successfully cross assembled/linked some basic amiga tutorials using the latest versions of vasm and vlink, as referenced above -- so hurray for me!

So that's me probably gone from developing on the hardware itself. I also have Amiga Forever, so I can test it on the pc before transfering to the amiga, which is handy..

alpine9000 · 15 July 2017, 09:50

Quote:

Originally Posted by guy lateur

I've just successfully cross assembled/linked some basic amiga tutorials using the latest versions of vasm and vlink, as referenced above -- so hurray for me!

So that's me probably gone from developing on the hardware itself. I also have Amiga Forever, so I can test it on the pc before transfering to the amiga, which is handy..

Cross development is so much easier.

Wait until you discover the power of the WinUAE debugger.

guy lateur · 15 July 2017, 09:55

Quote:

Originally Posted by alpine9000

Wait until you discover the power of the WinUAE debugger.

Yeah, I do miss the debugger. Any chance of a quick link to some info on how to set that up?

alpine9000 · 15 July 2017, 10:01

Quote:

Originally Posted by guy lateur

Yeah, I do miss the debugger. Any chance of a quick link to some info on how to set that up?

I mainly use fs-uae but its basically the same debugger.

This http://www.amigacoding.com/index.php/WinUAE_debugger seems to show the basics.

guy lateur · 15 July 2017, 10:06

Quote:

Originally Posted by alpine9000

I mainly use fs-uae but its basically the same debugger.

This http://www.amigacoding.com/index.php/WinUAE_debugger seems to show the basics.

Ok thanks, I'll definitely check that out!

10 July 2017, 19:19	#69
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	Try adding /D snprintf=_snprintf to COPTS in the makefile.

10 July 2017, 20:08	#71
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	No idea why it fails then, because snprintf is available as _snprintf according to Microsoft's own documentation and I've built vasm like this in the past. If you're willing to install the free VS 2017 Community edition's CLI tools, then you can use the attached solution to build vasm. Extract vasm into src/vasm and run: msbuild vbcc.sln /m /p:Configuration=Release;Platform=x86 Last edited by Leffmann; 02 September 2017 at 11:13.

11 July 2017, 13:06	#74
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	The makefile works fine with VS 2017 for both Alkis and myself. Otherwise, the solution needs the Windows 8.1 SDK and the Windows XP platform toolset, maybe you need to install those first, or you can edit the solution to ditch the resource scripts and use the regular Windows 10 toolset. I also have an installer in this thread: http://eab.abime.net/showthread.php?t=83113 and if you don't need the whole thing then you can open the installer in 7-zip and just extract the executables you need. EDIT: attached GNU Make 4.1, vbcc 0.9f, vasm 1.8, and vlink 0.16 Last edited by Leffmann; 02 September 2017 at 11:13.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
vasm and word alignment	Den	Coders. Asm / Hardware	9	07 February 2014 11:25
Help linking VASM object code	clenched	Coders. Asm / Hardware	2	24 May 2013 22:32
vasm fsincos	dalton	Coders. Asm / Hardware	4	03 September 2012 10:35
vasm 1.5 RFC	phx	Coders. General	30	11 December 2010 02:08
Win32 Game Ports?	BobRedthorp	Retrogaming General Discussion	11	03 August 2003 13:56

15 May 2016, 22:38	#61
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,232	BTW found another bug: If I define a macro, the IFD on this macro name fails (not defined). Using Barfly for instance, the IFD on a macro name is true.

16 May 2016, 14:34	#62
phx Natteravn Join Date: Nov 2009 Location: Herford / Germany Posts: 2,500	I don't think this is a bug. A macro is a macro and not a symbol definition. Devpac and A68k behave like vasm, and even Barfly has a special ifmacrod directive to check if a macro exists. So I guess this is just a side effect.

16 May 2016, 20:26	#63
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,232	Ok then whdload includes should be adapted. Thanks

29 June 2016, 23:01	#64
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,232	BTW I just tried that IFMACROD with VASM and got vasm 1.7e (c) in 2002-2016 Volker Barthelmann ... error 2 in line 1321 of "kickfs.s": unknown mnemonic <IFMACROD>

01 July 2016, 17:57	#66
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,232	that would be good. I can build most of whdload slaves, but in some special cases I have to revert to Barfly because of that IFD behaviour difference. Thanks.

05 July 2016, 15:26	#67
phx Natteravn Join Date: Nov 2009 Location: Herford / Germany Posts: 2,500	Ok, implemented ifmacrod and ifmacrond. Please try tomorrow's snapshot.

10 July 2017, 20:28	#72
alkis Registered User Join Date: Dec 2010 Location: Athens/Greece Age: 53 Posts: 719	On vs2017 builds cleanly with nmake CPU=m68k SYNTAX=mot -f makefile.win32 (Had to mkdir obj_win32 first though)

11 July 2017, 17:37	#76
guy lateur Registered User Join Date: May 2017 Location: Belgium Age: 50 Posts: 334	I've just successfully cross assembled/linked some basic amiga tutorials using the latest versions of vasm and vlink, as referenced above -- so hurray for me! So that's me probably gone from developing on the hardware itself. I also have Amiga Forever, so I can test it on the pc before transfering to the amiga, which is handy..

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