Closed efortuna closed 9 years ago
This comment was originally written by whe...@gmail.com
Which part doesn't run on Windows? I've only tested the vm parts, since I thought that was the only part with a Windows implementation. What should we prioritize? We have a solution planned, that does not involve backslashes.
Sorry that was probably the world's vaguest bug report. You can also build the SDK (create_sdk), which generates a version of frog that is runnable on Windows. So, I was using test.py to run browser tests in Windows, in which case I used --component=webdriver, but this runs line 470 in test_suite.dart (executable = '$dartDir/tools/testing/run_selenium.py';) for example, which uses Unix slashes.
I have tested the fix of eagerly changing all backslashes to slashes as soon as we get them from the Windows API, and it seems to be the best solution. There is no problem using slashes in inputs to the Win32 API - it converts them internally. I have also run tests with paths like 'c:/', '/', '/tmp/', etc., and they all work fine. We should eventually move it into the platform-specific implementation for Windows, and test that everything works.
The advantage of having a single path separator, '/', on all platforms and in URIs is really immense.
Added Started label.
I suspect a big chunk of this is due to a lot of paths in the dart code "containing/strings/like/this".