mirrors/cosmopolitan
1
0
Fork 0
mirror of https://github.com/jart/cosmopolitan.git synced 2025-06-03 03:02:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Stop using .com extension in monorepo

Browse source 
The WIN32 CreateProcess() function does not require an .exe or .com
suffix in order to spawn an executable. Now that we have Cosmo bash
we're no longer so dependent on the cmd.exe prompt.
This commit is contained in:
Justine Tunney 2024-03-02 16:57:56 -08:00
parent c8383f25b4
commit a6baba1b07
No known key found for this signature in database
GPG key ID: BE714B4575D6E328
239 changed files with 2092 additions and 2244 deletions
Download patch file Download diff file Expand all files Collapse all files

2
libc/runtime/efimain.greg.c
View file

@ -160,7 +160,7 @@ static void EfiInitAcpi(struct mman *mm, EFI_SYSTEM_TABLE *SystemTable) {
* -net none \
* -drive format=raw,file=fat:rw:o/tool/viz
* FS0:
* deathstar.com
* deathstar
*
* @see libc/dce.h
*/

12
libc/runtime/getsymboltable.c
View file

@ -88,7 +88,7 @@ static struct SymbolTable *GetSymbolTableFromZip(struct Zipos *zipos) {
}
/**
* Reads symbol table from .com.dbg file.
* Reads symbol table from .dbg file.
* @note This code can't depend on dlmalloc()
*/
static struct SymbolTable *GetSymbolTableFromElf(void) {
@ -109,11 +109,11 @@ static struct SymbolTable *GetSymbolTableFromElf(void) {
* __static_yoink("__zipos_get");
*
* In that case, the symbol table may be read from `/zip/.symtab` which
* is generated by `o//tool/build/symtab.com`. The second strategy is to
* look for the concomitant `.com.dbg` executable, which may very well
* be the one currently executing, or it could be placed in the same
* folder as your `.com` binary, or lastly, it could be explicitly
* specified via the `COMDBG` environment variable.
* is generated by `o//tool/build/symtab`. The second strategy is to
* look for the concomitant `.dbg` executable, which may very well be
* the one currently executing, or it could be placed in the same folder
* as your binary, or lastly, it could be explicitly specified via the
* `COMDBG` environment variable.
*
* Function tracing is disabled throughout the duration of this call.
* Backtraces and other core runtime functionality depend on this.