RESOLVED INVALID 131952
WTF.xcodeproj no longer builds in Xcode since bmalloc target was added 
https://bugs.webkit.org/show_bug.cgi?id=131952
Summary WTF.xcodeproj no longer builds in Xcode since bmalloc target was added
Matt Langston
Reported 2014-04-21 14:36:04 PDT
The WTF.xcodeproj no longer builds in Xcode 5.1.1 since bmalloc target was added. This is the error from Xcode Issue Navigator: Libtool /Users/matt/Library/Developer/Xcode/DerivedData/JavaScriptCore-gvckxkaproycptdlzqvkmupxvzdm/Build/Products/Debug/libWTF.a normal x86_64 cd /Users/matt/Documents/Appcelerator/src/Apple/WebKit.github2/Source/WTF export MACOSX_DEPLOYMENT_TARGET=10.9 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -static -arch_only x86_64 -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -L/Users/matt/Library/Developer/Xcode/DerivedData/JavaScriptCore-gvckxkaproycptdlzqvkmupxvzdm/Build/Products/Debug -filelist /Users/matt/Library/Developer/Xcode/DerivedData/JavaScriptCore-gvckxkaproycptdlzqvkmupxvzdm/Build/Intermediates/WTF.build/Debug/WTF.build/Objects-normal/x86_64/WTF.LinkFileList -lbmalloc -o /Users/matt/Library/Developer/Xcode/DerivedData/JavaScriptCore-gvckxkaproycptdlzqvkmupxvzdm/Build/Products/Debug/libWTF.a error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't locate file for: -lbmalloc error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: file: -lbmalloc is not an object file (not allowed in a library) Warmest regards, Matt
Attachments
Add attachment proposed patch, testcase, etc.
Geoffrey Garen
Comment 1 2014-05-01 12:49:09 PDT
Did you remember to build bmalloc before building WTF? This is required -- just like you need to build WTF before building JavaScriptCore.
Alexey Proskuryakov
Comment 2 2014-09-04 09:41:16 PDT
No response in several months, closing. Please feel free to re-open if this still occurs to you.
Note You need to log in before you can comment on or make changes to this bug.