Mail Archives: djgpp/2002/11/07/10:46:25
>Charles Wilkins <chas AT pcscs DOT com> wrote:
>
>> libstdc++ includes a form of the C standard library.
>
>> examples
>> ctype.h in the C standard library is cctype in libstdc++
>> stdio.h in the C standard library is cstdio in libstdc++
>> stdlib.h in the C standard library is cstdlib in libstdc++
>> etc...
>
>Those are not the library. They're just C++-ified versions of the
>*headers* for that library.
Yes, you are right. Headers are not libraries. I did not mean to
imply otherwise. Those are the newer C++ified versions of the
*headers* for for the standard C++ library... and additionally...
as every C++ programmer knows, the C++ standard library does in fact
include C with few exceptions.
If I wanted to program stricly C in DOS, there are many such
implementations that will do this, including Borland PowerPackforDOS,
Turbo C++, and Pacific C.
What is special about DJGPP to me is that it can build as a target for
gcc on a linux host. So of course my question refers to C++ and not
C.
This is why I asked this question in this fashion:
"Isn't the standard library (along with all of the non-deprecated
header and STL files for ANSI / ISO C++) supposed to build with the
crossgcc build?"
I guess now that I think about it, I could have been more clear and
asked it this way:
Isn't the ANSI / ISO C++ Standard Libray ( libstdc++ ) along with its
headers (non-deprecated or 'C++ified' headers and STL headers)
supposed to build with the linux hosts crossgcc.
I ask it this way because several years ago, there were C++
implementations that did not have STL support and used what is now
considered to be deprecated headers.
I just want to be clear that I will be able to build a cross gcc that
makes DOS executables with the same full C++ support that a natively
built GCC-3.2 can do.
I believe that the answer is yes, but I just wanted to hear somebody
say it so I could decide whether or not to keep trying to get this to
work. I am stubborn, so I will continue to assume that it will work,
so I will keep trying :)
>You might just cheat and install the libraries of the native DJGPP GCC
>build, of course.
I tried linking against them and it didn't work.
> Or at least have a very close look at the native
>DJGPP source distribution for GCC to see how that's being built.
Yes, this is what I am doing in between posting and e-mailing for
help. Any chance to get help is preferred so I do not waste time or
possibly fail where another may have succeeded. :)
Many thanks for your help and replies, Hans-Bernhard.
Once I work through this I will gladly post the final recipe.
Charles Wilkins
- Raw text -