Hi Folks,
As far as I remember, there is an issue with the "install(CODE | SCRIPT
..." that prevent it from being executed last. As a workaround, something
like this could be done:
https://github.com/Slicer/Slicer/blob/32979bf79bc2db503bbbe4b29082d5dd97411ebb/CMake/SlicerCPack.cmake#L61-66
See ht
On Tue, Apr 23, 2013 at 7:26 AM, Clinton Stimpson wrote:
>
> As a cmake module, it could be used at packaging
> time by having a install(CODE ...) in the CMakeLists.txt file.
>
Where would you call the install(CODE ...)? I wrote a shell script to do
the signing first, and I tried to use install(C
On Monday, April 22, 2013 08:22:50 AM Brian Milco wrote:
> > Does this workflow in your MacAppStore generator include anything that
> > prevents making a .pkg for OS X Installer?
> > From the stackoverlfow link below, the person says App Store submissions
> > follow different rules. Do you know wh
>
> Does this workflow in your MacAppStore generator include anything that
> prevents making a .pkg for OS X Installer?
> From the stackoverlfow link below, the person says App Store submissions
> follow different rules. Do you know what those differences are?
>
As I've never created an OS X Inst
Bringing this thread back to the cmake list...
- Original Message -
> Hi Clint,
> On Fri, Apr 12, 2013 at 9:28 AM, Clinton Stimpson < clin...@elemtech.com >
> wrote:
> > Ok, I now see what is special about it.
>
> > It uses "productbuild" to generates a .pkg (which is then put inside a
Hi Eric,
On Fri, Apr 12, 2013 at 12:58 AM, Eric Noulard wrote:
>
> Some ##end documentation markup where missing one '#' which makes the
> corresponding CPACK_APPLE_xxx var
> not appearing in the command line doc.
> The doc parser is almost dumm so that it's almost impossible to detect
> that safe
2013/4/12 Brian Milco
> Hi,
>
> I've added a CPack package generator for the Mac App Store for your
> consideration. You can find it on github:
> https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
>
> This is a first draft, but it should work to get a basic application
> uploade
Thu, Apr 11, 2013 at 4:01 PM, Clinton Stimpson wrote:
> Why do you have this CPack generator creating the .app instead of letting
> the
> CMake build step create the .app from the add_executable( ...
> MACOSX_BUNDLE ..
> )?
>
Because I was so happy to have it working I forgot to refactor the cod
On Thursday, April 11, 2013 03:30:39 PM Brian Milco wrote:
> Hi,
>
> I've added a CPack package generator for the Mac App Store for your
> consideration. You can find it on github:
> https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
>
> This is a first draft, but it should work
Hi,
I've added a CPack package generator for the Mac App Store for your
consideration. You can find it on github:
https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
This is a first draft, but it should work to get a basic application
uploaded via Apple's "Application Loader". I
10 matches
Mail list logo
