Borland & wxWidgets!!! Help!!!

Help me!

I recently downloaded wxWidgets from its website, and located it in C:\wx...But when I use the instructions included to compile it with Borland C++ Compiler, I get an error. First, I change the directory to C:\Borland\BCC55\bin...Then I type in make -f C:\wx\wxWidgets-2.6.3\build\msw\makefile.bcc...I press enter, and the compiler tells me that it is unable to open include file "config.bcc"! When I look inside the install.txt included, this is what is says!

Code:

---

Borland C++ 5.0/5.5 compilation
----------------------------------------------------------------

Compiling using the makefiles (updated 24 Sept 02):

1. Change directory to build\msw. Type 'make -f makefile.bcc' to
  make the wxWidgets core library. Ignore the compiler warnings.
  This produces a couple of libraries in the lib\bcc_lib directory.

2. Change directory to a sample or demo such as samples\minimal, and type
  'make -f makefile.bcc'. This produces a windows exe file - by default
  in the bcc_mswd subdirectory.

Note (1): the wxWidgets makefiles assume dword structure alignment. Please
make sure that your own project or makefile settings use the
same alignment, or you could experience mysterious crashes. To
change the alignment, change CPPFLAGS in build\msw\config.bcc.

Note (2): if you get undefined _SQL... symbols at link time,
either install odbc32.lib from the BC++ CD-ROM into your BC++ lib
directory, or set wxUSE_ODBC to 0 in include\wx\msw\setup.h and
recompile wxWidgets. The same applies if compiling using the IDE.

Note (3): If you wish debug messages to be sent to the console in
debug mode, edit makefile.bcc and change /aa to /Tpe in link commands.

Compiling using the IDE files for Borland C++ 5.0: not supported - please
use version 2.4.1 (using the make utility in commandline mode works fine_

Compiling using CBuilder (v1-v6): not supported - please
use version 2.4.1 (using the make utility in commandline mode works fine_

** REMEMBER **

In all of your wxWidgets applications, your source code should include
the following preprocessor directive:

#ifdef __BORLANDC__
#pragma hdrstop
#endif

(check the samples -- e.g., \wx2\samples\minimal\minimal.cpp -- for
more details)

---

Notice the Note (1): the wxWidgets makefiles assume dword structure alignment. Please
make sure that your own project or makefile settings use the
same alignment, or you could experience mysterious crashes. To
change the alignment, change CPPFLAGS in build\msw\config.bcc.! Change the CPPFLAGS to what though? Can anyone please help me!?!

Thanks!
~Matt

Quote:

---

Then I type in make -f C:\wx\wxWidgets-2.6.3\build\msw\makefile.bcc

---

Which isn't what the instructions tell you to do. Have you tried "make -f makefile.bcc" ?

Quote:

---

and the compiler tells me that it is unable to open include file "config.bcc"

---

I doubt the compiler tells you such a thing. Make might - and it might if the currect directory isn't %WXDIR%\build\msw, which might be because of the first thing mentioned.

Yeah, I did try that. Nothing happens. More detail:

I change the directory to C:\wxWidgets-2.6.3\build\msw\. Then I type make -f makefile.bcc, and it tells me that make is not recognized as an internal or external command, program, or whatever else it said. So, what's wrong with it?

PS
I got rid of the folder named "wx", to shorten the filepath.

I use MinGW/gcc so I'll do my best here:

Is Borland's bin folder (which I presume is also where your compiler/linker/etc is) not in your PATH? You might consider putting it there, which would allow you to call make anywhere.

(PATH is an evironment variable that is a list of directories. Anything in the listed directories can be called from any directory. Google it.)

Quote:

---

Is Borland's bin folder (which I presume is also where your compiler/linker/etc is) not in your PATH? You might consider putting it there, which would allow you to call make anywhere.

(PATH is an evironment variable that is a list of directories. Anything in the listed directories can be called from any directory. Google it.)

---

If you don't want to modify your path variable for some reason, type the full path to your make executable:

Code:

---

C:\wxWidgets-2.6.3\build\msw>\borland\bin\make -f makefile.bcc

---

I can't think of any reason you wouldn't want to modify your path variable, though. (Unless it already takes up 512 bytes, in which case you can change the size of it with a parameter to command.com in config.sys.)

Quote:

---

Originally Posted by dwks

If you don't want to modify your path variable for some reason, type the full path to your make executable:

---

I thought of that too - I was concerned that if the wx makefile tried to call make, then that might backfire. (But $(MAKE) or w/e it is might fix that).
Furthermore, if his compiler/linker are in the same folder as his make, then good luck to the makefile in trying to find them.
Completely agree though - all the tools (make, compiler, linker) ought to be in PATH.