Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

WhatEver

Libs compiled with MSVC 6.0 are not compatable with MSVC 5.0 compiler?

This topic is 6115 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I can kinda understand why, but why? How can I make libs that are compatable with all MSVC compilers? Now that I know that libs compiled with VC 6.0 don't work with VC 5.0, then they definatly won't work with C++ Builder :/(not all that important really, but it would be nice if it was). Edited by - WhatEver on December 27, 2001 5:33:20 PM

Share this post


Link to post
Share on other sites
Advertisement
If you can kinda understand, then why ask? 8)

Static libs are generally not portable across compilers due to

1. specific compiler settings
2. external library references (e.g VC++ runtime lib)

What might work on one compiler might not even work on the same compiler - It requires the linking appl to use the same compilation flags as the static lib.

Unless your interface function stick strictly with C, then it is possible to portably distribute the library.


It is generally less hassle to let the other party use a build the static library in their environment.

..


Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!