Dolphin Smalltalk Core Image
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
This repository contains: * A VS2019 solution to build the Virtual Machine (VM) elements of Dolphin Smalltalk. * The necessary Smalltalk packages to build the Dolphin Smalltalk Core Images from a pre-built boot image.
It is not necessary to build the VM, since pre-built binaries are available for download from github using the FetchVM script in the repo. You can skip straight to building the product image if you wish.
First clone the Dolphin repo to a
\Dolphindirectory on your machine. It can actually be any location but for convenience we'll call it
\Dolphin. Use a Git client tool to clone. Downloading the ZIP file won't work due to use of Git LFS.
Versions prior to 7.1: You should also clone the separate VM repository (DolphinVM) into a
Version 7.1 and later: The DolphinVM repository has been merged into the main Dolphin repository and can be found in the
Core\DolphinVMfolder. The history from the original repository has been retained.
Install the free VS2019 Community Edition on your machine with the "Desktop development with C++" workload. The Dolphin VM is a set of C++ projects so make sure to install this option (it's not the default) or you'll end up only being able to compile C#. You can use the Pro or Enterprise edition if you have it. It is possible to compile the VM with earlier versions of VS (certainly VS2017) but you will need to downgrade the solution to the appropriate toolset and either retarget to the ealier Windows SDK that shipped with VS, or install the latest SDK standalone.
Load the DolphinVM solution into Visual Studio. Choose the Release profile (Debug will compile but will run slowly) and then Build Solution. A bunch of DLLs and
Dolphin7.exewill have been copied to the
Follow these instructions to create the product image and launch Dolphin Smalltalk for the first time.
First clone the Dolphin repository (this one) into a suitable working directory on your machine, let's call it
\Dolphin. Any supported version of Windows should be suitable, and at the moment that means Windows 10. Dolphin may run on older Windows versions, but there should be no expectation that it will, or will continue to do so.
The master branch is on the bleeding edge and may represent an unstable state, although the tests should always be passing. If you want a stable build then you may want to go back at least to the last tagged version.
Next you will need to build the binaries as described above, or fetch the VM binaries. For convenience a batch file,
FetchVM.CMDis supplied and, providing you have PowerShell scripting enabled, you can just double-click this to pull the correct version of the VM down from GitHub. Alternatively, you can right click on the
FetchVM.ps1file and choose Run with PowerShell, which does not require scripting to be explicitly enabled in Windows. If you supply a parameter to either of these script files you can choose to fetch an alternative VM version to the default (not usually recommended).
Before proceeding you will also need to pull the boot image from github large file storage. To do this execute
git lfs pull.
If you do not have a Visual Studio 2019 installed on your machine, then depending on what other software you have you may also need to install the VC++ runtime distribution, specifically https://aka.ms/vs/16/release/vc_redist.x86.exe. This is required by the VM. If Dolphin fails to start, try installing this first.
In the root folder of the repo you will find the
BootDPRO.cmdscript and a small boot image,
BootDPRO.cmdor run it from a console window. When the boot process has completed, you should see a
DPRO.img7file in your directory. IMG7 is the image extension for Dolphin 7, and DPRO stands for Dolphin Professional.
Should you wish to test your booted image before proceeding with your own changes or work, you may want to run the standard regression test suite. This is recommended, and easy to do. Just run the
TestDPRO.cmdscript in the root folder. This will launch Dolphin, load the tests, and then execute them. As it runs you will see results being reported as console output. When complete a summary will state whether there were any failures. You should expect there to be none, but check the AppVeyor build to see the current build status.
To launch the image you can right click on
DPRO.img7and choose Open With, selecting
Dolphin7.exeas the executable to be permanently associated with this file type.
You should see Dolphin Professional 7 launch successfully. You can now continue with the Dolphin Getting Started introduction if you wish.
If you want to submit changes, you will need to create your own fork and clone that instead. You will not be able to push directly to the main Dolphin repo.
No further changes will (normally) be accepted into the DolphinVM repo for versions of Dolphin from 7.1, although it remains open for bug fixes to 7.0. If you wish to contribute to the 7.1 VM, please make and commit your VM changes in this main Dolphin repo and submit a PR here. PRs can contain synchronized changes to both the VM and the image, and the PR validation build will exercise both.
Any contributions are welcome, but are expected to be of a very high standard. You are more likely to have your contribution accepted unchanged if you follow these rules: - PRs should be associated with an pre-existing issue. In other words, create a github issue describing your bug or proposed improvement first. This allows the merits of the change to be discussed and should save wasted time preparing a PR that is rejected because the change is not agreed on principle. - Source code should follow good Smalltalk style principles and designs should be simple and clear. The existing image is full of many examples of good practice. - Source must be formatted using the standard in-image code formatter for consistency. - Changes should be accompanied by tests that cover the mainstream scenario and boundary conditions. This applies even if there are no existing tests. Exceptions are unlikely to be made to this rule.
If sufficient changes have been made to the VM or image such that a new release is warranted, you can push a new tag of the form v.7.x.y (eg: v7.0.42). When the tag is eventually pushed to the GitHub master branch (by a maintainer) this will trigger an AppVeyor to build and generate a new Release. Each release consists of the full set of VM binaries wrapped up as a zip called
DolphinVM.zip, and associated PDBs (native debug information for the binaries). The
FetchVMscript will automatically download the correct set of binaries associated with the latest tag at which the repository is checked out.