I've asked the same question some time ago (
http://www.mail-archive.com/cmake@cmake.org/msg14883.html).
We had a problem with big number of threads: the 32-bit address space can
fit only ~200 threads with such huge stacks. So if you are writing
multithreaded application, it is best to remove this
Just use "build project" command on it (through right click, for example).
On 3/3/09, Anders Backman wrote:
> Hi all.
>
> A slightly off-topic, but perhaps not question ;-)
>
> Is there a way to build the INSTALL project from the command line?
>
> Im trying the following:
>
> devenv /useenv vrlib
On Fri, Jan 30, 2009 at 5:11 PM, BlinkEye wrote:
> On Fri, January 30, 2009 14:37, Eric Noulard wrote:
> > As far as I know CPack only handles a single per-project package,
> > i.e. you may easilly build a package (deb, rpm, tgz etc...) for the WHOLE
> > project, even if the project does have sub
This problem may occur with gcc because of static library linking policy. If
you have a symbol in static library which is not referenced from main
executable it will not be linked in. (For example, if you use static classes
to register something to factories). To solve this issue, you should either
Actually, make install calls cmake in command mode to process
cmake_install.cmake file in binary dir. You can move your doxy into separate
component, and call cmake to process installation of particular component.
Something like:
INSTALL(DIRECTORY html/
DESTINATION /share/doc/${PROJECT_NAME}
On Sat, Dec 20, 2008 at 3:09 AM, Brad Aisa wrote:
> I would like to create a target that will copy (or link) a big whack of
> include files defined in my project to a local /include folder. (They start
> life in a bunch of subfolders, and some of them are generated
> programmatically during the b
may be this can work too:
file(glob find_paths /usr/include/libNAME-*)
find_path(INC_PATH NAMES libName/name.h PATHS ${find_paths})
On 10/23/08, Wilfried Holzke <[EMAIL PROTECTED]> wrote:
> Hi,
>>>
>>> I have an library header file in
>>> "/usr/include/libNAME-version/libNAME/name.h" and want to f
On Fri, Oct 3, 2008 at 1:22 AM, 0xd34df00d <[EMAIL PROTECTED]> wrote:
> 2008/10/2 Eric Noulard <[EMAIL PROTECTED]>:
> > 2008/10/2 0xd34df00d <[EMAIL PROTECTED]>:
> >> Hi there!
> >>
> >> I have a project which consists of main application, few helper
> >> libraries and some plugins, each of them i
2008/10/2 user790 user790 <[EMAIL PROTECTED]>
> Disabling specific warnings is a simple task so I thought I could do it
> myself but I must admit defeat. A simple CMakeLists.txt like this won't
> work.
>
> project(testcmake)
> # None of this works
> #set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /wd4669
On Fri, Oct 3, 2008 at 2:15 AM, Alexander Neundorf
<[EMAIL PROTECTED]>wrote:
> On Friday 19 September 2008, Tanguy Krotoff wrote:
> > Hi everybody
> >
> > I would like to change the directory layout generated by CPack given
> > the generator used.
>
> AFAIK this is currently not possible.
> And ac
t;\"${binDirNative}\\main.js.bin\""
>> COMMAND ${COMPILE_SCRIPT} "-o \"${binDirNative}\\main.js.bin\""
>> DEPENDS "\"${binDirNative}\\main.js\"" )
>> ADD_CUSTOM_TARGET(
>> Test DEPENDS "\"${binDirNative}\\m
I don't think it is correct.
Better, you should pass configuration which you want to install to cpack.
For your solution, I suppose you need more elaborate build process. While VS
can do this job for you, on Unix you should (manually) explicitly build all
of your configurations. That is: (this usua
On Tue, Sep 30, 2008 at 3:45 PM, Jonas Bähr <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm using a macro [1] iterating over a list of source files and setting a
> COMPILE_FLAGS property. The problem is that there are some files in the list
> which are generated (Qt moc files, produces by QT_WRAP_CPP) wh
On Fri, Sep 26, 2008 at 2:40 PM, Jan Roehrich <[EMAIL PROTECTED]>wrote:
> Hello list,
>
> I have the following problem:
>
> I'm using cmake in a C++ project where I create some executables which
> sources rest in its own directories. These
> directories are included using ADD_SUBDIRECTORY.
>
> One
Look for CMAKE_INSTALL_SO_NO_EXE in your cache / CMakeLists.
Also, look for its definition in cmake/Modules/Platform/Linux.cmake.
On Thu, Sep 25, 2008 at 5:54 PM, Jan Dinger <[EMAIL PROTECTED]>wrote:
> Hallo folks,
>
> I've build my library with cmake, and I'll install (make install) my
> librar
This week I played with xerces too :) but on windows, so I suppose there
will be different view point on this problem.
1) I think using FIND_PATH(XERCESC_INCLUDE_DIR
xercesc/util/XercesVersion.hpp) is slightly better, because there may be
different xercesc files or directories.
2) SET(XERCESC_NAM
On Thu, Sep 25, 2008 at 12:12 AM, Eric (Brad) Lemings <[EMAIL PROTECTED]>wrote:
>
> Consider the following:
>
> CMakeLists.txt:
>set (ZERO 0)
>configure_file (
>${CMAKE_SOURCE_DIR}/include/config.h.cmake
>${CMAKE_BINARY_DIR}/include/config.h
>)
>
> ${CMAKE_SOURC
Here we can call myC::myfunc(), because its implementation is accessible
from here.
I can be wrong, because I don't know how exactly you can define template
classes and functions' implementations, but generally this should work.
>
> Roy
>
> On Mon, Sep 22, 2008 at 06:00:5
On Tue, Sep 23, 2008 at 11:05 PM, George Neill <[EMAIL PROTECTED]> wrote:
> Hi Manu,
>
> On Tue, Sep 23, 2008 at 1:54 PM, Emmanuel Blot <[EMAIL PROTECTED]> wrote:
> >> The only way would be something like this:
> >>
> >> set(a "-mcpu=arm7tdmi -std=gnu99 -fgnu89-inline -finline-functions")
> >> set
On Tue, Sep 23, 2008 at 10:10 AM, Sharma, Gaurav <
[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> Can anybody tell me that If I wish to link my one static lib 'A' with other
> multiple static libs statically(all these libs should become part of my 'A')
> on Borland c++ 5.5 platform then how can I do
Use add_custom_command to compile your files. This one accepts source and
destination file names for proper dependency handling.
Next, use add_custom_target command with dependencies on add_custom_target's
output.
For example:
add_custom_command(OUTPUT myscript.compiled
COMMAND compile_script mysc
On Mon, Sep 22, 2008 at 10:00 AM, Roy Zuo <[EMAIL PROTECTED]> wrote:
> Hello eveyone,
>
> I am just new to cmake and have some trouble when compiling a big
> project whose cpp source files are put deep inside subdirectories.
>
> In my CMakeLists.txt, I use AUX_SOURCE_DIRECTORY(subdir VARX) and
> S
I've hurried a bit when I was writing previous message.
On Sat, Sep 20, 2008 at 8:12 PM, Tanguy Krotoff <[EMAIL PROTECTED]> wrote:
> > FIrst of all, there are a couple of discussions about using
> > CPACK_SET_DESTDIR, install prefixes and co in this list which are about
> same
> > problems: direc
On Fri, Sep 19, 2008 at 9:15 PM, Tanguy Krotoff <[EMAIL PROTECTED]> wrote:
> Hi everybody
>
> I would like to change the directory layout generated by CPack given
> the generator used.
> In a way, I would like a more fine-grained control about what CPack
> generates and after reading the different
On Wed, Sep 17, 2008 at 10:59 AM, Jesper Eskilson <[EMAIL PROTECTED]>wrote:
> Timenkov Yuri wrote:
>
>>
>>
>> On Tue, Sep 16, 2008 at 11:08 AM, Jesper Eskilson <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:
>>
>>Hi all,
>>
>>
he value of MYVAR: " $ENV{MYVAR})
execute_process(COMMAND "/usr/bin/env" OUTPUT_VARIABLE myEnvOut)
#message(STATUS "Local Environment: ${myEnvOut}")
string(REGEX MATCH "MYVAR=[^\n]*" MyVarEnv "${myEnvOut}")
message(STATUS "Found MYVAR=${MyVarEnv}")
&g
On Monday 07 July 2008 15:53:00 Alexander Bubnov wrote:
> Hello!
>
> Below simple example to clarify the problem.
>
> My CMakeLists.txt:
>
> cmake_minimum_required(VERSION 2.6)
>
> set(ENV{MYVAR} "SOME VALUE")
> message("the value of MYVAR: " $ENV{MYVAR})
>
> the output:
>
> the value of MYVAR: S
On Monday 07 July 2008 10:26:49 Miguel A. Figueroa-Villanueva wrote:
> Hello,
>
> I would like to propose the addition of a NO_CACHE keyword to the
> find_xxx commands that would treat as a non-cached variable. I
> have posted this as a feature request with an initial patch
> implementing it for
On Thursday 03 July 2008 05:24:07 Miguel A. Figueroa-Villanueva wrote:
> Hello,
>
> Since EXECUTABLE_OUTPUT_PATH / LIBRARY_OUTPUT_PATH have been replaced
> with the CMAKE_RUNTIME_OUTPUT_DIRECTORY /
> CMAKE_LIBRARY_OUTPUT_DIRECTORY they shouldn't appear in the GUI
> (CMakeSetup, QtDialog). That gi
On Friday 27 June 2008 18:14:05 Jorrit Schaap wrote:
> Hi,
>
> We have quite a large source tree with many libraries and many
> executables. We use CMake to build everything which works great.
>
> To deploy the executables we create deb packages by hand, gathering some
> executables and libs for
On Tuesday 24 June 2008 20:27:53 J wrote:
> Greetings all!
>
> I've been sold on cmake. From what I gather, it's hands down better than
> automake and family. However, I do have a problem with not having a
> configure script.
>
> A couple of the main benefits of having a configure script are lett
On Monday 23 June 2008 20:43:29 Mike Arthur wrote:
> On Monday 23 June 2008 17:30:21 Timenkov Yuri wrote:
> > Hmm, I don't think this should be a big deal:
> >
> > qt4_wrap_cpp(MyApp_MOC_SRCS ${MyApp_HDRS})
> > source_group("Autogenerated MOC files" FILES
On Monday 23 June 2008 20:17:06 Mike Arthur wrote:
> On Monday 23 June 2008 16:36:53 Timenkov Yuri wrote:
> > Just add them to corresponding target. CMake won't try to compile them if
> > they don't have source file extension. If file has a source file extension,
> &
On Monday 23 June 2008 19:22:28 Mike Arthur wrote:
> It seems that the CMake Visual Studio 2008 project generator won't add any
> source files that it doesn't use in a add_executable or add_library call.
> I've tried manually adding others using source_group but this doesn't seem to
> make any d
On Friday 20 June 2008 19:55:55 Mike Arthur wrote:
> On Friday 20 June 2008 16:51:15 Timenkov Yuri wrote:
> > However, if you have complex deployment layout, you should prefer
> > installing your project and running from target location. Trying to make
> > in-source runs may b
On Friday 20 June 2008 18:48:18 Mike Arthur wrote:
> Part 3 in my never-ending quest to replace our Visual-Studio-based build
> system with CMake has me tearing my hair out...
>
> I've set CMAKE_RUNTIME_OUTPUT_DIRECTORY to bin so everything is build
> correctly in bin/Debug or bin/Release depend
On Thursday 05 June 2008 17:47:27 Mathieu Malaterre wrote:
> On Thu, Jun 5, 2008 at 3:39 PM, Timenkov Yuri <[EMAIL PROTECTED]> wrote:
> > On Thursday 05 June 2008 17:36:06 Mathieu Malaterre wrote:
> >> Hi,
> >>
> >>Has anyone started working on th
On Thursday 05 June 2008 17:36:06 Mathieu Malaterre wrote:
> Hi,
>
>Has anyone started working on the development vs runtime package.
> For example the runtime package should only install libfoo.so.1.2
> while the -dev package would distribute the libfoo.so symlink to
> libfoo.so.1.2.
> I kn
On Thursday 15 May 2008 20:01:02 kent williams wrote:
> I won't name the package because I find this construction really
> stupid, but I'm writing CMakeLists.txt files for a package we want to
> use and came across this:
>
>
> %_floof: %.c
> $(CC) $(CFLAGS) -DFLOOF -o $@ -lfloof
>
> So I don
On Wednesday 07 May 2008 16:59:35 Eric Noulard wrote:
> Oops forgot to CC the list
>
> -- Forwarded message --
> From: Eric Noulard <[EMAIL PROTECTED]>
> Date: 7 mai 2008 14:58
> Subject: Re: [CMake] how to install files outside /usr in rpm?
> To: Erik Sjölund <[EMAIL PROTECTED]>
>
hey may be represented as phony
targets, which cause build of every project which enters group (User may
build all projects in folder). Though this is now possible with
add_custom_target command.
>
>
> On Sat, May 3, 2008 at 6:13 AM, Timenkov Yuri <[EMAIL PROTECTED]>
>
>
On Saturday 03 May 2008 23:09:16 Alin M Elena wrote:
> Hi,
>
> Thanks Yuri.
> Based on your observations I got a solution.
> Note that I use doxygen to generate the documentation so I use the
> find_package(Doxygen) somewhere before in CMakeLists.txt
>
> Here is what I did
> if(DOXYGEN)
> confi
On Saturday 03 May 2008 19:41:02 Alin M Elena wrote:
> Hi,
>
> Is there any way to add a dependency to install or preinstall targets?
>
> The idea is simple. I have a custom target that builds the documentation
> from sources.
> When I package or install I want to be sure that I have up-to-date
> d
On Saturday 03 May 2008 05:35:02 Michael Andronov wrote:
> Let me explain briefly my question:
>
> I have the following dir structure with my source file:
> foo/
> library/{ some code here for the library}
> samples/
>example1/{ some code here for example 1}
>
On Thursday 01 May 2008 16:05:34 Bill Hoffman wrote:
> Leopold Palomo Avellaneda wrote:
> > A Dimecres 30 Abril 2008, John Doe va escriure:
> >> Hello,
> >>
> >> I just started using ubuntu linux and it is a pleasure to see that
> >> they provide both static and shared versions of libtcl8.4. Is th
On Monday 21 April 2008 17:05:32 [EMAIL PROTECTED] wrote:
> Falko Bilz schrieb am 21.04.2008 15:05
> _
>
> Hello,
>
>
>
> How can I set specific link libraries for the two different targets
> 'Debug' and 'Release' ? I've tried
>
>
> On Tue, Apr 15, 2008 at 1:14 PM, Timenkov Yuri <[EMAIL PROTECTED]>
>
> wrote:
> > On Tuesday 15 April 2008 20:56:11 David Cole wrote:
> > > Something must be wrong with your build tree or your CMake
> > > installation. This is from the CMake 2.4.8 Modules/CPack.
CATABLE)
>
> set(CPACK_PACKAGE_RELOCATABLE "false")
>
> endif(CPACK_PACKAGE_RELOCATABLE)
>
>
> If CPACK_PACKAGE_RELOCATABLE is set to something other than "true" or
> "false" at CPack time, then something very odd is happening
>
> If you start
On Tuesday 25 March 2008 19:54:08 Alexander Neundorf wrote:
> On Tuesday 25 March 2008, Timenkov Yuri wrote:
> > Can anyone point me in right direction?
>
> Please file a feature request on the cmake bug tracker for cpack. We don't
> have too much feedback for cpack so t
Hi everyone.
This is just FYI.
I'm started to playing with CPack (2.4) for Apple (Tiger 10.4, PackageMaker
v2.1.1), and encountered very strange error:
CPack: Compress package
The package could not be created because of the following errors:
No package identifier specified.
While investigating
On Wednesday 09 April 2008 10:13:58 Ilya Shvetsov wrote:
> On Wed, 09 Apr 2008 07:32:59 +0300, Vladimir Sysoev
>
> <[EMAIL PROTECTED]> wrote:
> > Ilya,
> > I suppose you have to specify your libraries as dependency to target.
> >
> > - vladimir
>
> I did.
> I give example just to show.
>
> Project(
On Monday 07 April 2008 19:37:26 Mathias Dalheimer wrote:
> Hi,
>
> as a new cmake user I am pretty impressed how painless software builds
> can be - so first of all, thanks for releasing this software.
I came to different solution. I have to build statically with some libraries
(including boost),
On Thursday 03 April 2008 23:41:16 Filipe Sousa wrote:
> Alexander Neundorf wrote:
> > On Thursday 03 April 2008, Alan W. Irwin wrote:
> >
> > One prinicipal problem I see with pkg-config is that it is intended to be
> > used in such a way that the stdout is directly used as command line
> > argume
On Monday 31 March 2008 17:31:56 Crni Gorac wrote:
> On Mon, Mar 31, 2008 at 8:03 AM, Timenkov Yuri <[EMAIL PROTECTED]>
wrote:
> > You may try to add install(SCRIPT/CODE) command which ensures that
> > translations are built.
> >
> > install(c
On Monday 31 March 2008 13:07:43 Timenkov Yuri wrote:
> On Monday 31 March 2008 13:01:06 Niko Vuokko wrote:
> > Hi,
> >
> > I have
> >
> > SET(CMAKE_VERBOSE_MAKEFILE TRUE)
>
> This sets CMAKE_VERBOSE_MAKEFILE variable only for current CMakeLists.txt.
>
On Monday 31 March 2008 13:01:06 Niko Vuokko wrote:
> Hi,
>
> I have
>
> SET(CMAKE_VERBOSE_MAKEFILE TRUE)
This sets CMAKE_VERBOSE_MAKEFILE variable only for current CMakeLists.txt.
If you want verbose output in all projects, you should use something like:
set(CMAKE_VERBOSE_MAKEFILE TRUE CACHE BOOL
You may try to add install(SCRIPT/CODE) command which ensures that
translations are built.
install(code "
execute_process(
COMMAND \${CMAKE_MAKE_PROGRAM} translations
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
)
FILE(INSTALL
DESTI
On Friday 28 March 2008 18:05:40 Andreas Pakulat wrote:
> On 28.03.08 09:36:06, David Thulson wrote:
> > It would be nice if this could get into 2.6.0. Boost 1.35 is about to
> > be released:
> >
> > http://lists.boost.org/boost-users/2008/03/34896.php
> >
> > And it at least appears that the late
On Friday 28 March 2008 14:02:03 Stephen Collyer wrote:
> Timenkov Yuri wrote:
> > Did you run this on clean build directory or CMakeCache.txt existed?
> > If so, you should manually delete CURL_INCLUDE_DIR value from cache (or
> > whole cache).
> >
> > The poin
On Friday 28 March 2008 13:26:43 Stephen Collyer wrote:
> Timenkov Yuri wrote:
> > On Friday 28 March 2008 12:48:49 Stephen Collyer wrote:
> >> I'm trying to change some find* modules to prefer /usr/local/lib
> >>
> >> over /usr/lib and I can't get it
On Friday 28 March 2008 12:48:49 Stephen Collyer wrote:
> I'm trying to change some find* modules to prefer /usr/local/lib
>
> over /usr/lib and I can't get it to work. I have, for example:
> > FIND_PATH(CURL_INCLUDE_DIR
> > NAMES
> > curl/curl.h
> > PATHS
> > /usr/local/include
On Tuesday 25 March 2008 19:54:08 Alexander Neundorf wrote:
> On Tuesday 25 March 2008, Timenkov Yuri wrote:
> > Can anyone point me in right direction?
>
> Please file a feature request on the cmake bug tracker for cpack. We don't
> have too much feedback for cpack so th
Can anyone point me in right direction?
On Friday 21 March 2008 13:08:02 Timenkov Yuri wrote:
> I have following requirement: I have big source tree (~100 projects -
> libraries or binaries), and want to package them in different ways. And
> encapsulate packaging knowledge in sin
On Monday 24 March 2008 21:20:45 Ilya Shvetsov wrote:
> On Mon, 24 Mar 2008 20:02:27 +0200, Timenkov Yuri
>
> <[EMAIL PROTECTED]> wrote:
> >> May be exist some way do the same with COMPILE_FLAGS ?
> >
> > I do it following way:
> > set_source
On Monday 24 March 2008 20:42:46 Ilya Shvetsov wrote:
> Hi, all.
>
> I need define some compile flags for my targets. This flags deepend on
> config tipe.
> With LINK_FLAGS I can do this very simple. I can write just
>
> set_target_properties(target1 PROPERTIES
> LINKER_FLAGS_FINAL "som
On Monday 24 March 2008 12:23:04 Ákos Maróy wrote:
> Andreas Pakulat wrote:
> > Use out-of-source builds, then you can just rm -rf builddir and be done.
>
> I'd love to, but I want to use Eclipse for the building itself, and it
> seems Eclipse needs in-source builds to be able to do meaningful
> de
I have following requirement: I have big source tree (~100 projects -
libraries or binaries), and want to package them in different ways. And
encapsulate packaging knowledge in single place.
That is I want that some libraries may enter into different packages. That is
pakcageA contains libA and
67 matches
Mail list logo
