The following assumes that you have already installed SPIDER.
The screenshots below are mostly from Eclipse 4.4 on Windows 7 but both SICStus and Eclipse looks almost the same on other platforms, such as Linux and macOS, and the same or similar steps should be performed on all platforms. Note that current versions of SPIDER requires a newer version of Eclipse, see the prerequisites page for details.
Full-size versions of the screenshots will open in a separate window when the thumbnail is clicked.
test :- write('This is a test'), nl.
SICStus runs within Eclipse and interacts via the SICStus top-level view.
Some special commands are available by using the buttons at the top-right of the view. There is an interrupt button (with a "Pause" icon) as well as a command history mechanism.
There is a, currently invisible, divide between the input area at the bottom of the SICStus view and the output area. The output area is read-only, you can only enter new text in the input area.
Of course, it is also possible to call compile/1 et al. directly from SICStus.
You run your code from the SICStus top-level, as usual.
First select (or create) a Prolog project and a folder within that project where you would like the link to the external folder to appear. Then chose New Folder from the File menu.
In the New Folder dialog the Advanced button will allow you to create the folder as a link to your existing folder. It is a good idea to restart Eclipse after you have added all needed links.
You enable the debugger using the trace/0 command etc. as usual.
When you then enter the Prolog debugger Eclipse will ask whether you want to switch to the SICStus Prolog Debug Perspective, a Perspective optimized for debugging. You should let Eclipse switch perspective.
You can switch between perspectives using the Window menu or by using the perspective buttons in the upper right corner of the Eclipse Window.
The SICStus Prolog Debug Perspective shows the Debug view in the upper right-hand corner. Its buttons correspond to variants of common Prolog debugger commands.
The Breakpoints view shows breakpoints. You can set spy-points and line breakpoints by double clicking in the left margin in a Prolog editor window (setting a breakpoint at the first like of a predicate will create a spy-point, other lines will create a line breakpoint).
The Variables view shows bindings for variables at the current debugger location.