HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
open-watcom
open-watcom-v2
C2016–2026
open-watcom / open-watcom-v2

open-watcom-v2

Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.

13Distinct people
19Mentions
1Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I do some light hacking in iDOS for fun as well. Might as well go straight to Borland C++ 3.1 [0] (the "professional" version) over Turbo C++ these days. When you eventually…

mezentius used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year19 dated mentions

Observed mentions: 2016-07-24 16:45:09 UTC to 2026-10-01 00:29:08 UTC.

01232016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

19 sources
I guess it made a lot of sense to implement compilers in 32-bit protected mode to get more space to work with easier? Free Pascal's compiler also requires 32-bit even if it can generate 16-bit DOS code as well (at least when cross-compiling from some other OS; I have not tried to cross-compile from DOS 32-bit compiler to DOS 16-bit executable). Some people (and by that I mean Debian people; not sure about anyone else) disagree about OpenWatcom being free software. The license has some unusual requirement(s). There has been talk for a long time about possibly fixing that, but I do not know how on track that is (or how much it matters, in practice): https://github.com/open-watcom/open-watcom-v2/discussions/27...
In Writing FreeDOS Programs in C
I have 3 envs on my Windows work laptop 1. PellesC => small C+win32 hobby 2. Msys2+mingw64 => main env for rust too 3. Clang-LLVM + Windows SDK + Cmake + jom (and Windows CRT from C3 install) => Works fine https://github.com/llvm/llvm-project/releases/download/llvmo... (I use 3 for D too) 4. I would like to add to your guide compiling with OpenWatcom V2 (https://github.com/open-watcom/open-watcom-v2) 5. Cygwin they have latest GCC 15 in testing 6. Winlibs or equation.com mingw distros
In Getting C++ Hello World working on Windows (a comedy & tragedy)
mezentius·Sep 5, 2024Recommendation phrase
I do some light hacking in iDOS for fun as well. Might as well go straight to Borland C++ 3.1 [0] (the "professional" version) over Turbo C++ these days. When you eventually hit the Great Wall of 16-bit real mode, I recommend switching to OpenWatcom [1], aka "the compiler that built Doom," which comes with something closer (relatively speaking) to a modern toolchain. DJGPP [2] has been recommended as well, although I found it more trouble to set up. [0] https://winworldpc.com/product/borland-c/30 [1] https://github.com/open-watcom/open-watcom-v2 [2] https://www.delorie.com/djgpp/
In Ask HN: Any Recommendations Around Programming on an iPad?
I should note, that OpenWatcom 2.0[1] is far better for supporting more recent C and C++ code, modern hosts and tooling, but still able to compile into 16 bit code. It is also actively maintained. Instead of MASM I recommend JWasm[2] + Jwlink[3]. Back in time I did a fork[4] of JWasm that has cleaner build system (CMake). [1] https://github.com/open-watcom/open-watcom-v2 [2] https://github.com/Baron-von-Riedesel/JWasm [3] https://github.com/JWasm/JWlink [4] https://github.com/JWasm/JWasm
In Win16 Retro Development
The most recent commit for OpenWatcom, which is what I originally asked about, was 4 hours ago[1] at time of writing. [1]: https://github.com/open-watcom/open-watcom-v2/commit/ac10ed3... (FWIW: I'm in agreement with you that DMC++ is likely superior, I'm more curious about what OpenWatcom's deficiencies in relation to it are, and I reckon there are probably only a few people as familiar and qualified than yourself to comment)
In How FreeDOS Grew Up and Became a Modern DOS (2021)
> I would like something that works uniformly across Windows, Linux desktop (such as XFCE, GNOME, KDE), and macOS. Löve [0] has a great approach to cross-platform deployment [1]. It's not exactly constrained when you compare it to QBasic, but of course using only a subset of its modules is no problem :) Of course the closest equivalent is … DosBox! Runs on basically every system, does graphics and sound and not much else :) Btw., Watcom in Open Source now [2]. IIRC Retro City Rampage 486 was made with that. [0] https://love2d.org/ [1] https://love2d.org/wiki/Game_Distribution [2] https://github.com/open-watcom/open-watcom-v2
In Software Library: MS-DOS Games

Showing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.