Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local Artery automated setup #357

Open
AshFungor opened this issue Jan 4, 2025 · 2 comments
Open

Local Artery automated setup #357

AshFungor opened this issue Jan 4, 2025 · 2 comments

Comments

@AshFungor
Copy link
Contributor

Hey,

Myself and my fellow colleagues have had pleasure to work with this awesome tool for (I might be a bit mistaken, memory lets me down sometimes) a year now and, considering the fact that we are just working on our small island in this quite big project, it appeared to us that to some extent uniform script for handling Artery setup might be useful for complete newbies like us.

We are aware of VM setup, but running VMs (our opinion) makes sense only in foreign environments, like MacOS or Windows, where there is pretty much no other choice.

Manual setup (installing components, providing libs) is fine, but might be difficult to comprehend for someone new or just too much of work in case you need to perform quick tests with different component versions.

The idea is to create a script to handle all dependencies in isolated manner (all installation in a single directory) with agile version configurations, similar to how Docker operates, but locally to setup development environment and export those compile_commands that can be picked up by Clangd or any other IDEs with support for them.

We have some sort of this done already, which have taken a lot of effort to create, probably due to our skill level :)

Please, let me know if Artery could use such a script.

@riebl
Copy link
Owner

riebl commented Jan 4, 2025

Hi @AshFungor,

Your proposed setup script is a great idea! I am just worried about its maintenance burden. At least some form of automated testing would be needed for this script.
I think the addition of a DevContainer setup would be nice. Probably, such a bundled configuration would also ease the setup efforts in your environment. AFAIK, these DevContainers are no longer VSCode-only but are also supported by other tools nowadays. Your mentioned script could be one piece for creating a suitable DevContainer.

What do you think?

@AshFungor
Copy link
Contributor Author

Thank you for your feedback here! Sounds great, I will get to work on this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants