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

After the divorce from vtest, marry it again as a submodule #2838

Closed
wants to merge 1 commit into from

Conversation

nigoroll
Copy link
Member

please note:

@nigoroll
Copy link
Member Author

travis: make[3]: *** No rule to make target `vtest/src/vtc_h2_dectbl.h', needed by `distdir'. Stop.
seems like we need to teach it how to work with submodules

@nigoroll nigoroll force-pushed the vtest_submodule branch 2 times, most recently from 4f4e993 to acf7994 Compare December 3, 2018 09:51
please note:

* for now, the submodule is https://github.com/nigoroll/VTest
  because of additional changes to vtest required
  (PR is vtest/VTest#3 )

* This will change the procedure to check out the sources:
  (not yet docmented)

	git clone --recursive

	or, if already cloned

	git submodule update --init

* To pull

	git pull --recurse-submodules
@bsdphk
Copy link
Contributor

bsdphk commented Dec 3, 2018

Thanks for doing this Nils.

I think my conclusion is that the time is not ripe for this yet.

How we integrate vtest ultimately depends on what the vtest project develops into.

Right now it is sort of a "source-code library" and the manual integration is not a big deal.

If vtest development picks up, that calculus will change and if so, we will make new decisions.

@nigoroll
Copy link
Member Author

VDD: revive this

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

Successfully merging this pull request may close these issues.

4 participants