Thread: Using libraries from different compilers

>Would be as simple as adding the Borland library path in the list of
>GCC libraries and the include path to the list of includes?
No, but it would be a learning experience to try and see what happens.

I've tried this before. It's not such a good idea. The library will conflict with other libraries that they don't belong with and you'll be in a worse off position than when you started.

I would say, if there is a library that has a function you need, then just get the code for that function and add it to your program. Then if you're gonna give out the source code, give credit where credit is due.

I tried it and got this using some old code and the MSVC++ compiler.
The linker didn't like it.

Code:

nibbles.obj : error LNK2001: unresolved external symbol _gotoxy
nibbles.obj : error LNK2001: unresolved external symbol _wherex
nibbles.obj : error LNK2001: unresolved external symbol _clrscr
nibbles.obj : error LNK2001: unresolved external symbol _textbackground
nibbles.obj : error LNK2001: unresolved external symbol _textcolor
nibbles.obj : error LNK2001: unresolved external symbol __setcursortype

However I tried making a test app and it could do cprintf without a problem. Before building the above program I had some problems compiling too. Like, _NOCURSOR wasn't defined. Which is weird because it is in the include file. Maybe it didn't even include it. But if it didn't wouldn't it produce an error?

Edit: MSVC++ had it's own conio.h. I don't feel like messing around with it's stuff so I give up, will it work or not?

You're trying to move Borlands conio.h to your compiler, but I can tell you that most of those functions can be found in other libraries on your compiler.

Check windows.h.

>No, if anything I am trying to stick to only one compiler instead of
>having a million of them everywhere taking up a bunch of space.
Actually, it's a good idea to have at least three unique compilers if you're serious about programming. That way you can test on all three and be reasonably confident that your code doesn't rely on the quirks of any one compiler.