Jump to content

immolator

Members
  • Posts

    1
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Krakow/Poland
  • Interests
    Atari 8-bit, Amiga, Linux, demoscene, coding, Linux, programming

immolator's Achievements

Combat Commando

Combat Commando (1/9)

0

Reputation

  1. Hi there! @JAC! Add 1 to the WUDSN users global counter please. We briefly talked at Silly Venture 2014 in Gdansk, but I'd like to say 'thank you' here as well. Thanks for the plugin and youtube tutorials! Fantastic job! @snicklin My OS is Linux Mint. I use MADS compiled natively for Linux, and Altirra which runs with Wine. To make "Compile and Run" works, I wrapped Altirra with a tiny shell script that contains the following: /usr/bin/wine64 g:\Altirra64.exe "${@}" (of course g: drive maps a proper directory in winecfg) and I set "Path to Application" to that script. That hack makes the World somewhat a better place, but there are two major glitches that need to be workarouned (solved?) still: 1. The MADS natively compiled for Linux does not add the "Source:" line to .lst file. That makes the Altirra debug-on-the-fly impossible to use, unless you add that entry manually. 2. .atdbg file contains native Linux path what confuses Altirra of course. Result similar as described above. No source level debugging without manual corrections. Partially that could be solved by editing these files manually or not using full paths to asm files (you can define another drive in wincfg for the sources), but still every time you hit Ctrl+Alt+0 you end up with .atdbg file screwed... Next step would be to wrap Windows MADS executable into a shell script and include it in that tweaked toolchain. When I don't need the debug mode, Altirra runs just fine, not mentioning native atari++ and atari800, both natural options in Linux world of course. The issue though is that I'm a beginner, and need debug a lot Cheers.
×
×
  • Create New...