Mail Archives: djgpp/1998/07/31/22:30:31
On 8 Jun 1998 12:27:54 GMT, slapierr AT acs2 DOT acs DOT ucalgary DOT ca (Soleil Lapierre) wrote:
>Hi. Sorry if this has been covered, but I tried DejaNews and looked in
>all the documentation that seemed appropriate.
>
>A while back I was working on a C++ project using RHIDE and DJGPP and
>NASM. This project had lots of source files - over a dozen if I recall
>correctly. (I'm using DOS 7, BTW)
>
>Anyway, after the project grew to a certain number of files, linking
>would fail under RHIDE. By playing around with the number of optimization
>flags I had turned on, I discovered that the problem was that the command
>line was getting chopped off. So I made a makefile. Shelling out and
>running make worked fine, no matter how long the command line it generated.
>
>My question is this: Is there a way around this command line length
>limitation in RHIDE? It's a hassle to shell out every time I want to
>rebuild.
>
>BTW, my compliments to the authors. RHIDE, DJGPP and NASM are
>excellent tools and I appreciate having them around.
>
>--
>/* Soleil "Ra" Lapierre http://www.cuug.ab.ca/~lapierrs/
> *
> * Birdie num-nums.
> */
Don't quote me on this, but i'm 99% sure that there's NO way to change how RHIDE does it's compiling & linking. I ran into a problem a while ago where i wanted RHIDE to say "gnatmake this_file" instead of it's normal method of compiling & linking a file, and i found there's no way to do it.
Well, there is a way... get the source to RHIDE and reprogram it to work for bigger command lines. Either that or complain to the author. The only problem with messing around with RHIDE source is that it requires other sources, too. like sources to a port of a TurboVision libary, and i think to SET's editor. Anything that RHIDE requires is available off the internet, but i'm just saying it's a hassle.
-**** Posted from Supernews, Discussions Start Here(tm) ****-
http://www.supernews.com/ - Host to the World's Discussions & Usenet
- Raw text -