There are two ways of installing WUDSN IDE. If you are using a Windows operating system, I recommend downloading the
ready to run zero installation distribution:
It contains the Eclipse Platform, the Java Runtime Environment, the latest stable version of the WUDSN IDE plugin,
all supported compilers, and an emulator for each supported platform. All paths to folders, compilers, and emulators
are pre-configured. Unpack the content of this archive to the directory "C:\jac\wudsn" and click the "WUDSN IDE-64
bit" link. Eclipse will open with the predefined workspace that contains "Hello World" examples for different
platforms.
If you use another operating system or want to use the latest version of WUDSN or want to
install compilers and emulators more selectively, read the descriptions of the installation steps below. In
addition, the following previous versions of the zero installation distribution are available
In case something is not correct or not working, please contact me.
Installing Eclipse » top
- Download Eclipse from https://www.eclipse.org/downloads.
- If you don't know which version to take, use Eclipse 4.12 Platform Runtime Binary (81 MB) for WUDSN IDE
1.7.1 and newer. Eclipse 4.3.2 Platform Runtime Binary (61 MB) for WUDSN IDE
1.7.0 and older.
This is a minimum size installation that does not include the Java Development Toolkit
(JDT). WUDSN IDE has no dependency on the JDT but of course on the Java Runtime Environment (JRE). Make sure you
also have the 64-bit version of the JRE installed if you want to use the 64-bit version of Eclipse.
- Unzip the downloaded archive file and store the contained folder "eclipse" where you want Eclipse to be located
on your local hard drive.
- Start the Eclipse executable from that folder.
- Upon the first start, you are prompted to specify the folder where the workspace shall be located.
- Normally a start link a created to this end. You can use the parameter "-nl" to specify the locale if you want.
Use "en_US" for English or "de_DE" for German. Example: "C:\Program Files\Eclipse\4.12\eclipse\eclipse.exe"
-Xmx512M -nl en_US"
- It is recommended to create the workspace folder in your home directory.
- After you have read the welcome page and got familiar with the Eclipse UI, just switch to the Resource
perspective.
- Open the view "Problems" via the menu "Window/Show View/Problems" and then click the entry "Configure
Contents..." from its view menu.
- Select the configuration "All Errors", the radio button "On selected element and its children" and the
checkboxes "Error", "Warning" and "Info".
- Now Eclipse itself is ready and you can proceed with step Installing WUDSN
IDE.
Installing WUDSN IDE » top
- Start Eclipse
- Select the entry "Install New Software..." from the menu "Help".
- Enter "https://www.wudsn.com/update" in the "Work with" field and press ENTER.
- Select the latest version of the feature "WUDSN IDE" for in and press the button "Next".
You don't need
to install the "General Eclipse Enhancements" feature as it is already included in the "WUDSN IDE" feature".
- Review the installation details and press the button "Next".
- Read the license agreement, choose the option "I accept..." and press the button "Finish".
- In case you get a security warning that the content is unsigned, confirm the warning by pressing the button
"OK".
- When you are prompted to restart Eclipse now, press the button "Yes".
- As always with updates, it may happen that the update fails for whatever reason or the installed version turns
out to have severe issues. For example, the required Java version might not be available on your machine. In
this case, you can uninstall it via the link "What is already installed" in the "Install New Software..." dialog
and restart the IDE. Then you can reinstall the latest version from "https://www.wudsn.com/update" or previously
released versions from the locations listed in the "Releases" chapter.
Installing compilers like ATASM, MADS, XASM... » top
- Start Eclipse
- Select the entry "Preferences" from the menu "Window" (in Windows and Linux) or the menu "Eclipse" (in Mac OS X)
- Open the preferences page "Assembler/Atari 8-bit Compilers" or the respective page for your platform.
- Select the tab for the compiler of your choice.
The following compilers are or will be supported:
| Compiler |
Default Target Platform |
| ACME |
C64 |
| ASM6 |
NES |
| ATASM |
Atari 8-bit |
| DASM |
Atari 2600 |
| KickAss |
C64 |
| MADS |
Atari 8-bit |
| XASM |
Atari 8-bit |
| TASS |
C64 (in preparation) |
- Click the "Download" link to open the home page of the compiler.
- Follow the instruction on the download site to install the compiler to the folder of your choice.
- Alternatively, you can download the single archive containing all supported 6502 compilers including the Linux and Mac OS
X versions where available. The archive contains a readme file with the date of the last update and the included
compiler versions.
| Compiler |
Operating System |
Architecture |
Compiler Version |
Executable Path |
Compilation Date |
Compiled By |
| ACME |
Windows |
Intel - 32 bit |
0.90 |
ACME / acme.exe |
2006-03-19 |
Krzysztof Dabrowski |
| ASM6 |
Windows |
Intel - 32 bit |
1.6 |
ASM6 / asm6.exe |
2011-03-11 |
loopy |
| ATASM |
Windows |
Intel - 32 bit |
1.07 (non-final) |
ATASM / atasm.exe |
2010-05-10 |
M. Schmelzenbach |
| ATASM |
Mac OS X |
Intel |
1.07 (non-final) |
ATASM / atasm.macosx-i386 |
2015-05-01 |
JAC! |
| ATASM |
Mac OS X |
PowerPC |
1.07 (non-final) |
ATASM / atasm.macosx-powerpc |
2015-05-01 |
JAC! |
| ATASM |
Linux |
Intel - 32 bit |
1.07 (non-final) |
ATASM / atasm.linux-i386 |
2015-05-01 |
JAC! |
| ATASM |
Linux |
Intel - 64 bit |
1.07 (non-final) |
ATASM / atasm.linux-x86-64 |
2015-05-01 |
JAC! |
| DASM |
Windows |
Intel - 32 bit |
2.20.11 |
DASM / bin / dasm.exe |
2015-05-08 |
JAC! |
| DASM |
Mac OS X |
Intel |
2.20.11 |
DASM / bin / dasm.macosx-i386 |
2015-05-01 |
JAC! |
| DASM |
Mac OS X |
PowerPC |
2.20.11 |
DASM / bin / dasm.macosx-powerpc |
2015-05-01 |
JAC! |
| DASM |
Linux |
Intel 32-bit |
2.20.11-20140304 |
DASM / bin / dasm.linux-i386 |
2015-05-01 |
JAC! |
| DASM |
Linux |
Intel 64-bit |
2.20.11-20140304 |
DASM / bin / dasm.linux-x86-64 |
2015-05-01 |
JAC! |
| KickAss |
All |
Java |
V3.39 |
KICKASS / KickAss.jar |
2015-03-26 |
Mads Nielsen |
| MADS |
Windows |
Intel - 32 bit |
2.0.7 (new features since 1.9.0 are not fully supported in WUDSN IDE yet) |
MADS / mads.exe |
2014-05-20 |
JAC! |
| MADS |
Mac OS X |
Intel - 32 bit |
2.0.7 (new features since 1.9.0 are not fully supported in WUDSN IDE yet) |
MADS / mads.macosx-i386 |
2017-11-05 |
JAC! |
| MADS |
Mac OS X |
Intel - 64 bit |
2.1.0 (new features since 1.9.0 are not fully supported in WUDSN IDE yet) |
MADS / mads.macosx-x64 |
2021-03-26 |
John Paul Jones |
| MADS |
Mac OS X |
PowerPC |
2.0.7 (new features since 1.9.0 are not fully supported in WUDSN IDE yet) |
MADS / mads.macosx-powerpc |
2017-11-05 |
JAC! |
| MADS |
Linux |
Intel - 32 bit |
2.0.7 (new features since 1.9.0 are not fully supported in WUDSN IDE yet) |
MADS / mads.linux-i386 |
2017-11-05 |
JAC! |
| TASS |
Windows |
Intel - 32 bit |
1.46 r38 |
TASS / 64tass.exe |
2011-07-03 |
Soci |
| XASM |
Windows |
Intel - 32 bit |
3.1.0 |
XASM / xasm.exe |
2014-07-20 |
0xF |
| XASM |
Linux |
Intel - 32 bit |
3.1.0 |
XASM / xasm.linux-i386 |
2014-07-20 |
0xF |
| XASM |
Mac OS X |
Intel - 32 bit |
3.1.0 |
XASM / xasm.macosx-i386 |
2014-07-20 |
0xF |
- In the section "Browse..." button for the field "Path to Compiler" to locate the executable.
- If not explicit compiler parameters are specified, the default parameters are used.
- If explicit compiler parameters are specified, the default parameters are ignored.
- The variable "${sourceFilePath}" is replaced by the absolute path to the source file.
The variable
"${outputFilePath}" is replaced by the absolute path to the output file.
For more variables see section
preferences for compiling.
- Choose if you want to use the source folder or the temporary folder as the output folder.
- Choose the file extension for the output file, for example, ".xex" or ".bin"
- Press the button "OK".
- Using the button "Restore Defaults" all values are reset, except for the paths to the compilers.
- Using the button "Default" in the "File Associations" preferences you can set the default editor for a file
extension, for example, "MADS" for "*.asm".
Installing Atari800Win and other emulators » top
- Start Eclipse.
- Select the entry "Preferences" from the menu "Window" (for Windows and Linux) or "Eclipse" (for Mac OS X).
- Open the preferences page "Assembler/Atari 8-bit Compilers" and select to tab for your compiler.
- The field "Default Application to open Output File" is defaulted to "Operating System Default Application".
- If you have the emulator registered as the default application for the extension of the output file, for
example, "Atari800Win" or "Atari800MacX" for ".xex", you don't need to configure anything in addition
and can skip the steps below.
- If your operating system, like for example Linux, does not support default applications or if you need a
special output file extension and special parameters to open the output file in the emulator you can
choose the emulator in the field "Application to open Output File" and configure the command line on the
corresponding tab.
- You can also use the "User Defined Application" to open the output file with an arbitrary application
like a script, linker, or whatever.
- If you have not yet downloaded the corresponding emulator, you can use the download link on the tab of the
emulator and follow the instructions on the download site to install the emulator.
- Use the "Browse..." button for the field "Path to Application" to locate the executable. If required you can
specify your own command-line based on the default command line displayed.
Note: Under Mac OS-X, you must
specify the path to the actual executable inside the ".app" folder. To see this path you have to select "Show
Package Contents" in the context menu of the ".app" folder. For the "Stella" emulator installed in the
"/Applications/Stella.app" folder this means "/Applications/Stella.app/Contents/MacOS/Stella".
- If no explicit command line is specified, the default command line is used.
- If an explicit command line is specified, the default command line is ignored.
- The variable "${runnerExecutablePath}" is replaced by the path to the application executable.
The
variable "${outputFilePath}" is replaced by the absolute path to the output file.
For more variables see
section preferences for compiling.
- Press the button "OK".
- In case you also need the Atari ROM files, you can find them in the file PCXF380.ZIP which is available at http://www.emulators.com.
Creating and compiling an example project » top
