>  RL> You see, GCC was developed under unix, and rather than go to a lot of
> work
>  RL> porting it they just use a .dll that emulates unix.
>  RL> (foreward slashes for filenames,
> Wrong, the OS/2 Dos Subsystem does this.

Does it?  I never really used the unix emulation.

>  RL> manager and everything.  If you have the developer's toolkit, you can
> even
>  RL> use SOM.)
> But not (yet) SOM2. According to EM, this has never been tested. The
> accompanying sample uses SOM1.

All the som stuff is in the toolkit.  It's seperate from the compiler.  If
the same som toolkit can create header files that work with Cset++, Watcom,
BC++, and metaware, it should work with EMX.

It's fairly straightforward, in a twisted peverted sort of mind-numbing way.

>  RL> that whenever you create a .dll file you need a .def file as one of the
>  RL> source files, but if you're just making text mode .exe files then all
> you
>  RL> need are normal C source files
> DLLs are not limited to PM/WPS programming. You can as well use DLLs for
> textmode applications.

I never said they were.  You're thinking .rc files.  Those are PM/WPS. 
.def are for .dll's.

They overlap considerably, of course, since the PM is made out of dll's,
and you can use .rc files to store text strings for a text mode program...

I see the source of the confusion:  "If you're just making text mode
.exe files then all you need are normal c source files."

For PM apps you need .rc files.  For .dll's you need .def files.  If either
the "text" or the ".exe" qualification goes away, you
need another file.

Well, .lib files don't...

Rob
 
--- Xblat