Hundreds of warnings when linking ShinobiEssentials 2.6.0


#1

Looks like in 2.6.0 the ShinobiEssentials build includes paths from someone at Shinobi named “jenkins” resulting in hundreds of warnings in the compiler. Here’s just a small sample:

warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/UIColor+ShinobiEssentials.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/SEssentialsPullToActionAlignBottomVisualizer.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/UIImage+ShinobiEssentials.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/SEssentialsTheme.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/SEssentialsView.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/ShinobiLog.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/Alignment.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/AlignmentBottom.o unable to open object file
warning: (armv7) /var/lib/jenkins/workspace/ShinobiEssentials/BuildOutput/checkout/Framework/build/ShinobiEssentials.build/Standard-iphoneos/ShinobiEssentials.build/Objects-normal/armv7/AlignmentCenter.o unable to open object file

#2

Hi wfilleman,

When building our static library we aim to leave in enough debug information (method names, symbol tables, type information, etc) to make your life easier when debugging your app. Unfortunately we went a bit too far with this and line number information has been left in.

Because of how the Mac ecosystem works, debugging information is stored in the object files but not the final binary. This is also what the .dSYM files are, that you may see lying around. So for the debugger to be able to debug an app, it needs access to the original object files or the dSYM directory which contains a file with the Dwarf debugging information. As we don’t distribute this for obvious reasons, we normally erase these paths to the object files. Since these paths haven’t been erased, when linking your app, the linker/debug linker is trying to find the object files to aggregate them into a dSYM folder for your app - but it can’t find them.

This warning is harmless and a minor release coming soon will remove these paths from the binary  :grin:

Thanks,
Jan


#3

Thanks Jan for that detailed write-up. Indeed it does appear that the framework runs just fine in my apps with these warnings. I’ll patiently wait for the patch release.

Wes


#4

Still the same issue with 2.6.1. When will this stuff be removed?

Regards,
Urs


#5

Hi guys,

The issue has now been fixed as of ShinobiEssentials 2.6.2!

For those of you with ShinobiCare, the new version should be available in the Portal, otherwise the new version is available from the trial download.


#6

Thanks Tom!

Wes