Steven Watanabe-4 wrote

AMDG

When I try to run the tests for Boost.Thread or Boost.Chrono I get an error like:

failed to write output file '..\bin.v2\libs\chrono\test\basic_stopwatch_reporter _laps_accumulator_set_pass_shared.test\msvc-10.0express\debug\asynch-exceptions- on\threading-multi\stopwatch\basic_stopwatch_reporter_laps_accumulator_set_pass. obj.rsp'!

Could the names possibly be made shorter? I can get it to build using --hash, but they're still rather long.

I will do it. Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/chrono-thread-Test-names-too-long-tp44816... Sent from the Boost - Dev mailing list archive at Nabble.com.

AMDG On 03/18/2012 11:33 AM, Vicente J. Botet Escriba wrote:

Le 18/03/12 11:32, Vicente Botet a écrit :

...

Steven Watanabe-4 wrote

...

When I try to run the tests for Boost.Thread or Boost.Chrono I get an error like:

failed to write output file '..\bin.v2\libs\chrono\test\basic_stopwatch_reporter _laps_accumulator_set_pass_shared.test\msvc-10.0express\debug\asynch-exceptions-

on\threading-multi\stopwatch\basic_stopwatch_reporter_laps_accumulator_set_pass.

obj.rsp'!

Could the names possibly be made shorter? I can get it to build using --hash, but they're still rather long.

I will do it. Vicente Hi, I have made the test case shorter( See Committed revision 77378). BTW, which is the limit?

I think we used to have a policy limiting file names to 31 characters. According to http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%2..., the limit for the total path length is 260 characters. In Christ, Steven Watanabe

On Mon, Mar 19, 2012 at 5:56 AM, Steven Watanabe <watanabesj@gmail.com>wrote:

AMDG

I think we used to have a policy limiting file names to 31 characters. According to

http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%2... , the limit for the total path length is 260 characters.

In Christ, Steven Watanabe

Perhaps this is a good reason to look into using the Unicode path style? The obvious pro is that it supports path up to around 32k characters, however the downside is that the majority of Windows software doesn't really deal well with paths this long, including programs built into Windows like Explorer (which is just ridiculous imo, but there's nothing we can do about that...). Obviously it would be better to keep the paths under the MAX_PATH limit regardless, just to keep the majority of users sane, however it would be nice if the Unicode path style was supported regardless, so users (who understand the consequences) can nest Boost arbitrarily deep into a directory structure and it still works (assuming the tools they are using also support the Unicode path format). On Mon, Mar 19, 2012 at 8:09 AM, Vicente J. Botet Escriba < vicente.botet@wanadoo.fr> wrote:

Ok. I will check that.

I run the test on Boost.Thread and Boosty.Chrono regularly and I didn't see never this error. On which environment this error occurs?

______________________________**_________________ Unsubscribe & other changes: http://lists.boost.org/** mailman/listinfo.cgi/boost<http://lists.boost.org/mailman/listinfo.cgi/boost>

It will occur on any Windows platform. I haven't run the tests on this machine lately, so I can't say whether or not it will happen in the 'best case scenario' (i.e. Boost is located at the root of a drive), however it is pretty much guaranteed to happen if you nest it even a few levels deep into a directory structure. The relative path posted by Steven above is 219 characters long, so you don't have much room to work with there...