simfactory should create exe directory

Create issue
Issue #1645 closed
Roland Haas created an issue

Using virtual (--virtual) configuration one can wrap a Cactus config (or at least the parts that simfactory cares about) around an existing executable. Simfactory then copies the executable to exe/cactus_sim (or whatever), however it assumes that exe already exists. Since exe is not part of the Cactus checkout, simfactory needs to itself ensure that it exists.

Keyword:

Comments (5)

  1. Frank Löffler
    • removed comment

    First, I have never used virtual configs, nor do I understand what they are for. But when you say "around an existing executable", the "exe" directory would already have been created by Cactus' installation script, wouldn't it?

    But in any case I don't see harm in creating the directory if it is not there yet. Of course, someone might have set EXEDIR to something, and simfactory should probably honor it.

  2. Roland Haas reporter
    • removed comment

    I don't know what they were created for. In my case they are convenient for a tutorial to let the students use a pre-compiled executable with their own Cactus tree. Since they never compiled there is no exe directory. Ie what they do is (schematically):

    GetComponents http://einsteintoolkit.org/about/gallery/NsNsToHMNS/NsNsToHMNS.th
    cd Cactus
    simfactory/bin/sim setup
    simfactory/bin/sim build --virtual --virtual-executable ~rhaas/Cactus/exec/cactus_sim
    simfactory/bin/sim create-submit ...
    
  3. Log in to comment