On Monday, September 29, 2014 01:23:04 PM Chuck Atkins wrote:
> > Maybe it shouldn't even be a CPack thing. Maybe it should be an
> > install time step so that all CPack generators will contains signed
> > binaries if codesign is used...
>
> I know this is a bit after the fact and I'm jumping
>
> Maybe it shouldn't even be a CPack thing. Maybe it should be an
> install time step so that all CPack generators will contains signed
> binaries if codesign is used...
>
I know this is a bit after the fact and I'm jumping in here pretty late,
but...
It would be nice to have package signin
Maybe it shouldn't even be a CPack thing. Maybe it should be an
install time step so that all CPack generators will contains signed
binaries if codesign is used...
D
On Mon, Sep 29, 2014 at 9:55 AM, wrote:
>
>
>
>>
>> It should not be an error for 'codesign
- Original Message -
> > It should not be an error for 'codesign' to not be available
>
> > in the PATH. The user may have set CPACK_COMMAND_CODESIGN
>
> > to some other location. The error should only occur if no
>
> > value for CPACK_COMMAND_CODESIGN is available when the tool
>
> >
On 23-Sep-14 19:42, Florent Castelli wrote:
On 23 Sep 2014, at 16:56, Bill Hoffman wrote:
That said it would be really cool to beef up the xcode support enough to
be able to create an actual ios app. I have not dug into that enough.
Should be able to do most of it with CMAKE_XCODE_ATTRIBUTE.
>
> It should not be an error for 'codesign' to not be available
> in the PATH. The user may have set CPACK_COMMAND_CODESIGN
> to some other location. The error should only occur if no
> value for CPACK_COMMAND_CODESIGN is available when the tool
> is actually needed for signing.
>
I attached an
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15176
==
Reported By:David Coppa
Assigned To:
