Why doesn't the C99 backend place the resulting C code in the same directory as the original spec?

[ivanperez-keera]

I find it a bit frustrating that I cannot compile a Copilot spec from wherever and I have to move the resulting files to where the original spec is. While I can modify the spec to specify a directory, I cannot modify the spec to mean "in the same directory where the spec is".

As a common user of sandboxes, my scenario is the following:

• Copilot is installed in ~/copilot, locally using sandboxes.
• Ogma is installed in ~/ogma, locally using sandboxes.
• I generate a cFS application.
• To compile the Copilot file that accompanies the generated application, I have to either install Copilot again, or create a sandbox in the cFS application directory pointing to ~/copilot/.cabal-sandbox, or do runhaskell from ~/copilot and move the resulting copilot{.c,.h,_types.h} to the cFS application directory.

I would have preferred to have the generated files be in the same directory as the spec, so that I could cd into ~/copilot and just runhaskell of the Copilot spec file, wherever it it.

[RyanGlScott]

I don't have a particularly strong opinion about what the default behavior should be, so I'm open to changing it.