Mail Archives: djgpp/1998/04/18/05:54:25
Michael Vanecek,
Well, here's what I have so far. I renamed rsxntdj's lib to ~~lib, and
copied the contents of djgpp's lib over into rsxntdj as lib. Well, lo
and behold - demo.c from allegro, and hello.c from a tutorial in djgpp
compile as happily as ever. But none of the samples from rsxntdj would
compile. Surprised? To confirm a growing hunch, I name the djgpp's lib
in the rsxntdj dir to ~lib, and return rsxntdj's own lib from ~~lib to
lib. Rsxntdj's sample files compile without a hitch, excepting the cplus
program that returns a missing seperator error (<--? any translation to
that one?), but none of the djgpp c files, including allegro's demo.c
would compile.
Hmmm...That would indicate that rsxntdj isn't compatible with djgpp at
all. Or at least this version of djgpp. What would it take to overcome
that? Wouldn't a merger of the two into a single compiling environment
for both dos and Windows be advantagious? It seems that was what rsxntdj
was attempting to do. But since there isn't a web page that I know of
for rsxntdj, or seemingly any continuation of the project, I can assume
that rsxntdj is dead, and djgpp has pressed on and evolved without it.
And this evolution would be the source of my woes. It's too bad, I'd
love to be able to compile both dos and win32 programs right from the
same dir using the same compiler (without spending $500). Now, either I
rename the lib back and forth depending on what I'm working on using a
compiler that no one seems interested in, or I us two different
compilers for my development projects, djgpp and lcc. I wish I was more
adept at programming - I would then offer to revamp rsxntdj into
something that could grow with djgpp. But I'm still in beginner mode for
the time being. Anyone else interested? With direction and as part of a
team, I'd love to help where I can.
Cheers,
Mike
- Raw text -