[ofiwg] symlinks in git repos

Jeff Squyres (jsquyres) jsquyres at cisco.com
Sat Nov 24 19:18:55 PST 2018


My $0.02: git submodules are great in theory, but usually turn out to be somewhat complicated in execution.

Jason's example is probably the best one so far (i.e., foo.c is #include "../../...../foo.c")


> On Nov 22, 2018, at 11:57 AM, RIHANI, HAMZA <hamza.rihani at atos.net> wrote:
> 
>> Subject: Re: [ofiwg] symlinks in git repos
>> 
>> On Wed, Nov 21, 2018 at 06:59:27PM +0000, Hefty, Sean wrote:
>>> With the merger of fabtests into libfabric, we're looking at code being shared
>> between the two.  One way of handling this is to use symlinks in fabtests to
>> reference files stored in the libfabric portion of the tree.
>>> 
>>> This works wonderful... on Linux.  On Windows, not so much.  :/ Has
>>> anyone had any experience using symlinks or sharing files between
>>> different directories in git that works when building on Windows?
>>> 
>>> So far, our best option appears to be maintaining actual copies of
>>> the files/code, and relying on some sort of script to ensure that
>>> they are kept in sync.
>> 
> 
> Hello,
> 
> You could use the -I option of the compiler and set the include path to where the
> header files are.
> Maybe also add an option in configure script (for instance "--libfabric-src") to control the
> path in case the header files are not in the default location.
> 
> Hamza
> 
>> _______________________________________________
>> ofiwg mailing list
>> ofiwg at lists.openfabrics.org
>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.op
>> enfabrics.org%2Fmailman%2Flistinfo%2Fofiwg&data=01%7C01%7Chamza.ri
>> hani%40atos.net%7C3c258d324a0a4e21af5108d6509a4aa7%7C33440fc6b7c7412cb
>> b730e70b0198d5a%7C0&sdata=Uj%2FzckEnyHZgqEIKYs7pCl3uTeg%2BWllpm
>> sJSABwAWsc%3D&reserved=0
> _______________________________________________
> ofiwg mailing list
> ofiwg at lists.openfabrics.org
> https://lists.openfabrics.org/mailman/listinfo/ofiwg


-- 
Jeff Squyres
jsquyres at cisco.com



More information about the ofiwg mailing list