Please note that I typically work w/ the MS Visual Studio which is
installed on my PC. I shouldn't think that it would interfere w/ the
Borland Developer Studio.
Any help you can offer within a short time would be greatly appreciated.
> To date, I have been unable to compile. My major
> roadblock is when it chokes because it is "Unable to open include file
> 'assert'" This is specified in the source file as:
> #include <assert>
> which is correct. Also the configurations seem ok for both the Paths and
> Defines sections of C++: Compiler: $(BDS)\include
> Linker: $(BDS)\lib
IIRC, you need to have $(BDS)\include\dinkumware in the include paths
for the compiler.
--
-David Dean
CodeGear C++ QA Engineer
<http://blogs.codegear.com/ddean/>
Your fix works. But I am not sure why that wasn't 'included' w/ the install. Maybe not w/ the evaluation copy.
> Your fix works. But I am not sure why that wasn't 'included' w/ the
> install. Maybe not w/ the evaluation copy.
New projects should have it by default. Imported projects don't have
their include paths changed.
> I am trying to get a project written in Borland C++ Builder
> v6 to work on my Developer Studio 2006 evaluation copy (before I spring
> for the license). To date, I have been unable to compile. My major
> roadblock is when it chokes because it is "Unable to open include file
> 'assert'" This is specified in the source file as:
> #include <assert>
> which is correct.
Which is wrong! There is no Standard header <assert> in either C or
C++.
Either do it the C way:
#include <assert.h>
or the C++ way:
#include <cassert>