Hi,
[subject formulated for best keyword search impact]
forgive me for the possibly dumb question,
but since cpack of course includes executing the "make install" step
I'd like to know how to possibly detect this within CMake code.
My build is capable of launching an external script
to pop up a "
2010/12/16 Andreas Mohr :
> Hi,
>
> [subject formulated for best keyword search impact]
>
> forgive me for the possibly dumb question,
> but since cpack of course includes executing the "make install" step
> I'd like to know how to possibly detect this within CMake code.
> My build is capable of la
On 16 December 2010 08:34, Andreas Mohr wrote:
> I'd like to know how to possibly detect this within CMake code.
This works for me:
INSTALL( CODE "
IF( \${CMAKE_INSTALL_PREFIX} MATCHES .*/_CPack_Packages/.* )
ENDIF( \${CMAKE_INSTALL_PREFIX} MATCHES .*/_CPack_Packages/.* )
" )
However, you t
On Sun, Dec 19, 2010 at 3:50 PM, Mike McQuaid wrote:
> On 16 December 2010 08:34, Andreas Mohr wrote:
> > I'd like to know how to possibly detect this within CMake code.
>
> This works for me:
> INSTALL( CODE "
> IF( \${CMAKE_INSTALL_PREFIX} MATCHES .*/_CPack_Packages/.* )
>
> ENDIF( \${CMA
On 20 December 2010 12:34, David Cole wrote:
> On Sun, Dec 19, 2010 at 3:50 PM, Mike McQuaid wrote:
> When you find yourself in the "must escape too much" situation in an
> INSTALL(CODE scenario you should switch to writing out a script that you
> then include with an INSTALL(SCRIPT command.
On Mon, Dec 20, 2010 at 7:51 AM, Mike McQuaid wrote:
> On 20 December 2010 12:34, David Cole wrote:
> > On Sun, Dec 19, 2010 at 3:50 PM, Mike McQuaid
> wrote:
> > When you find yourself in the "must escape too much" situation in an
> > INSTALL(CODE scenario you should switch to writing out
On 20 December 2010 13:17, David Cole wrote:
> I don't think an INSTALL(... PACKAGE construct is necessary. And, in fact, I
> think it might be harmful. (For one thing, INSTALL(PACKAGE sounds like
> you're installing "a package", not like you're installing "something you've
> built but only as par
On 20 December 2010 16:07, Clinton Stimpson wrote:
> BundleUtilities already skips system libraries, so I don't see a difference
> between making a package and "make install" in this case.
> If you're using all system libraries, BundleUtilities can become a no-op.
You're basically saying "don't u
