I tried the following, but it doesn't work.
It creates only one group and the display name isn't the value which is set
with DISPLAY_NAME:
CPACK_ADD_COMPONENT_GROUP(BaseGroup DISPLAY_NAME "Name Of Base Group")
CPACK_ADD_COMPONENT_GROUP(SubGroup DISPLAY_NAME "Name Of Sub Group"
PARENT_GROUP BaseGro
2011/3/8 NoRulez :
> Ok,
>
> I mean a parent group instead of sub component.
> But i doesn't find any documentations about this too.
look in CPack.cmake
or
cmake --help-module CPack
> If it isn't implemented in CPack, can i mix cpack and nsis scripts, and if so
> how?
CPack is using a NSIS tem
Ok,
I mean a parent group instead of sub component.
But i doesn't find any documentations about this too.
If it isn't implemented in CPack, can i mix cpack and nsis scripts, and if so
how?
Best Regards
Am 08.03.2011 um 21:36 schrieb Eric Noulard :
> 2011/3/8 NoRulez :
>> Hello everyone,
>>
2011/3/8 NoRulez :
> Hello everyone,
>
> is there a way to generate sub and sub sub components with CPack and Nsis?
Yes theoretically there is.
But I never tried.
> I would like to have the following structure, but I couldn’t figure out how
> to do this:
>
> Component
> |
> +---
> Hello everyone,
>
>
>
> is there a way to generate sub and sub sub components with CPack and Nsis?
>
> I would like to have the following structure, but I couldn’t figure out how
> to do this:
>
>
>
> Component
>
> |
>
> + Sub Component 1
>
> +-
Hello everyone,
is there a way to generate sub and sub sub components with CPack and Nsis?
I would like to have the following structure, but I couldnt figure out how
to do this:
Component
|
+ Sub Component 1
+ Sub Component 2
Brad,
Thanks for your input -- setting it as Catamount was the trick.
Is there a way to use a toolchain file with ccmake? It throws a warning saying
it doesn't use the CMAKE_TOOLCHAIN_FILE. If I do it with cmake, everything is
fine.
Thanks again,
Tim
- Original Message -
From: "Bra
I have a program called "tone12" which I was working on in KDevelop 3, then
copied to my DragonFly box which has KDev 4. Finding out that KDev4 no longer
has support for autotools, I created an empty project, copied the files, and
got it to compile. Then I added a big-endian test (I just added a
I have created an issue in the bug tracker:
http://public.kitware.com/Bug/view.php?id=11940
-Nico
2011/2/24 Nicolas Desprès :
> I have checked by calling cmake from the "real" builddir (not the
> symlink) and it works fine:
>
> $ pwd
> /home/despre_n/build/test/helloworld-cmake/_build
> $ cmake ~
Am 08.03.2011 17:11, schrieb Brad King:
Does it happen even if you don't pass -D... on ccmake's command line
when regenerating an existing build tree?
No, it runs perfectly on an existing tree.
Andreas
___
Powered by www.kitware.com
Visit other Kit
On 03/08/2011 11:05 AM, Andreas Kelle-Emden wrote:
> It happens every time when I generate the makefile structure with ccmake.
> I didn't set the *_DIR variable manually, neither does the CMakeLists.txt.
> The culprit might be the fact that I have to configure at least
> twice before I can generate
Is it in a public repo? Can we just try to repro the "complicated" case
here?
On Tue, Mar 8, 2011 at 11:01 AM, kent williams wrote:
> Thanks for getting back to me on this. After my initial post I tried
> to come up with some 'cut-down' examples, and the simple cases work.
> I'll keep trying to
Am 08.03.2011 14:22, schrieb Brad King:
If the _DIRs are already set then there is no search and the variable
is not used. Does this happen on the very first run in a new build tree?
You shouldn't need to pass it on the command line after the first time
because it will be stored persistently in
Thanks for getting back to me on this. After my initial post I tried
to come up with some 'cut-down' examples, and the simple cases work.
I'll keep trying to get a version that exhibits this failure.
This is kind of a worst case for debugging. I have a top level
CMakeLists.txt file that builds I
You need to postpone calling ctest_submit until *after* you call
ctest_start. Move that call down, and it should be good.
On Tue, Mar 8, 2011 at 8:59 AM, Zou, Di (Cont, ARL/CISD) wrote:
> Yes. I am calling ctest_start(Nightly). Here is my entire CTest script:
>
> SET(CTEST_SITE $ENV{HOSTNAME})
Yes. I am calling ctest_start(Nightly). Here is my entire CTest script:
SET(CTEST_SITE $ENV{HOSTNAME})
SET(MODE "Nightly")
SET(CTEST_SOURCE_DIRECTORY "$ENV{HOME}/$ENV{NIGHTLY_SOURCE}")
SET(CTEST_BINARY_DIRECTORY "$ENV{HOME}/$ENV{NIGHTLY_BUILD}")
SET(CTEST_INSTALL_DIRECTORY "$ENV{NIGHTLY_INSTALL}")
On 03/07/2011 09:54 PM, Tim Gallagher wrote:
> How can I get it to drop the -rdynamic option?
That option appears because the host system name is probably Linux on which
that option is supported. You need to set up a cross-compiling toolchain
file that sets the correct name of the target platform
On 03/08/2011 02:53 AM, Andreas Kelle-Emden wrote:
> I set the variable CMAKE_PREFIX_PATH on the command line
> so that CMake can find some Config files installed in a
> non-standard directory.
> The makefile generator prints the following warning:
>
> CMake Warning: The variable, 'CMAKE_PREFIX_PA
On 03/07/2011 03:59 PM, kent williams wrote:
> Looking at the difference between FindITK.cmake in 2.8.3 and 2.8.4 it
> looks like someone replaced trusting the ITK_DIR variable and using it
> directly if defined, with
>
> FIND_PACKAGE(ITK QUIET NO_MODULE
> NAMES ITK InsightToolkit CONFIGS ITKConfi
2011/3/8 Laszlo Papp :
> I could not still build cmake.. But I did this modification
> locally you suggested and that is the output:
>
> CPack: Create package using RPM
> CPack: Install projects
> CPack: - Run preinstall target for: Gluon
> CPack: - Install project: Gluon
> CPack: Create packag
Yes it works..
Thanks for the help.
I need to add this to my list of things to remember.
Now i still have the problem of the missing tlb file to fix, but i'll
handle that on my own.
-mika
mika.raj...@patria.fi
Sent by: cmake-boun...@cmake.org
08.03.2011 13:42
To
cmake@cmake.org
cc
Subj
Second try, replied to sender directly :)
Now that i checked the IDL_OUTPUT_DIR i found out that the second output
file is always missing, the .tlb one.
Maybe this is why it always runs that command?
Testing..
Richard Wackerbarth
Sent by: cmake-boun...@cmake.org
08.03.2011 13:18
To
mika
My cmake version is 2.8.4
"Rolf Eike Beer"
Sent by: cmake-boun...@cmake.org
08.03.2011 13:21
To
cmake@cmake.org
cc
Subject
Re: [CMake] Run/build custom command/target only when "input" files change
> foreach(in_file ${ARGN})
>
>
>
> ADD_CUSTOM_COMMAND(
> OUTPUT ${IDL_O
On Mar 8, 2011, at 5:10 AM, mika.raj...@patria.fi wrote:
>
> foreach(in_file ${ARGN})
>
>
>
> ADD_CUSTOM_COMMAND(
> OUTPUT ${IDL_OUTPUT_DIR}/${out_file}.h
> ${IDL_OUTPUT_DIR}/${out_file}.tlb
> DEPENDS ${in_file}
> COMMAND(${MIDL_EXECUTABLE} ${
> foreach(in_file ${ARGN})
>
>
>
> ADD_CUSTOM_COMMAND(
> OUTPUT ${IDL_OUTPUT_DIR}/${out_file}.h
> ${IDL_OUTPUT_DIR}/${out_file}.tlb
> DEPENDS ${in_file}
> COMMAND(${MIDL_EXECUTABLE} ${in_file}
> WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
> )
foreach(in_file ${ARGN})
ADD_CUSTOM_COMMAND(
OUTPUT ${IDL_OUTPUT_DIR}/${out_file}.h
${IDL_OUTPUT_DIR}/${out_file}.tlb
DEPENDS ${in_file}
COMMAND(${MIDL_EXECUTABLE} ${in_file}
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
)
endforeach()
> Hi
>
> I have created a custom command that generates source code for me.
>
> There is a slight annoyance still, the command is excecuted every single
> time i tell the compiler to build.
>
> Can I make it so that it runs the program only when the source file
> changes or the target file doesn't
Hi
I have created a custom command that generates source code for me.
There is a slight annoyance still, the command is excecuted every single
time i tell the compiler to build.
Can I make it so that it runs the program only when the source file
changes or the target file doesn't exist?
I loo
Hi list,
I set the variable CMAKE_PREFIX_PATH on the command line
so that CMake can find some Config files installed in a
non-standard directory.
The makefile generator prints the following warning:
CMake Warning: The variable, 'CMAKE_PREFIX_PATH', specified manually,
was not used during the ge
Was discussed on #meego-arm. Nokia and other "professionals" are
heavily working on this issue as far as it a qemu emulation issue, let
us see.
Best Regards,
Laszlo Papp
On Tue, Mar 8, 2011 at 2:25 AM, Laszlo Papp wrote:
> 1) What is the hackaround to install the newest version on arm ?
> 2) Wha
My familiar did a package as an interim solution and let us see
whether or not this version can be integrated into the 1.2 MeeGo
release or just later.
http://forum.meego.com/showthread.php?p=18810#post18810
Best Regards,
Laszlo Papp
On Tue, Mar 8, 2011 at 7:59 AM, Laszlo Papp wrote:
> I could
31 matches
Mail list logo
