文件列表:

open_watcom_1.6.0-src\bat\doeb.bat (36, 2006-12-15)
open_watcom_1.6.0-src\bat\eb.bat (225, 2006-12-15)
open_watcom_1.6.0-src\bat\filesize.c (1099, 2006-12-15)
open_watcom_1.6.0-src\bat\makecomm (9021, 2006-12-15)
open_watcom_1.6.0-src\bat\makeinit (337, 2006-12-15)
open_watcom_1.6.0-src\bat\master.ctl (1426, 2006-12-15)
open_watcom_1.6.0-src\bat\stub.c (255, 2006-12-15)
open_watcom_1.6.0-src\bat\unset.bat (138, 2006-12-15)
open_watcom_1.6.0-src\bat\wlink.lnk (537, 2006-12-15)
open_watcom_1.6.0-src\bat\xb.sed (5863, 2006-12-15)
open_watcom_1.6.0-src\bat (0, 2006-12-15)
open_watcom_1.6.0-src\bin\parsedlg.exe (49254, 2006-12-15)
open_watcom_1.6.0-src\bin (0, 2006-12-15)
open_watcom_1.6.0-src\binp\parsedlg.exe (49254, 2006-12-15)
open_watcom_1.6.0-src\binp\wlink.lnk (530, 2006-12-15)
open_watcom_1.6.0-src\binp (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\alpha.mif (623, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\c\alphafmt.c (46129, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\c\alphains.c (30913, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\c\asregs.c (2084, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\c (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\dos386\makefile (118, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\dos386 (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\alphafmt.h (1673, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\alphafmt.inc (4591, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\as_arch.h (1597, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\insenum.inc (2590, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\inslist.h (5661, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\regclass.inc (1718, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h\register.h (2080, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\h (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osi386\makefile (186, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osi386\test\makefile (157, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osi386\test (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osi386 (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osiaxp\makefile (180, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osiaxp\test\makefile (157, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osiaxp\test (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline\osiaxp (0, 2006-12-15)
open_watcom_1.6.0-src\bld\as\alpha\inline (0, 2006-12-15)
... ...

Note: This information and much more is now in the Open Watcom Developer's Guide. To produce a PostScript version go to docs\ps and run wmake hbook=devguide If you have everything set up correctly, you should end up with devguide.ps which you can print or view. ------------------------------------------------------------------------------- Getting up to Speed on Open Watcom ================================== Here's a quick intro on the build layout and build process. Original Sybase build tree was more or less fixed to d:\, Open Watcom is more flexible and the build tree root can be located anywhere. Where this file refers to d:\, substitute your Open Watcom root location (stored in the owroot environment variable). 1) Default build machine layout: d:\ bld - this is the root of the build tree each project we build has a subdirectory under d:\bld for example: d:\bld\cg - code generator d:\bld\cc - C compiler d:\bld\plusplus - C++ compiler etc. (see projects.txt for details) rel2 - this is where the software we actually ship gets copied after it is built - it matches the directory structure of our shipping Open Watcom C/C++/FORTRAN tools. Note: the rel2 directory structure is created on the fly. bat - batch files, many of which aren't used anymore of most interest are the .ctl files - scripts for the "builder" tool (see below) and make init files (makeint et al.). docs - here is everything related to documentation, sources and tools bin - for the rare case where a tool is not available in source form binp - same as above, but containing OS/2 binaries distrib - contains manifests and scripts for building binary distribution packages contrib - 3rd party source code which is not integral part of Open Watcom. Contains primarily several DOS extenders. ------------------------------ 2) To set up a new machine, modify setvars.bat/setvars.cmd/setvars.sh to reflect your setup. See comments within the file for additional information. Your path should look something like this if you are on NT: PATH=C:\WINNT\system32; C:\WINNT; d:\bat; d:\lang\binnt; d:\lang\binw; d:\bin; d:\tools; d:\bld\build\binnt WARNING: Some platforms (notably Windows 9x) require DOS style line endings in batch files. If source files were moved from a UNIX platform. as is the case with ow_daily.tar.bz2, you must make sure that line endings are properly converted. Loading the batch files in an editor such as EDIT and saving them is one way to do this. ------------------------------ 3) Priming the pump: Besides the Open Watcom C/C++ 1.x binaries you'll need a few other executables used by the build process, primarily builder. The source is in \bld\builder. Run wmake in the directory corresponding to your host platform and if you set up everything properly, the executables will be built and copied to the right place. Perhaps someone will fully automate this process one day. For now please consider it an aptitude test. ------------------------------ 4) Build process: ---- Linux note - build process on Linux is somewhat different. It uses gcc to bootstrap Open Watcom, ie. wmake, the C compiler and several other utilities are first built using gcc, then the rest of the tree is built using the freshly created Open Watcom tools. See the build.sh script in the root of the source tree - it should take care of everything. Some of the OW tools are still only available as DOS versions. Under Linux, DOSEMU and FREEDOS need to be installed to be able to do a complete build. In addition: - You need to copy parsedlg.exe from %OWROOT%/bin to %OWROOT%/docs/gml/dos, to keep the dosemu PATH statement short. - In setvars.sh, set DOC_BUILD=1 if you want to build docs. - The setvars.bat file needs to be set up to use D:\ as OWROOT. - The dosemu autoexec.bat needs to have the "unix -e" and the end replaced by: call d:setvars.bat path=d:\docs\gml\dos;%PATH% unix -s GMLINC cdd d:\ unix -s RUNASDOS_CWD cd %RUNASDOS_CWD% cd unix -e RUNASDOS_CMD exitemu ---- We use the Open Watcom C/C++ compilers and Open Watcom wmake to build our tools, but at the top level we have a tool which oversees traversing the build tree, deciding which projects to build for what platforms, logging the results to a file, and copying the finished software into the release tree (rel2), making fully automated builds a possibility. This tool is called builder. See d:\bld\builder\builder.doc for detailed info on the tool and the source if the documentation doesn't satisfy you. Here's how we use it: Each project has a "lang.ctl" builder script file. If you go to a project directory and run builder, it will make only that project; if you go to \bld and run builder, it will build everything the overall build uses \bat\lang.ctl which includes all of the individual project lang.ctl files that we use. Note that if you run builder, it will traverse directories upwards until it finds a lang.ctl (or it hits the root and still doesn't find anything, but then you must have done something wrong). Results are logged to "build.log" in the current project directory (or d:\bld), the previous build.log file is copied to build.lo1. Common commands: builder build - build the software builder rel2 - build the software, and copy it into the "rel2" release tree builder clean - erase object files, exe's, etc. so you can build from scratch Many of the projects use the "pmake" features of builder (see builder.doc). To determine what to build, pmake source is in \bld\pmake. Each makefile has a comment line at the top of the file which is read by pmake. Most of our lang.ctl files will have a line similar to this: pmake -d build -h ... this will cause wmake to be run in every subdirectory where the makefile contains "build" on the #pmake line. You can also specify more parmeters to build a smaller subset of files. This is especially useful if you do not have all required tools/headers/libraries for all target platforms. For example: builder rel2 os_nt will (generally) build only the NT version of the tools. A word of warning: running a full build may take upwards of two hours on a ~1GHz machine. There is a LOT to build! This is not your ol' OS kernel or a single-host, single-target C/C++ compiler. It is generally possible to build specific binaries/libraries by going to their directory and running wmake. For instance to build the OS/2 version of WLINK you can go to \bld\wl\os2386 and run wmake there (note that the process won't successfully finish unless several required libraries are built). Builder is useful for making full builds while running wmake in the right spot is handy during development. ------------------------------ 5) Getting more information: If you have any further questions (and you will if you're serious), visit http://www.openwatcom.org/ and subscribe to the Open Watcom newsgroups at news://news.openwatcom.org/, particularly openwatcom.contributors.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：