Closed mrcroc closed 11 years ago
I cannot reproduce this in a fresh checkout. If you do a checkout to a directory without spaces and run the cross compile script, does the issue persist?
cd ~/Desktop
git clone git@github.com:p2/Redland-ObjC.git
cd Redland-Objc/Redland-source
python cross-compile.py
ld
is given the path where libxml was built, you can see that with all the -L
and -I
with /PATH_WITHOUT_SPACES/Redland-ObjC/Redland-source/product-iOS-armv7/lib
in the log.
Thx. I've been able to overcome this finally by uninstalling MacPorts port libxml2 and hence the file /opt/local/lib/libxml2.dylib as it was owned by this port. Presence of this file/library on my OS X 10.7.5 build host had evidently "somehow" interfered with the normal build process in cross-compile.py.
sudo port uninstall --follow-dependents libxml2
Ah that makes sense. There probably is a way to have the script prefer its own path before system paths so this issue doesn't come up again. Thanks!
This is a follow-up issue to #4.
The compilation now fails because it apparently tries to pick up e.g. libxml2.dylib from a wrong location. Here's the peraps relevant excerpt of cross-compile.py's output:
I am wondering: why is ld not instructed to pick up libxml2.dylib from where it was placed by the previous compile step and where that would be. At /opt/local/lib/libxml2.dylib is apparently an older version (perhaps part of OS X or installed by MacPorts) for the x86_64 (not armv7) architecture.
BTW, if I run _cd /PATH_WITHOUTSPACES; find . -name lib''.dylib* I get this (i.e. neither libxml2.dylib nor one of the other three libraries exists here for the armv7 architecture).