Binder appears to write main cpp file before checking if output directory exists about binder HOT 6 CLOSED

The prefix directory is indeed should be present before run

The prefix directory is created during the run (at some point, at least. Perhaps it's not intentional?), but I think there's a race condition, or a mis-ordering so it's created after the attempt to write the module root. The issue is repeatable, at least for me.

from binder.

Ok, I moved into a plain folder on the local drive, and can confirm this problem exists without all the network/shared folder oddments.

Basically, if the path specified by --prefix doesn't exist, it is created, but {root-module}.cpp is never generated, and no error is thrown.

from binder.

@fake-name thank you for reporting this! The prefix directory is indeed should be present before run so such failure is expected, however we should indeed report an error in such cases. I will looks this up.

from binder.

I struggle with this as well until I realized the problem. It's interesting this issue has been hanging for a couple of years, seems easy enough to me to solve. So either:

1. Check if the prefix folder exists and bail out if not; or
2. At start, create the prefix folder if it does not exist, recursively
   Of course, now that I spent hours on this, I know and I've put a mkdir -p <prefix> on my script, for sanity.
   But it should indeed be solved within binder, for the mental sake of new users.

from binder.

Submitted this PR to solve this issue - not sure how to link the PR to the issue though
#124

from binder.

I updated master so prefix is now treated only as directory: a1870cb. I also added some error checks. So this should be fixed now.

from binder.