ERROR MESSAGE:object files exceed 64k

Whaley

I am compiling a large application using the Spin tool, and I get the message "object files exceed 64k". I can't find any reference to this error message anywhere in the online help or on this forum.

The issue seems to be related to the size of the full tree of OBJ sections across my whole application. If I remove any entry from an OBJ section the error message goes away (but then of course I have missing functionality!)

Does anyone know what the real cause of this limit is, and whether there is any way to work around it? I haven't asked the parallax support team yet as I wanted to check with the forum first in case anyone else has come across this and knows how to solve it.

My generated application size·fills up about half the hubram·at the moment, so I don't think it is anything to do with generated application size.

As a test I removed a number of OBJ's from one of my objects and the error went away. I then added one back (for a small module with only a simple PUB function with a single return inside it) and I got the same error message again. It appears while compiling the whole application from the top object.

Thanks in advance

David.
·

Dave Hein

I had this problem with some code that I was working with.· The problem occurs in·a large project that·references objects from multiple objects, and those objects reference other objects.· It appears that·the Spin tool first links multiple copies of an object, and then it removes the extra copies to produce the final binary image.· The error occurs if the first step produces an image greater than 64K.

The easiest solution for me was to use BST instead of the Parallax Spin Tool.· BST doesn't have this problem.

Dave

Whaley

Ok, thanks, that does indeed explain the problem I am having, as I have quite a deeply nested tree of objects including objects, and quite a lot of references to the same object from other places - so the tree is quite wide and deep at the same time.

I will try out BST as you suggest.

Thanks very much for your speedy response.

David.