Opened 14 years ago

Closed 13 years ago

Last modified 13 years ago

#26 closed enhancement (wontfix)

OpenWatcom build

Reported by: abwillis Owned by: abwillis
Priority: minor Milestone: compiler switch
Component: odin Version:
Severity: low Keywords:
Cc:

Description

I did some work with Michal Necasek to get Odin to build with Open Watcom. It does not build but this ticket is for any work toward that goal.

Change History (7)

comment:1 by abwillis, 14 years ago

Allow WRC to build with Open Watcom: Committed revision 21551

comment:2 by dmik, 14 years ago

Can you give a rationale of making Odin build with OW? It's clear why we should not work on building it with VAC (because it's dead and forever bogus). OW is more alive it seems but still, why?

comment:3 by abwillis, 14 years ago

Type: defectenhancement

The primary reason being OW being Open Source, active and available is better than VAC. I put some time in a few years ago with Michal and while it is not working yet, much of what is necessary is already in place in the build system. Some of what stymied me at the time I have since learned more and have gotten past some of that.

comment:4 by Silvan Scherrer, 14 years ago

btw there is also a ticket to move the compiler to gcc. as we are condidering of doing that.

comment:5 by Silvan Scherrer, 14 years ago

Milestone: compiler switch

comment:6 by dmik, 13 years ago

Resolution: wontfix
Severity: low
Status: newclosed

I don't think that there is any sense to make it build with Open Watcom after we switched to GCC (see #19). The current GCC build is pretty stable now (with a few known limitations that are about to get fixed for the next release) and GCC itself is the best modern compiler for OS/2 that is being constantly improved anyway.

comment:7 by dmik, 13 years ago

If, though, anybody decides to do that, he should keep in mind that we now use kBuild to build Odin and kBuild has some Watcom support already. So most work will have to be done in the area of adopting the source code to Watcom LIBC etc.

Note: See TracTickets for help on using tickets.