Linker Error

does anyone know a work around for the internal linker size limit? I am currently getting this...

LINK : fatal error LNK1210: exceeded internal ILK size limit; relink with /INCREMENTAL:NO

RavikumarvAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

andrewjbCommented:
Try a full rebuild, after deleting all your .obj and .tlb files..

Don't know what version you're using, but builder 6 is very flakey once you start writing anything-but-tiny projects...
0
RavikumarvAuthor Commented:
I am using VC 6.0 with visual studio service pack. Even if i rebulid all after deleting all .obj and .tlb i am getting the same message.
0
andrewjbCommented:
.. then you ought post this in the general C++ area, or under a VC topic. This is the Borland C++ Builder TA..

Ask in CS to close this and re-ask, or get it moved :-)
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

CayceCommented:
Edit the project options and look for the incremental linker option. disable the option. That's it.

Good Luck
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RavikumarvAuthor Commented:
By de-selecting that option it works but I need to, I want to why was this problem not comming earlier to the service pack installation.

Ravi.
0
CayceCommented:
Well, that's a question I certainly cannot help you with. Perhaps because it's not a very common error or it doesn't affect a lot of customers. Maybe it doesn't behave like that on VS2003, you could try upgrading, too.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.