Compilation with 2 byte chars in file path
-
I am trying to compile some cpp files which have 2 byte chars (something like C:\日本\myfile.cpp) in its path but I am unable to compile it with VS 2005. Is there any way to compile it ? You must be thinking why I need 2 byte chars in folder name ? Actually there is some crash in application at launch time if folder have 2 byte chars, I want to debug the same. Please help if some one know the way to debug it with VS 2005.
Manish Agarwal manish.k.agarwal @ gmail DOT com
-
I am trying to compile some cpp files which have 2 byte chars (something like C:\日本\myfile.cpp) in its path but I am unable to compile it with VS 2005. Is there any way to compile it ? You must be thinking why I need 2 byte chars in folder name ? Actually there is some crash in application at launch time if folder have 2 byte chars, I want to debug the same. Please help if some one know the way to debug it with VS 2005.
Manish Agarwal manish.k.agarwal @ gmail DOT com
What is the exact error you are getting? I just tried the same and go the following
BSCMAKE: error BK1506 : cannot open file '.\Debug\????.sbr': No such file or directory -
I am trying to compile some cpp files which have 2 byte chars (something like C:\日本\myfile.cpp) in its path but I am unable to compile it with VS 2005. Is there any way to compile it ? You must be thinking why I need 2 byte chars in folder name ? Actually there is some crash in application at launch time if folder have 2 byte chars, I want to debug the same. Please help if some one know the way to debug it with VS 2005.
Manish Agarwal manish.k.agarwal @ gmail DOT com
It sounds like the compiler is still using byte-oriented character sets in this area. It might work if you were trying to compile with a Japanese version of Windows. You could try compiling in the normal location, then adding a post-build step to copy the final executable (and its .pdb file) to the location that is causing the problem. Then, in Project Properties, Configuration Properties, Debugging, set the 'Command' to be the path you need the program to run from. Or, simply set the Output Directory (in Configuration Properties, General) to be the path that has the problem, although the linker might struggle with this.
Stability. What an interesting concept. -- Chris Maunder
-
It sounds like the compiler is still using byte-oriented character sets in this area. It might work if you were trying to compile with a Japanese version of Windows. You could try compiling in the normal location, then adding a post-build step to copy the final executable (and its .pdb file) to the location that is causing the problem. Then, in Project Properties, Configuration Properties, Debugging, set the 'Command' to be the path you need the program to run from. Or, simply set the Output Directory (in Configuration Properties, General) to be the path that has the problem, although the linker might struggle with this.
Stability. What an interesting concept. -- Chris Maunder
I have found that exculding the creation of a sbr file for that single file works, but it hampers debugging. I also tried replacing the BSCMAKE.exe with that from VC6, but it complained too much. It looks like the filename is saved as a utf8 encoded string within the .sbr which is correct.
-
What is the exact error you are getting? I just tried the same and go the following
BSCMAKE: error BK1506 : cannot open file '.\Debug\????.sbr': No such file or directoryThat's VC6 output, isn't it?
-- This episode performed entirely by sock puppets