Issue543

Title Make fast-downward.py compatible to run on Windows
Priority feature Status resolved
Superseder Nosy List jendrik, malte, silvan
Assigned To silvan Keywords
Optional summary

Created on 2015-06-23.17:58:44 by silvan, last changed by silvan.

Messages
msg4294 (view) Author: silvan Date: 2015-06-30.17:26:34
Pushed.
msg4281 (view) Author: silvan Date: 2015-06-24.12:01:50
So far, the idea was to only circumvent the non-existing modules on Windows. The
script now runs on Windows, but porfolio functionality (and SIGXCPU) is not
supported.

https://bitbucket.org/SilvanS/fd-dev/branch/issue543

I think it would be great if our scripts in misc/test/ also worked, but some of
the steps there fail because Windows tries to run some of the indirectly called
scripts as a Windows application rather than as a python one. Maybe we can have
a look at these during the sprint.
msg4280 (view) Author: malte Date: 2015-06-23.19:49:29
I think this is not just a matter of easier testing; "fast-downward.py" is in
some sense "the planner". (I'm not sure our documentation is up to date with
this, but that's more of a documentation bug. ;-))

Silvan, I see you assigned this to yourself, but I'm happy to help on this
during the sprint. Just let me know.
msg4279 (view) Author: silvan Date: 2015-06-23.17:58:44
For easier testing on Windows (also for the buildbot), fast-downward.py should
be compatibe with Windows. One problem we know of is "import resource".
History
Date User Action Args
2015-06-30 17:26:35silvansetstatus: chatting -> resolved
messages: + msg4294
2015-06-24 12:01:50silvansetmessages: + msg4281
2015-06-23 19:49:29maltesetmessages: + msg4280
2015-06-23 17:58:44silvancreate