Going over to submodules #18
Closed
razterizer
announced in
Announcements
Replies: 1 comment
-
It was quite more complicated than I imagined. I reverted all of the submodule changes. I might re-introduce app-to-lib submodules but scrap lib-to-lib submodules. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As I'm new to git, I just found out a neat feature reminiscent of Plastic SCM's xlinks feature ; Git submodules. I discovered it when working on the
AudioLibSwitcher
project where I needed to put the interface from one repo available in the repo of the interface adapter.So, instead of me instructing you to place the different library checkouts in certain folders for everything to work (and to clone multiple repos to make it work), you will soon just have to clone the repo you are interested in and it will hopefully just work out of the box (except for those 3rdparty libs that I cannot include in my repo because of clashing between licenses. Those you have to take care of yourself. But that will hopefully also change as I'm working on moving on to MIT or MIT-compatible licenses for all 3rdparty-libs).
I have already created submodules in all of my repos so far. I just need a little time to re-route the include paths and then my repos (
Core
(leaf lib, so works already),Termin8or
,8Beat
andPilot_Episode
) should all be ready to fly.Beta Was this translation helpful? Give feedback.
All reactions