Skip to content

Commit 9a10ada

Browse files
committed
Remove .com from README
1 parent 0c12c26 commit 9a10ada

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -92,8 +92,8 @@ guaranteed to be compatible and furthermore includes our extensions for
9292
doing build system sandboxing.
9393

9494
```sh
95-
build/bootstrap/make.com -j8
96-
o//examples/hello.com
95+
build/bootstrap/make -j8
96+
o//examples/hello
9797
```
9898

9999
Since the Cosmopolitan repository is very large, you might only want to
@@ -103,30 +103,30 @@ depends on core LIBC packages.
103103

104104
```sh
105105
rm -rf o//libc o//test
106-
build/bootstrap/make.com o//test/posix/signal_test.com
107-
o//test/posix/signal_test.com
106+
build/bootstrap/make o//test/posix/signal_test
107+
o//test/posix/signal_test
108108
```
109109

110110
Sometimes it's desirable to build a subset of targets, without having to
111111
list out each individual one. For example if you wanted to build and run
112112
all the unit tests in the `TEST_POSIX` package, you could say:
113113

114114
```sh
115-
build/bootstrap/make.com o//test/posix
115+
build/bootstrap/make o//test/posix
116116
```
117117

118118
Cosmopolitan provides a variety of build modes. For example, if you want
119119
really tiny binaries (as small as 12kb in size) then you'd say:
120120

121121
```sh
122-
build/bootstrap/make.com m=tiny
122+
build/bootstrap/make m=tiny
123123
```
124124

125125
You can furthermore cut out the bloat of other operating systems, and
126126
have Cosmopolitan become much more similar to Musl Libc.
127127

128128
```sh
129-
build/bootstrap/make.com m=tinylinux
129+
build/bootstrap/make m=tinylinux
130130
```
131131

132132
For further details, see [//build/config.mk](build/config.mk).
@@ -179,11 +179,11 @@ end
179179
src
180180
```
181181

182-
You normally run the `.com.dbg` file under gdb. If you need to debug the
183-
`.com` file itself, then you can load the debug symbols independently as
182+
You normally run the `.dbg` file under gdb. If you need to debug the
183+
`` file itself, then you can load the debug symbols independently as
184184

185185
```sh
186-
gdb foo.com -ex 'add-symbol-file foo.com.dbg 0x401000'
186+
gdb foo -ex 'add-symbol-file foo.dbg 0x401000'
187187
```
188188

189189
## Platform Notes

0 commit comments

Comments
 (0)