Source code broken after pull on OS X
Soderqvist, Henrik
henrik.soderqvist at capgemini.com
Wed Oct 14 20:19:36 UTC 2015
Hi!
Iâve been facing an issue for the last 5-6 months where some symlink files are broken after checking out code from the repo. The symlinks appear as plain text files containing a path to the file that used to be linked by the symlink.
This happens for CocoaPods included in an iOS project. All header files have a symlink in a folder for each CocoaPod like this âPods/Headers/Public/<podname>â. For example for the CocoaPod âGoogleTagManagerâ there is a header file called TAGContainer.h which is symlinked like this "TAGContainer.h -> ../../../GoogleTagManager/Headers/Public/TAGContainer.hâ, but after checking out the source code the symlink looks according to below:
MyMac:GoogleTagManager macuser$ more TAGContainer.h
../../../GoogleTagManager/Headers/Public/TAGContainer.h
And hence build will fail since the header file is no longer found in the search path. The search path includes "Pods/Headersâ and all directories below that recursively.
Is there any setting that I can use on Mercurial to force it to treat symbolic links differently? Iâve been googling for quite some time to find a solution and even considered migrating the repo to git.
Iâm running:
Mercurial Distributed SCM (version 3.5.2+20151001)
Mac OS X 10.11 El Capitan (same issue on OS X 10.10)
CocoaPods 0.39.0
Regards,
Henrik
________________________________
Capgemini is a trading name used by the Capgemini Group of companies which includes Capgemini Sverige AB, a company registered in Sweden (number 556092-3053) whose registered office is at Gustavslundsvägen 131 Box 825 â S-161 24 Bromma.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
More information about the Mercurial
mailing list