Re:A Developer's Perspective On Porting Games To Linux
by derekp7 on Thursday May 08, 2014 @04:09PM
(#7717376)
One slide mentioned having to fix hardcoded backslashes to forward slashes, and using path.join to make it portable. But on Windows, you can use forward slashes as well at the system call level. You only need to use backslashes on the command line, since many programs interpret a forward slash as the beginning of an argument.
[ Parent
| on HN ]
Re:A Developer's Perspective On Porting Games To Linux
by blt on Thursday May 08, 2014 @04:57PM
(#7717657)
Yes, but that doesn't mean the original developers used them :)
Some developers are shockingly Microsoft-centric...
Re:A Developer's Perspective On Porting Games To Linux
by flohofwoe on Thursday May 08, 2014 @05:37PM
(#7717858)
Doesn't have to be on purpose, for instance Visual Studio inserts backslashes in autocompleted C/C++ header paths by default (can be set to forward slash in the settings, but default is backslash). The case-insensitive filesystems on Windows and OSX are usually also a problem when moving games with hundred-thousands of source- and asset files over to a Linux build system.
Re:A Developer's Perspective On Porting Games To Linux
by scrollaway on Saturday May 10, 2014 @12:11AM
(#7724459)
OSX/HFS has case insensitivity? Since when?
Re:A Developer's Perspective On Porting Games To Linux
by flohofwoe on Monday May 12, 2014 @03:49PM
(#7735018)
I was baffled too but that's like it is by default, on my MBP #include paths don't have to match case, just like on Windows. Or you can do a 'echo blub >bla.txt' followed by a 'echo blob BLA.txt' and there will only be a single file 'bla.txt' which contains the string 'blob'.