Symbolic Link. Its like an alias or shortcut on Windows but gets resolved by the operating system.
TheVinn wrote:1) How do I check a symlink into a Git repository?
You shouldn't need to check it into a Git repository. Just don't add it (using 'git add') to any branch of Juce you may have forked.
TheVinn wrote:2) How do I make a symlink on Windows?
Never actually done it on Windows but I think its a command line tool called mklink
. I have created one on the Mac and it resolves correctly through a Windows VM shared folder.
This is how I do it:
1) Have my own module repository with modules, apps etc. in it
2) Create a symlink to the module
3) Place the symlink in the JUCE 'modules' directory
4) Open the Introjucer, my module is there in the list along with all the JUCE ones and the config flags are correctly recognised
5) When I generate a project the header file gets included by JuceHeader.h & the cpp gets included in the "Juce Library Code" group.
Now this is not an ideal solution but it has been working nicely for me for months.
What we really need is for Jules to add some kind of additional module search path option in the Introjucer. I know he has bigger plans for 3rd party module integration and they will eventually be able to be updated remotely. I also know there are only so many hours in a day and there are other, probably more important things that need doing first as there are only a few of us providing modules at the moment. I'm just using this method for the time being and waiting patiently for the module master plan to be revealed to us followers.