Mail Archives: djgpp/2010/03/30/15:15:36
Hi,
On Mar 28, 3:42=A0pm, Pablo Marty <tigrepotrazosalv DOT DOT DOT AT yahoo DOT com DOT ar>
wrote:
>
> I realised that to find the bugs in my game that only crashes sometimes
> under DOSBox, I have to run it from RHIDE under DOSBox, so that the
> RHIDE error-detector will highlight the code lines where the errors (run
> time, something like overpass an array limit)=A0occured; under Windows it
> doesn't crash but Allegro sound is not allowed,=A0that's why=A0I have=A0t=
o make
> it run under DOSBox, because the music sounds correctly=A0
Okay.
> When I try to run my program from the Run command it compiled all the
> files perfectly, but at link moment, it said "Command line too long" ...
> I suposse that I should change something in "Linker Options", but I have =
no
> idea, ... does anyone of you knows? thank you
I don't use RHIDE, but I know DOSBox isn't LFN-aware, hence you're
probably exceeding the 126-byte limit of the cmdline. It also doesn't
properly truncate LFNs to 8.3 like real DOS, which can cause issues.
(IIRC, trying that once before actually crashed DOSBox for me, hence
why I no longer try compiling under there.)
A workaround would be to convert your .gpr (project) to .mak
(makefile) and try again. Perhaps you'll have to use a @list file to
overcome the 126-byte limit, e.g. "ld @myfiles.txt", but I can't guess
from here. ;-)
Actually, if you use GNU Emacs, you can jump directly to the compile
errors too. RHIDE is just somewhat easier due to built-in debugger,
easier interface, etc. Too bad it doesn't work under modern
Windows. ;-(
- Raw text -