This is not a bug, but it bugs me! In my M51 map file, some files are shown on the included command line as residing in ".\filename.obj" and others as just "filename.obj", even though they are all in the same place and uV2 shows them as being in the same place. The linker seems to be just echoing what the uV2 project builder is telling it, but what does it mean? Also, I type in all my .c and .h filenames in lower case, but uV2 will sometimes show the name.ext in all caps, just the extensions in caps, or just the name in all caps. I wonder why. I am using Windows NT 4.0, svc pak 6a, and am using networked file shares. Thanks in advance for any clues. George
You ask, "uV2 will sometimes show the name.ext in all caps, just the extensions in caps, or just the name in all caps. I wonder why?" You say, "I am using Windows NT 4.0..." You should be used to it then! It's a feature of the PC/MS-DOS/Windows; Microsoft operating systems are not case sensitive, but may preserve case when storing/displaying filenames. Haven't you noticed how NT sometimes insists on using lowercase with a capital initial, irrespective of how you try to force it otherwise?!
Andy, Point taken. Especially where long filenames and network shares are involved. But changing "filename.ext" to "FILENAME.ext" or "filename.EXT" seems over the top, even for Windows/DOS. Fortunately, I have never seen it cause any harm. How about the ".\" question? Further poking around revealed that some source files in the ProjectName.Uv2 file are listed by their full path name and some by just ".\filename.c". These are the ones whose object files are listed differently in the linker M51. I must be adding project files differently for this to happen, but as far as I know I add them all the same. And anyway, don't all the objects go to the same place? Any ideas? Thanks, George
"anyway, don't all the objects go to the same place?" I s'pose you could use the OBJECT command-line directive to put each object into a different folder, if you really wanted...