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

Guide to showcase the quickest way to create a package based on a C program #171

Open
greenbreakfast opened this issue Oct 24, 2024 · 12 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@greenbreakfast
Copy link
Contributor

Motivation

Why are we doing this? What use cases does it support? What problems does it solve? What is the expected outcome?

C programs are
This helps streamline the development process on the Omega2

Is your documentation request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Onion recommends wrapping all custom code/applications into packages.
But there isn't a single source that can be followed from start to finish that explains how to create a package based on a C program

Describe the solution you'd like

A clear and concise description of what you want to happen.

A example-based, step by step guide that's easy to follow that shows me how to create a package based on a C program. It should mention the environment setup but ideally this should be very easy and quick.

I want to know:

  • how to compile the package
  • transfer the package to Omega
  • Install the apckage
  • Run the installed application

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

It would be ideal to have everything in one place, focusing on an example. Once I complete the example, I should be able to adapt it to my own application

@greenbreakfast
Copy link
Contributor Author

Note for implementation: A new "Guides" section to the documentation will be added.
To publish the guide, please work in the content/guides branch on the guides/packages/c-package-example.md file

@remingtontr
Copy link
Contributor

remingtontr commented Oct 31, 2024 via email

@remingtontr remingtontr moved this from Ready for Development to In Progress in Omega2 Beta Documentation Improvement Oct 31, 2024
@remingtontr remingtontr moved this from In Progress to In Review in Omega2 Beta Documentation Improvement Nov 1, 2024
@remingtontr
Copy link
Contributor

Ready for initial review.

@remingtontr
Copy link
Contributor

remingtontr commented Nov 4, 2024 via email

@greenbreakfast
Copy link
Contributor Author

@remingtontr thanks! added another round of comments and suggestions

@remingtontr
Copy link
Contributor

remingtontr commented Nov 5, 2024 via email

@remingtontr
Copy link
Contributor

remingtontr commented Nov 6, 2024 via email

@greenbreakfast
Copy link
Contributor Author

@remingtontr Please go ahead with a PR. Let me know if you need any guidance on the windows steps for transferring the file.

@remingtontr
Copy link
Contributor

Okay, so I added 171 directly to the contents/guides branch.

@remingtontr remingtontr moved this from In Review to Approved for Production in Omega2 Beta Documentation Improvement Nov 11, 2024
@remingtontr remingtontr moved this from Approved for Production to In Review in Omega2 Beta Documentation Improvement Nov 11, 2024
@remingtontr
Copy link
Contributor

I got ahead of myself and committed changes for this on the content/guides branch directly rather than creating an Issue. My commit is under the #177 issue. Please let me know if you want me to back this out and create a separate PR.

@greenbreakfast
Copy link
Contributor Author

@remingtontr yep, committing to the content/guides branch is ok. I made PR #177 so we can see it rendered.
I will take a closer look later this week and get back to you

@remingtontr
Copy link
Contributor

remingtontr commented Nov 12, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: In Review
Development

No branches or pull requests

2 participants