Skip to content

Commit c112db2

Browse files
committed
Remove references to cygwin in favour of Windows instead
Because cygwin is not tested in CI and because this means that we can list operating systems rather than a mix of operating systems and tool chains.
1 parent d34fc86 commit c112db2

File tree

1 file changed

+1
-62
lines changed

1 file changed

+1
-62
lines changed

COMPILING.md

Lines changed: 1 addition & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ following environments:
55

66
- Linux
77
- MacOS X
8-
- Microsoft Visual Studio 2019
8+
- Windows
99

1010
The above environments are currently tested as part of our continuous
1111
integration system. It separately tests both the CMake build system and the
@@ -17,7 +17,6 @@ past, but are not actively tested:
1717

1818
- Solaris 11
1919
- FreeBSD 11
20-
- Cygwin
2120

2221
# Building using CMake
2322

@@ -203,66 +202,6 @@ Follow these instructions:
203202
make -C jbmc/src
204203
```
205204
206-
## COMPILATION ON WINDOWS WITH CYGWIN
207-
208-
There are two options: the Visual Studio compiler with version 14 (2015) or
209-
later, or the MinGW cross compiler with version 5.4 or later.
210-
We recommend Visual Studio.
211-
212-
Follow these instructions:
213-
214-
1. First install Cygwin, then from the Cygwin setup facility install the
215-
following packages: `flex, bison, tar, gzip, git, make, wget, patch,
216-
curl`.
217-
2. Get the CBMC source via
218-
```
219-
git clone https://github.com/diffblue/cbmc cbmc-git
220-
cd cbmc-git
221-
```
222-
3. Depending on your choice of compiler:
223-
1. To compile with Visual Studio, change the second line of `src/config.inc`
224-
to
225-
```
226-
BUILD_ENV = MSVC
227-
```
228-
Open the Developer Command Prompt for Visual Studio, then start the
229-
Cygwin shell with
230-
```
231-
bash.exe -login
232-
```
233-
Please note that this might open a different shell instead, especially if
234-
you have installed other Linux subsystems previously. To verify that you
235-
are in the correct shell, make sure that the Windows file system can be
236-
accessed via the folder`/cygdrive`. If the command above does not open
237-
the Cygwin shell, you can also access it by using its absolute path,
238-
`C:\cygwin64\bin\bash.exe` by default. In the Developer Command Prompt,
239-
simply type
240-
```
241-
C:\cygwin64\bin\bash.exe -login
242-
```
243-
2. To compile with MinGW, use Cygwin setup to install a mingw g++ compiler
244-
package, i.e. one of `mingw{32,64}-{x86_64,i686}-gcc-g++`. You may also
245-
have to adjust the section in `src/common` that defines `CC` and `CXX`
246-
for BUILD_ENV = Cygwin.
247-
Then start the Cygwin shell.
248-
4. To compile CMBC, open the Cygwin shell and type
249-
```
250-
make -C src DOWNLOADER=wget minisat2-download
251-
make -C src
252-
```
253-
5. To compile JBMC, you additionally need the JDK and Maven 3, which have
254-
to be installed manually. Then open the Cygwin shell and type
255-
```
256-
make -C jbmc/src setup-submodules
257-
make -C jbmc/src
258-
```
259-
260-
(Optional) A Visual Studio project file can be generated with the script
261-
"generate_vcxproj" that is in the subdirectory "scripts". The project file is
262-
helpful for GUI-based tasks, e.g., the class viewer, debugging, etc., and can
263-
be used for building with MSBuild. Note that you still need to run flex/bison
264-
using "make generated_files" before opening the project.
265-
266205
## COMPILATION ON SOLARIS 11
267206
268207
We assume Solaris 11.4 or newer. To build JBMC, you'll need to install

0 commit comments

Comments
 (0)