Create a separate make command to build vin2dot #25
Labels
enhancement
New feature or request
good first issue
Good for newcomers
vinumc
Issues related with the vinumc compiler
Comments
artP2
added
enhancement
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
Merged
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
Grillo-0
added a commit
that referenced
this issue
Feb 11, 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: