| RE: [cdt-dev] MBS Slash issues |
|
Agreed. It feels wrong to use ‘/’
on Windows. And really, the problem I ran into is a bug with the particular
version of gdb I’m using. But having said that, I can see a point in time
where cygwin will stop supporting the ‘\’ as they feel it less necessary
to support Windows paths, so such an option may become necessary. I’ll take a stab at the gdb version
I have and see if I can solve it there first. If that takes too long, I’ll
look at a better workaround than just changing separators for everything. Thanks for your wisdom, Leo J.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Treggiari, Leo I know we have considered the
“slash” problem in the past, but I don’t remember all of the
details. There are probably one or more cdt-dev threads or bugzillas
discussions. One thing that comes to mind is that MBS allows the tool
integrator to use any command line tool, and the custom build steps allow the
user to use additional command line tools as well. Therefore, I
don’t think it is sufficient to check cl and link and then decide it is
OK. Maybe we need a toolchain or tool attribute that specifies the
tool’s filename requirements – with the default being OS format. Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Hey gang, I’ve recently run across a problem with gdb and dwarf
in MinGW’s lastest compiler and debugger distribution. If we build using
the toOSString to generate the file names, gdb gets confused by the
‘\’ file separator. If I use ‘/’ it’s fine. Now this is obviously a bug with gdb dealing with Windows
path names, but to make life easier for the gnu tools, we could change the
separator to ‘/’ in the command generator for all platforms. The question is, does anyone have a tool that needs Windows
file separators for file names. I checked Microsoft’s cl and link and
they seems fine with ‘/’. Obviously gcc, is fine with it.
|