[cfe-dev] Problem with building Clang and LLVM using Xcode

[Don Hinton via cfe-dev]

I don't normally use Xcode -- prefer command line -- but thought this was
interesting so I looked into it.

Not sure what the problem is with polly, but instead generating for xcode,
try creating an External Build System project instead and point it to your
ninja or make build.

You can follow these instructions, but note that I was unable to select
clang in step 3, so I selected opt, then hand edited the <project>.xschema
file to use clang instead.

  https://forums.developer.apple.com/thread/65025

hth...
don


On Sat, Nov 18, 2017 at 9:35 AM, Firouzeh Soleymani via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> Hi,
>
> I'm trying to build clang and llvm using Xcode.  I used the following
> command to generate the Xcode project:
>
> cmake -G Xcode -DDCMAKE_INSTALL_PREFIX="path to my llvm install
> directory" "path to my llvm directory"
>
> Then I opened LLVM.xcodeproj in Xcode, and chose "clang" as the only
> build scheme and hit the Build.  I ran into this error:
> clang: error: no such file or directory: 'path to my build
> directory/lib/Debug/libPolly.a'.
>
> /lib/Debug contains only one file - 'libPollyISL.a'.  I got the same
> error when I tried building from the command line:
> clang: error: no such file or directory: 'my build
> directory/lib/Debug/libPolly.a'
> The following build commands failed: Ld
> /Users/Firouzeh/dev/llvmbuild/Debug/bin/opt normal x86_64
>
> I'm trying Xcode build, because I want to debug clang in Xcode.  I'd
> appreciate any help!
>
> I'm using macOS 10.13.1, Xcode 9.1, Apple LLVM version 9.0.0
> (clang-900.0.38), and trunk revision 318585 of the source code.
>
> Thanks!
> Firouzeh Soleymani
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20171119/aab527f0/attachment.html>