Hi,
Take a look also at Michael suggestion,
http://www.cmake.org/pipermail/cmake/2011-November/047333.html
br
L.
Łukasz Tasz
2015-03-11 0:15 GMT+01:00 Mark Abraham :
> Hi,
>
> Sure, this is straightforward to do all at make time, if you're prepared to
> find out what the names
compiled in parallel, man.cpp.o will be
compiled after linking of all libs,
If main.cpp is compiling long then this is overall additional waist of
time which could be done much earlier.
Do you have some ideas how this situation could be optimised?
with best regards
Łukasz Tasz
--
Powered by
Does somebody has some ideas?
Can I enforce cmake to make library as a one 'shoot' - single command line?
thanks in advance
Lukasz
Łukasz Tasz
2012/12/5 Łukasz Tasz :
> Hi all,
>
> I have a problem with making static library.
> There is behaviour which is not clear for me
od idea to put same name of object info archive,
but it's still valid...
I would like to avoid replacing template for appending to static
library CMAKE_C_ARCHIVE_APPEND
thank in advance
Łukasz Tasz
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware
Hi All,
I have quick question,
Is there any possibilities to set build time variable?
something similar to CMAKE_VERBOSE_MAKEFILE which ends with make
variable VERBOSE.
As far as I found inside documentation there is no such a possibility,
but before starting alternative implementation,
I would
Hi
As far as I understood your problem correctly:
in main cmakelists create target that will agregate subtargets:
main_cmake:
add_custom_target(aggr_target)
add_subdirectory(a)
add_subdirectory(b)
a/CMakeLists.txt
add_custom_target(a_special_test COMMAND specialtest)
add_dependencies(aggr_targe
structure changes.
I think you got my question about attaching to cmake
--check-build-system commnad genfiles.py --cmake-only ...
thanks in advance
Lukasz
2011/11/8 Michael Hertling :
> On 11/08/2011 03:30 PM, Łukasz Tasz wrote:
>> Hi All,
>>
>> I have one issue connecte
Hi All,
I have one issue connected with generated code.
What is recommended way to proceed with generators which provides
source which is dynamic?
The setup looks like: generator has some input, and depending on this
input files are generated.
>From cmake point of view I need only this list of s
#x27;s why
-lbaz is added to link command.
Initially I thought that's a mater of scope IMPORTED target, then I
check docs and scope is same for 2.6, and 2.8.
regards
Lukasz
2011/10/27 Eric Noulard :
> 2011/10/27 Łukasz Tasz :
>> Problem solved.
>
> It would have been ni
Problem solved.
regards
Lukasz
2011/10/27 Łukasz Tasz :
> Hi All,
>
> I have small problem how to proceed with external library.
> I have project A which is producing one cmake target libfoo.
> This foo is link against lib bar, which is registered as imported
> library, and has
Hi All,
I have small problem how to proceed with external library.
I have project A which is producing one cmake target libfoo.
This foo is link against lib bar, which is registered as imported
library, and has imported location.
Lib foo is kind of wrapper/provider of functionality of bar lib. (ba
Hi,
in C,CMakelists.txt set variable which store include_dir but add
PARENT_SCOPE, and then use this variable in A,CMakeLists.txt to set
includes:
CCMakeLists.txt:
set(includesFromC "dir_name" PARENT_SCOPE)
ACMakeLists.txt:
add_subdirectory(C)
include_directories(${includesFromC})
Another op
Hi all,
with cmake 2.8.6 all my problems are solved,
I'm can easily recreate/replicate custom_target.
Thanks a lot!
Best regards
Lukasz
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and
> add_custom_target(TARGET generator
>COMMAND touch aaa.cxx
>COMMENT generate file
> )
>
> add_custom_command(OUTPUT aaa.cxx
>COMMAND echo "command"
>DEPENDS generator bar
> This does not work^^^
>
rget `../generator', needed by `aaa.cxx'. Stop.
make[1]: *** [CMakeFiles/foo.dir/all] Error 2
Why cmake assumes that generator is an output, since it is already
valid target...
thanks for help, regards
Lukasz
2011/10/20 Michael Hertling :
> On 10/20/2011 12:37 PM, Łukasz Tasz wrote:
Hi all,
In my cmake project I have few commands that are creating outputs.
But Unfortunately those outputs are used across many directories.
So my question is what's the real scope of output_command? only
Current_CmakeLists.txt?
Can I somehow make make_target that is creating output registered i
xecutables, and I need to manipulate includes a little, I wanted to
do this in wrapper macro, but it looks like I need to find some other
hook to attach in place when CMakelists will be processed.
Any ideas?
thanks a lot
Lukasz
2011/8/10 Michael Wild :
> On Wed 10 Aug 2011 04:51:36 PM CEST
Hi All,
Can somebody please advise me with this topic, if it is expected
behaviour or a bug?
thanks in advance
Lukasz
2011/8/4 Łukasz Tasz :
> Hi All,
>
> I have a question according include_directories() function and
> INCLUDE_DIRECTORIES directory property.
>
> Is it possibl
Hi All,
I have a question according include_directories() function and
INCLUDE_DIRECTORIES directory property.
Is it possible that I will know set of include directories that will
be used by preprocessor when I'm calling add_executable function?
I notticed, that order does not matter, for exampl
Hi,
I would like to execute process, during cmake phase, but I need to
tune LD_LIBRARY_PATH a little,
I would like to get something like:
execute_proccess(COMMAND LD_LIBRARY_PATH=my_path my_proccess
ERROR_VARIABLE _error)
Unfornately command above is not working...
I'm using cmake 2.6
thanks f
>
> I don't understand what you mean by partially. If you had
> cuda_add_executable(demo main.cxx demo1.cu demo2.cu), then main.cxx will be
> compiled by the host compiler, demo1.cu and demo2.cu will be compiled by
> nvcc (CUDA + host compiler), and then all will be linked by the host linker.
>
I
Hi all,
I have one issue with organising dependencies between projects.
I have three projects,
- first is application which contain static code of the application,
- second is library which is contain code for the library,
- third is library which generates the source code and headers,
Hi all,
>
> Other than the 'more elegant' prospect of being able to just put .cu files
> into a target, is there anything else deficient about the current FindCUDA
> macros? All you have to do really is to use cuda_add_executable instead of
> add_executable.
>
As far as I understood the topic ai
Hi,
Of course I read manual. But I'm a little bit confused. That's why I'm
asking about idea behind LINK_FLAGS,
Cmake is not consequent because when I'm adding:
add_library(test foo.cxx bar.cxx)
SET_TARGET_PROPERTIES( test PROPERTIES SOVERSION 1.2 VERSION 1.1)
it 'magicaly knows' how to build l
Hi all,
I got a simple question,
What is idea behind target property LINK_FLAGS?
When I add linker flag e.g --no-undefined then cmake is not alligning
it to real linker that will be used during linking.
for example --no-undefined is a valid ld switch, but when I specify it
LINK_FLAGS it will no
2011/2/21 Eric Noulard :
>
> Since the makefiles are generated by CMake WHY do you need
> to define a "make" var?
>
> What do you want to do ?
>
> CMake was not designed to let you decide generator specifics things.
>
That's cool, I really like it, and in most cases it works fine e.g
CMAKE_VERBOSE
Hi All,
Could somebody help me how to provide own predefined make varibable from
cmake configuration?
Such a variable should be avaliable in the context of all generated
makefiles.
I would like to receive output in a way:
in master Makefile:
export MY_OWN_DEBUG_VAR="3"
MY_OWN_DEBUG_VAR should b
27 matches
Mail list logo
