Improve v compiler integration in project #75

Closed
opened 2022-02-17 22:39:56 +01:00 by Jef Roosens · 2 comments
Owner

The current method of pulling the release tarballs doesn't really work out that well when we have to edit vlib n stuff. It would be better to either clone a release tag, or add the v repository as a submodule (maybe just the master branch tbh). That way, we can more easily test stuff if need be.

Current idea:

  • Manage our own fork of the V repo that incorporates our tiny changes
  • Add this fork as a submodule to our repo
  • Build the compiler for each CI build (I hope this doesn't slow things down too much)
  • Regularly update the fork with the latest changes
The current method of pulling the release tarballs doesn't really work out that well when we have to edit vlib n stuff. It would be better to either clone a release tag, or add the v repository as a submodule (maybe just the master branch tbh). That way, we can more easily test stuff if need be. Current idea: * Manage our own fork of the V repo that incorporates our tiny changes * Add this fork as a submodule to our repo * Build the compiler for each CI build (I hope this doesn't slow things down too much) * Regularly update the fork with the latest changes
Jef Roosens added this to the 0.2.0 milestone 2022-02-17 22:39:56 +01:00
Jef Roosens added the
enhancement
label 2022-02-17 22:39:56 +01:00
Author
Owner

Even better would be to switch to maintaining our own fork of the V compiler again, as keeping patches using version control is a lot more practical.

Even better would be to switch to maintaining our own fork of the V compiler again, as keeping patches using version control is a lot more practical.
Author
Owner

The issue with maintaining a fork however is having to constantly update the fork ourselves, which is rather time-consuming. We might have to think about how we can improve upon this workflow.

The issue with maintaining a fork however is having to constantly update the fork ourselves, which is rather time-consuming. We might have to think about how we can improve upon this workflow.
This repository is archived. You cannot comment on issues.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#75
No description provided.