Zeus IDE

Posted: **Fri Oct 08, 2004 7:57 am**

I want to use the C programming langauge and i am a beginner and i set it up right but it can not include stdio.h and i typed in

#include <stdio.h>

where should i put the include folder so it can find it?

Posted: **Fri Oct 08, 2004 7:59 am**

oh and i am trying to use the free borland compiler with it

Posted: **Fri Oct 08, 2004 2:28 pm**

I want to use the C programming langauge and i am a beginner and i set it up right but it can not include stdio.h and i typed in
#include <stdio.h>
where should i put the include folder so it can find it?

oh and i am trying to use the free borland compiler with it

The last time I used the Borland C 5.0 compiler I recall it seem to know how to find the compiler include files, so for now leave the include files where they are.

To start, check that the compiler is in fact correctly installed as follows:

Start Zeus
Tools, DOS Command Line menu
Enter bcc32.exe as the argument and hit the run button

This should produce the following output:

Code: Select all

Borland C++ 5.0 for Win32 Copyright (c) 1993, 1996 Borland International
Syntax is: BCC32 [ options ] file[s]     * = default; -x- = turn switch x off
  -3    * 80386 Instructions        -4      80486 Instructions
  -Ax     Disable extensions        -B      Compile via assembly
  -C      Allow nested comments     -Dxxx   Define macro
  -Exxx   Alternate Assembler name  -Hxxx   Use pre-compiled headers
  -Ixxx   Include files directory   -K      Default char is unsigned
  .............

If you get this instead:

Code: Select all

The name specified is not recognized as an internal or external command, operable program or batch file.

then the installation is broken. This is most likely because the Borland installation directory is not in the PATH. Add the install directory to the Path using the System Icon found in the Control Panel, restart Zeus and repeat the test until it works.

Once the Borland installation is correct, edit the C/C++ Document Type using the instructions found in the Configuring Zeus to Run a Third Party Compiler example and use the following as the compiler string:

Code: Select all

bcc32.exe -c $fn

To test the configuration do the following:

Options, Editor Options menu
In the General panel enabel the Help debug tools macros and executables option
Open a c/c++ source file
Use the Compiler, Compile menu to run the compile

You should see this output:

Code: Select all

bcc32.exe -c $fn
Debug: Changed to the 'c:\temp\' directory supplied
Debug: Command: bcc32.exe -c c:\temp\test.c
--------------------Configuration: <default settings> - Release--------------------
Using document type compiler options....

Debug: Command Line: C:\WINNT\system32\cmd.exe /c bcc32.exe -c c:\temp\test.c
Debug: Started Process ID: 0x54

Borland C++ 5.0 for Win32 Copyright (c) 1993, 1996 Borland International
c:\temp\test.c:

Notice the following line of output:

Code: Select all

Debug: Command Line: C:\WINNT\system32\cmd.exe /c bcc32.exe -c c:\temp\test.c

This shows the compiler command line that was used. Also notice these two lines of output:

Code: Select all

--------------------Configuration: <default settings> - Release--------------------
Using document type compiler options....

They give feedback as to which options are being used. In this case the compiler is using the document type compiler options.

Finally notice that at least in this case the compile has worked

If the compiler output does complain an error message regarding missing include files, go back to the C\C++document type[\b] and change the command line to read:

Code: Select all

bcc32.exe +c:\temp\my_options.cfg $fn

Next create a file called c:\temp\my_options.cfg that contains this information:

Code: Select all

-c -w
/Ic:\bc5\include;

The first line sets the compile only and warnings options and the second line defines the location of the Borland include files. Change the second line to point to your include files and run the compile again.

If after setting up the compiler it is still not working, post the contents of the compiler output window to the end of this thread and I am sure I will be able to get it working.

Jussi