[llvm-bugs] [Bug 36803] New: Mac OS X cmake scripts don’t test for necessary code-signing capacity before attempting to build

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=36803

            Bug ID: 36803
           Summary: Mac OS X cmake scripts don’t test for necessary
                    code-signing capacity before attempting to build
           Product: Build scripts
           Version: trunk
          Hardware: Macintosh
                OS: MacOS X
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: cmake
          Assignee: unassignedbugs at nondot.org
          Reporter: fish2000 at gmail.com
                CC: llvm-bugs at lists.llvm.org

If you are building LLVM using `cmake` on a Macintosh and you wish to include
any of the components that require code-signed binaries, you will need to have
already gone through the (perhaps infamous) manual process of creating a
self-signed code-signing certificate in your System Keychain:

    https://llvm.org/svn/llvm-project/lldb/trunk/docs/code-signing.txt

… if you haven’t already performed everything listed therein, or if this
procedure is somehow alien or off-putting to you, you may be stranded somewhat:
your `cmake` configure step will have successfully executed, but your build
phase will have choked out with a fatal error – likely with one whose
orthogonal nature to the problem will fail to lead to a solution.

A `cmake` function that tests for proper code-signing capacity (by building a
hello-world-ish program, and subsequently invoking `/usr/bin/codesign` on the
programs’ output binary) would surely be a valuable addition to this project,
no?

I, myself, had generated the certificate some time ago, and was happily
building LLVM with all available options – until today, when I was met with the
same sort of cryptically un-Googleable build-time errors. I eventually realized
that my certificate had past its “use-by” date, of two years’ past the
generation date, and had finally expired.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180319/f8fb2227/attachment.html>