Mail Archives: djgpp/1996/01/16/16:46:34
>> To get it working, add -liostream at the end of the command at your call to
>> gcc.
>
>I think it's best to use -lgpp, even if the program only uses iostream
>functions. The reason is that libgpp.a includes everything libiostream.a
>does, so you don't have to change your Makefile when you start using
>other classes. The above is especially true for new users of DJGPP which
>are already confused with the multitude of the different libraries.
>
>The only reason to have libiostream.a is that its terms of usage are less
>restricted by the GNU LGPL (in fact, libiostream isn't LGPL at all, its
>usage is virtually unrestricted).
Will V2 have libstdc++.a (renamed, presumably, to libstdcp.a)?
-- Aaron Ucko (ucko AT vax1 DOT rockhurst DOT edu; finger for PGP public key) | httyp!
"That's right," he said. "We're philosophers. We think, therefore we am."
-- Terry Pratchett, _Small Gods_ | Geek Code 3.1 [for explanation, finger
hayden AT mankato DOT msus DOT edu]: GCS/M/S/C d- s: a18 C++(+++)>++++ UL++>++++ P++
L++>+++++ E- W(-) N++(+) o+ K- w--- O M@ V-(--) PS++(+++) PE- Y(+) PGP(+) t(+)
!5 X-- R(-) tv-@ b++(+++) DI+ !D-- G++(+++) e->+++++(*) h!>+ r-(--)>+++ y?
- Raw text -