| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Borland and EMX ... |
hi Rob,
* Re:
to Andrew Grillet
RL> You see... EMX is a port of a unix package. By default it creates
RL> unix style a.out executable files. OS/2 can run these by 1) sticking
RL> a short little .exe file header onto the beginning of the file (the
RL> program emxbind.exe does this), and 2) using emx.dll to handle the
RL> unix system calls that a.out file is making.
RL> This is slow. This eats ram. But it offers the highest level of
RL> compatability with unix. If you're porting unix stuff to OS/2,
RL> that's the easy way.
And it runs under DOS with the emx.exe program loader and VCPI or the
rsx.exe program loader and DPMI. That capability is the only reason (apart
from debugging) to compile to a.out format. Use GCC (not emx;-) -Zomf
-lwrap -s to compile OS/2 programs that use the RTL DLLs. That way you
spare both RAM and disk space: DLLs are loaded on demand, and their code
and constant data is shared by all their clients. Generally, only stack
and heap space will be privately owned by an application instance then.
regards,
hugo
>> http://www.netresponse.com/zldf
* Origin: (2:283/608.5)SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407 SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809 @PATH: 283/608 6 1 512 396/1 270/101 105/103 42 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.