Rename /src/player/util.c ?

[PaulBlay]

It's a small point, but some compilers dislike it when there are two files of the same name. The 'object' files have (for example) 'obj-util.c' so they're no problem, using a a similar approach you could change the util.c in /src/player/ to 'pla-util.c' or 'plyr-util.c'.

[takkaria]

Originally Posted by PaulBlay

It's a small point, but some compilers dislike it when there are two files of the same name. The 'object' files have (for example) 'obj-util.c' so they're no problem, using a a similar approach you could change the util.c in /src/player/ to 'pla-util.c' or 'plyr-util.c'.

Really? Are you sure that the make rules are putting the object files in the right place? I started using subdirectories to avoid ridiculous names...

[PaulBlay]

Originally Posted by takkaria

Really? Are you sure that the make rules are putting the object files in the right place? I started using subdirectories to avoid ridiculous names...

Yes. Talking about Open Watcom in particular here (although I'm pretty sure I saw it in another compiler before). Although it says "\player\util.c" in the list of files to add, when you try to add the \util.c file the error message

Conflicting file 'player\util.c' found in target 'Angband65.exe'

is displayed.

[takkaria]

Originally Posted by PaulBlay

Yes. Talking about Open Watcom in particular here (although I'm pretty sure I saw it in another compiler before). Although it says "\player\util.c" in the list of files to add, when you try to add the \util.c file the error message

Conflicting file 'player\util.c' found in target 'Angband65.exe'

is displayed.

*sigh* I'm not willing to change source code organisation to work around bad tools. Is there any chance you could file a bug report on it with the OpenWatcom people? I wasn't even aware Watcom existed anymore...

[PaulBlay]

Originally Posted by takkaria

Is there any chance you could file a bug report on it with the OpenWatcom people? I wasn't even aware Watcom existed anymore...

They are, but it looks like it's a bad choice anyway.

I've reported the bug to Open Watcom.

[EDIT] It looks like what the problem is is that it creates all .obj files in the base (/src) directory whether the source files were in a subdirectory or not. So it's a compiler error, I guess, not an IDE error as I thought.

[ekolis]

Since the same issue is occurring with MSVC++ 2008 as well, perhaps you might reconsider your position on this, Takkaria?

edit: oh, wait, I just found a nifty feature in VC++... you can override the name of the obj file generated for a specific c file! Perhaps there is such a feature in OpenWatcom?

[takkaria]

Originally Posted by ekolis

Since the same issue is occurring with MSVC++ 2008 as well, perhaps you might reconsider your position on this, Takkaria?

Maybe. I really don't understand how MSVC can be that bad, though. There must be other projects which have more than one file with the same name in different directories...

[Sergio]

There are two bugs in Connect for your issue with Visual C++. It's a bug, and while it works just fine in VS2005, it's broken in VS2008. Sadly, it won't be fixed any time soon (maybe VS10).

http://connect.microsoft.com/VisualS...dbackID=395521
http://connect.microsoft.com/VisualS...dbackID=368272

[zaimoni]

Originally Posted by ekolis

edit: oh, wait, I just found a nifty feature in VC++... you can override the name of the obj file generated for a specific c file! Perhaps there is such a feature in OpenWatcom?

Yes: have to use non-default makefile rules, but any vaguely aware make utility has this capability.

[takkaria]

Originally Posted by ekolis

Since the same issue is occurring with MSVC++ 2008 as well, perhaps you might reconsider your position on this, Takkaria?

edit: oh, wait, I just found a nifty feature in VC++... you can override the name of the obj file generated for a specific c file! Perhaps there is such a feature in OpenWatcom?

How do you do that? And how do you do it on the commandline?