User forums > Nightly builds

The 19 January 2007 build is out.

<< < (3/6) > >>

cbexaminr:
thought regarding spaces - could the problem have always been there, but the switch to full paths that include them has caused it to be revealed...

whereas the previous relative paths perhaps contained no (path/directory) segments that had spaces in them (such as "Program Files", or "C Development")?

Should all absolute paths (at least with spaces) be quoted in the command lines?

basurapr:

--- Quote from: cbexaminr on January 20, 2007, 12:03:26 pm ---Should all absolute paths (at least with spaces) be quoted in the command lines?

--- End quote ---

Yes, I think that the arguments should be sended quoted to the compiler. When the argument have spaces like this: C:\Program Files, it will pass like two arguments, "C:\Program" and "Files" to the char** argv array. It should be "C:\Program Files" to stop the problem. Maybe I'm wrong!  :?

julienlecomte:

FYI:
There's some SDK mismatch problem with the ClearCase plugin with this build. To avoid error message at startup, I just deleted the clearcase zip and dll.

killerbot:

--- Quote from: julienlecomte on January 20, 2007, 05:56:14 pm ---
FYI:
There's some SDK mismatch problem with the ClearCase plugin with this build. To avoid error message at startup, I just deleted the clearcase zip and dll.


--- End quote ---

yes, destroy it, this is a personal plug-in that sneaked into the nightly zip, my mistake. Off course I you use clearcase I can always provide you with a newer one ;-)

branleb:
I  have openSuSE 10.2 and i installed C::B rpm for suse10.0/10.1 (nigthly)
The splash screen appearing at the start always shows BUILD# "SVN 0", could anyone confirm ?
and is so, could you fix it ?
it is not so important, but it doesn't look so good with version number "0" ;-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page