15 May 2016, 22:38 | #61 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,369
|
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 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,539
|
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 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,369
|
Ok then whdload includes should be adapted. Thanks
|
29 June 2016, 23:01 | #64 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,369
|
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, 11:29 | #65 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,539
|
|
01 July 2016, 17:57 | #66 |
This cat is no more
Join Date: Dec 2004
Location: FRANCE
Age: 52
Posts: 8,369
|
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 |
Natteravn
Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,539
|
Ok, implemented ifmacrod and ifmacrond. Please try tomorrow's snapshot.
|
10 July 2017, 16:43 | #68 |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
Compiling vasm 1.8 for win32
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. |
10 July 2017, 19:19 | #69 |
Join Date: Jul 2008
Location: Sweden
Posts: 2,269
|
Try adding
/D snprintf=_snprintfto COPTS in the makefile. |
10 July 2017, 19:26 | #70 |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
|
10 July 2017, 20:08 | #71 |
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. |
10 July 2017, 20:28 | #72 |
Registered User
Join Date: Dec 2010
Location: Athens/Greece
Age: 53
Posts: 722
|
On vs2017 builds cleanly with
nmake CPU=m68k SYNTAX=mot -f makefile.win32 (Had to mkdir obj_win32 first though) |
10 July 2017, 22:02 | #73 | |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
Quote:
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 |
|
11 July 2017, 13:06 | #74 |
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. |
11 July 2017, 13:19 | #75 | |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
Quote:
|
|
11 July 2017, 17:37 | #76 |
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.. |
15 July 2017, 09:50 | #77 | |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 881
|
Quote:
Wait until you discover the power of the WinUAE debugger. |
|
15 July 2017, 09:55 | #78 |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
|
15 July 2017, 10:01 | #79 | |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 881
|
Quote:
This http://www.amigacoding.com/index.php/WinUAE_debugger seems to show the basics. |
|
15 July 2017, 10:06 | #80 | |
Registered User
Join Date: May 2017
Location: Belgium
Age: 50
Posts: 334
|
Quote:
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
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 |
|
|