Allow different directory to run target from about neovim-cmake HOT 8 CLOSED

Sounds reasonable. I will begin working on it.

from neovim-cmake.

When locally using the code for development, I copy a basic configuration file to the CMAKE_BUILD_DIR instead of copying it to each directory in which a target exists. This then results in the run command not working, since it can't load the configuration file.

Have you considered setting CMAKE_RUNTIME_OUTPUT_DIRECTORY to CMAKE_BUILD_DIR? Since you copying configuration files there.

I would not mind adding an option to specify the startup folder, but at the moment the options are not set on a per-project. So you have to change your running path each time you change the project.

from neovim-cmake.

I have not thought about that, but I would prefer to keep my testsuite executables separate from the main executable. I understand the issue with having to do a different setup per-project. Would it be possible to do something like have a global configuration, about allow a local file maybe something like .neovim-cmake.cfg override the default settings? This way one could have project specific commands if desired, but wouldn't mess with the global setup.

from neovim-cmake.

Hm... Okay! We currently have neovim.json file that contains run arguments and selected project.
Perhaps we could expand it to store more settings. As startup directory or cmake options. But this will require some work :)
I can do this later when I have a little free time.
But if you want to contribute - please, let me know, we could discuss implementation details.

from neovim-cmake.

I wouldn't mind contributing to the project. I would be happy to discuss implementation details.

from neovim-cmake.

Okay!

For now we have set of options here:

But some of them could be platform-specific. So I would wrap all settings in neovim.json (including current settings such as selected project or parameters) in a top-level dictionary that contains os name. You could get os name from this variable:

And every time you trying to get setting - just read it from JSON, here is the function to get it content:

And set:

If requested setting doesn't exists - use according global setting. I would wrap this into a convenient class (table) and move into a separate file.

Also we should add the option that your requested. I think that it should be local-only. You should check for it here:

And here:

Your thoughts? Suggestions?

from neovim-cmake.

I think the first part makes sense. I would suggest modifying the get_parameters function and the set_parameters function. To first check to see if there is a neovim.json file in the project root directory. If there is, then it should load the parameters from there. If any required settings are missing, then it should load it from the global neovim.json or from the default values.

We would then just have to modify:

To see if the user has the option set for a different run directory in the neovim.json file. If they have it set, then use that, otherwise use the current setup. I think that would be cleaner than doing it in both:

Does that seem like a reasonable approach?

from neovim-cmake.

I agree! Just one thing:

If any required settings are missing, then it should load it from the global neovim.json or from the default values.

I would avoid using a global neovim.json. I think that having a project-specific neovim.json and default values is enough.

from neovim-cmake.