Generated XCode projects fail to link with apr dylibs in /usr/lib

• Key: LOGCXX-245
• Type: Bug
• Status: Resolved
• Resolution: Invalid
• Priority: Major
• Assignee: Curt Arnold
• Reporter: Curt Arnold
• Component/s: Build
• Affects Version/s: 0.10.0

Description

Mac OS/X comes with APR and APR-Util preinstalled in /usr/lib, however attempting to build the XCode project files that come with log4cxx 0.10.0 will fail to link with these libraries. The suggested work-around is to create symbolic links to the preinstalled libraries and then add the path to the symbolic links on the library search path which surprisingly does work.

From log4cxx docs:

  Xcode fails when linking to apr and aprutil dylibs in /usr/lib,
  however it will succeed linking to symbolic links to the same files.
  As a workaround until a resolution is found:
  
  Create symbolic links to the libraries in some arbitrary directory:
  
+-----+
mkdir ~/apr-dylib
cd ~/apr-dylib
ln -s /usr/lib/libapr-1.dylib libapr-1.dylib
ln -s /usr/lib/libaprutil-1.dylib libaprutil-1.dylib
+------+
   
   Then add the arbitary directory to the Library Search Paths
   (Build tab of the Get Info page for the project).
    
    
   The project file generation does does not
   properly create an entry in the "Link Binary with Libraries"
   build phase for projects that depend on log4cxx. To
   work around the problem, open the project in Xcode and
   in the Groups & Files pane, drag log4cxx.dylib
   and drop on the "Link Binary with Libraries" folder
   under Targets.

Comments

[Curt Arnold]

The issue is that MacOSX 10.4 did not ship with apr and apr-util and therefore do not have those libraries in $(DEVELOPER_SDK_DIR)/MacOSX10.4u.sdk. The better solution than suggested in RC2 is to change "Base SDK Path" to MacOSX10.5.sdk.

[Curt Arnold]

Intentional behavior of Xcode which inhibits linking with /usr/lib in preference to linking with SDK. Mac OS 10.4 SDK does not include APR and APR-Util, though 10.5 does.