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

gitignore config.h #34

Closed
artP2 opened this issue Jan 31, 2025 · 0 comments · Fixed by #36
Closed

gitignore config.h #34

artP2 opened this issue Jan 31, 2025 · 0 comments · Fixed by #36
Labels
meta Related with the organization of the project

Comments

@artP2
Copy link
Contributor

artP2 commented Jan 31, 2025

Since it's a file generated by autotools, I don't see a problem with git ignoring it.

Grillo-0 added a commit that referenced this issue Feb 5, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
@Grillo-0 Grillo-0 added the meta Related with the organization of the project label Feb 5, 2025
@artP2 artP2 linked a pull request Feb 5, 2025 that will close this issue
Grillo-0 added a commit that referenced this issue Feb 9, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
Grillo-0 added a commit that referenced this issue Feb 9, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
Grillo-0 added a commit that referenced this issue Feb 9, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
Grillo-0 added a commit that referenced this issue Feb 10, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
Grillo-0 added a commit that referenced this issue Feb 10, 2025
The project is growing, now we have two projects (vinumc and vunit) in
the future we're going to have more. To organize this, turn this repo
into a monorepo[1], were all vinum related projects reside.

The Autools build system is not up to the task (the SUBDIRS situation
is really painful when doing something like this).

So, change the build system to meson[2], using it's subproject
feature[3] makes the whole thing really manageable. Also, not having a
bunch of build scripts scattered around the project is a positive.

[1]: https://en.m.wikipedia.org/wiki/Monorepo 
[2]: https://mesonbuild.com/
[3]: https://mesonbuild.com/Subprojects.html

Fixes: #25
Fixes: #34
Fixes: #34
@artP2 artP2 closed this as completed in 0d6bfb2 Feb 11, 2025
@artP2 artP2 closed this as completed in #36 Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Related with the organization of the project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants