Re: [CMake] need help fixing warning message... 3.0
if it exists as a target; I need to know the path to the built library for
subsequent projects to link against. I have to manually add the option
-Lwrote:
> Maybe you can explain _why_ you need to do it this way? Can it be solved
> more inline with the better cross-compile support in cmake-3.0?
>
> On 26. Mai 2014 19:29:20 MESZ, J Decker wrote:
>
>> So... no alternatives to location in this instance?
>>
>>
>> On Sat, May 24, 2014 at 7:28 PM, J Decker wrote:
>>
>>> CMake Warning (dev) at
>>> C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
>>> (get_property):
>>> Policy CMP0026 is not set: Disallow use of the LOCATION target
>>> property.
>>> Run "cmake --help-policy CMP0026" for policy details. Use the
>>> cmake_policy
>>> command to set the policy and suppress this warning.
>>>
>>> The LOCATION property should not be read from target "keypad.isp".
>>> Use the
>>> target name directly with add_custom_command, or use the generator
>>> expression $, as appropriate.
>>>
>>> Call Stack (most recent call first):
>>> security.null/CMakeLists.txt:23 (my_target_link_libraries)
>>> This warning is for project developers. Use -Wno-dev to suppress it.
>>>
>>>
>>> -
>>>
>>> macro(my_target_link_libraries target )
>>> if(CMAKE_COMPILER_IS_GNUCC AND __ANDROID__ )
>>>foreach( target_lib ${ARGN} )
>>> if( TARGET ${target_lib} )
>>> get_property( lib_path TARGET ${target_lib} PROPERTY
>>> LOCATION)
>>> get_property( existing_outname TARGET ${target_lib}
>>> PROPERTY OUTPUT_NAME )
>>> if( NOT existing_outname )
>>> set( existing_outname ${target_lib} )
>>> endif( NOT existing_outname )
>>> if( ${lib_path} MATCHES "(.*)/([^/]*)$" )
>>> get_target_property(existing_link_flags ${target}
>>> LINK_FLAGS)
>>> if(existing_link_flags)
>>> set(new_link_flags "${existing_link_flags} -L
>>> ${CMAKE_MATCH_1} -l ${existing_outname}")
>>> else()
>>> set(new_link_flags "-L ${CMAKE_MATCH_1} -l
>>> ${existing_outname}")
>>> endif()
>>> set_target_properties( ${target} PROPERTIES LINK_FLAGS
>>> ${new_link_flags})
>>> add_dependencies( ${target} ${target_lib} )
>>> endif( ${lib_path} MATCHES "(.*)/([^/]*)$" )
>>> else()
>>> target_link_libraries( ${target} ${target_lib} )
>>> endif( TARGET ${target_lib} )
>>>endforeach( target_lib ${ARGN} )
>>> else()
>>> target_link_libraries( ${target} ${ARGN} )
>>> endif()
>>> endmacro()
>>>
>>> --
>>> In the script I'm getting LOCATION to know if the referenced library is
>>> a full pathname or a short name so I can strip the path appropriately... I
>>> don't think the target_file solution works here, what other alternative is
>>> there?
>>>
>>
>> --
>>
>> Powered by www.kitware.com
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Kitware offers various services to support the CMake community. For more
>> information on each offering, please visit:
>>
>> CMake Support: http://cmake.org/cmake/help/support.html
>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] need help fixing warning message... 3.0
Maybe you can explain _why_ you need to do it this way? Can it be solved more
inline with the better cross-compile support in cmake-3.0?
On 26. Mai 2014 19:29:20 MESZ, J Decker wrote:
>So... no alternatives to location in this instance?
>
>
>On Sat, May 24, 2014 at 7:28 PM, J Decker wrote:
>
>> CMake Warning (dev) at
>>
>C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
>> (get_property):
>> Policy CMP0026 is not set: Disallow use of the LOCATION target
>property.
>> Run "cmake --help-policy CMP0026" for policy details. Use the
>> cmake_policy
>> command to set the policy and suppress this warning.
>>
>> The LOCATION property should not be read from target "keypad.isp".
>Use
>> the
>> target name directly with add_custom_command, or use the generator
>> expression $, as appropriate.
>>
>> Call Stack (most recent call first):
>> security.null/CMakeLists.txt:23 (my_target_link_libraries)
>> This warning is for project developers. Use -Wno-dev to suppress it.
>>
>>
>> -
>>
>> macro(my_target_link_libraries target )
>> if(CMAKE_COMPILER_IS_GNUCC AND __ANDROID__ )
>>foreach( target_lib ${ARGN} )
>> if( TARGET ${target_lib} )
>> get_property( lib_path TARGET ${target_lib} PROPERTY
>LOCATION)
>> get_property( existing_outname TARGET ${target_lib}
>PROPERTY
>> OUTPUT_NAME )
>> if( NOT existing_outname )
>> set( existing_outname ${target_lib} )
>> endif( NOT existing_outname )
>> if( ${lib_path} MATCHES "(.*)/([^/]*)$" )
>> get_target_property(existing_link_flags ${target}
>> LINK_FLAGS)
>> if(existing_link_flags)
>> set(new_link_flags "${existing_link_flags} -L
>> ${CMAKE_MATCH_1} -l ${existing_outname}")
>> else()
>> set(new_link_flags "-L ${CMAKE_MATCH_1} -l
>> ${existing_outname}")
>> endif()
>> set_target_properties( ${target} PROPERTIES
>LINK_FLAGS
>> ${new_link_flags})
>> add_dependencies( ${target} ${target_lib} )
>> endif( ${lib_path} MATCHES "(.*)/([^/]*)$" )
>> else()
>> target_link_libraries( ${target} ${target_lib} )
>> endif( TARGET ${target_lib} )
>>endforeach( target_lib ${ARGN} )
>> else()
>> target_link_libraries( ${target} ${ARGN} )
>> endif()
>> endmacro()
>>
>> --
>> In the script I'm getting LOCATION to know if the referenced library
>is a
>> full pathname or a short name so I can strip the path
>appropriately... I
>> don't think the target_file solution works here, what other
>alternative is
>> there?
>>
>
>
>
>
>--
>
>Powered by www.kitware.com
>
>Please keep messages on-topic and check the CMake FAQ at:
>http://www.cmake.org/Wiki/CMake_FAQ
>
>Kitware offers various services to support the CMake community. For
>more information on each offering, please visit:
>
>CMake Support: http://cmake.org/cmake/help/support.html
>CMake Consulting: http://cmake.org/cmake/help/consulting.html
>CMake Training Courses: http://cmake.org/cmake/help/training.html
>
>Visit other Kitware open-source projects at
>http://www.kitware.com/opensource/opensource.html
>
>Follow this link to subscribe/unsubscribe:
>http://www.cmake.org/mailman/listinfo/cmake
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] need help fixing warning message... 3.0
So... no alternatives to location in this instance?
On Sat, May 24, 2014 at 7:28 PM, J Decker wrote:
> CMake Warning (dev) at
> C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
> (get_property):
> Policy CMP0026 is not set: Disallow use of the LOCATION target property.
> Run "cmake --help-policy CMP0026" for policy details. Use the
> cmake_policy
> command to set the policy and suppress this warning.
>
> The LOCATION property should not be read from target "keypad.isp". Use
> the
> target name directly with add_custom_command, or use the generator
> expression $, as appropriate.
>
> Call Stack (most recent call first):
> security.null/CMakeLists.txt:23 (my_target_link_libraries)
> This warning is for project developers. Use -Wno-dev to suppress it.
>
>
> -
>
> macro(my_target_link_libraries target )
> if(CMAKE_COMPILER_IS_GNUCC AND __ANDROID__ )
>foreach( target_lib ${ARGN} )
> if( TARGET ${target_lib} )
> get_property( lib_path TARGET ${target_lib} PROPERTY LOCATION)
> get_property( existing_outname TARGET ${target_lib} PROPERTY
> OUTPUT_NAME )
> if( NOT existing_outname )
> set( existing_outname ${target_lib} )
> endif( NOT existing_outname )
> if( ${lib_path} MATCHES "(.*)/([^/]*)$" )
> get_target_property(existing_link_flags ${target}
> LINK_FLAGS)
> if(existing_link_flags)
> set(new_link_flags "${existing_link_flags} -L
> ${CMAKE_MATCH_1} -l ${existing_outname}")
> else()
> set(new_link_flags "-L ${CMAKE_MATCH_1} -l
> ${existing_outname}")
> endif()
> set_target_properties( ${target} PROPERTIES LINK_FLAGS
> ${new_link_flags})
> add_dependencies( ${target} ${target_lib} )
> endif( ${lib_path} MATCHES "(.*)/([^/]*)$" )
> else()
> target_link_libraries( ${target} ${target_lib} )
> endif( TARGET ${target_lib} )
>endforeach( target_lib ${ARGN} )
> else()
> target_link_libraries( ${target} ${ARGN} )
> endif()
> endmacro()
>
> --
> In the script I'm getting LOCATION to know if the referenced library is a
> full pathname or a short name so I can strip the path appropriately... I
> don't think the target_file solution works here, what other alternative is
> there?
>
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte wrote: > My way of dealing with this problem is similar to other people here: > > 1. I have a separate Python post-build script designed to be driven > through command line. > This script read somewhere the list of direct binary dependencies of > the target[1] and copy them in the > output directory. The script also check that the dependency file is > not already in that place. > 2. I have CMake scripts that provide project definition macros which does > the actual work > of setting up the projects depending on the kind but it's all > specific to my project/domain. > 3. The CMake scripts will add a custom post-build command calling the > Python post-build script with the correct arguments for the specific target. > 4. Therefore, after build of any of MY projects of my Visual Studio > solution, the post build script copy the > necessary dependencies in what I call the "install" directory which > is settup in a way similar to a normal install > of the application. This happen after the target is generated into > it's output directory; so first the project is compiled > with it's dependencies, then all these binaries are copied in the > "install" directory. > 5. After generating my VS solution using CMake, the first thing I do is > to change the debug paths of the executables projects > so that debugging them will actually run the binaries in the > "install" direction. This is because I want that directory to be > as close as the final directory, so I can catch issues with missing > dlls immediately (and in practice it helped a lot catch any kind of > dependencies and configuration issues) > It's also easier to generate a test build this way. > > Note that: > > - I don't want to polluate the developer's PATH with anything from the > dependencies, which is one reason why I have so many constraints >(that CMake only solve in half) > - I want to be able to debug most of my dependencies (for a lot of > reasons) so I NEED to have their sources (except if I have no choice) >and I NEED to have their sources debuggable and visible from the > debugger. > - Why can't I use the install command from CMake? My understanding is > that it's used to install the application in the system, which is NOT what > I want to do here. > > Install can be targeted anywhere doesn't have to be 'into the the system'. With Install rules it becomes just one minor step more to add packaging to get an installer for distribution. > It's one of the reasons I have found CMake frustrating, there is not much > helping with these kind of contexts. > > [1] I didn't find a way to provide the dependencies automatically because > some dlls are simply not part of the project, > So I have a specific file with all the direct binary dependencies > explicitely listed for each target. > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] QT4_CREATE_TRANSLATION cannont fill my *.ts files
o/
Just for the record, I solved the issue: if there are empty *.ts files
lupdate will fail to populate them.
Regards
On Fri, May 23, 2014 at 2:25 PM, Sergio Vera wrote:
>
> Hello fellow CMakers
>
> I'm following the CMake guide to Qt based internationalization of my app:
> http://www.cmake.org/Wiki/CMake:How_To_Build_Qt4_Software
>
> However, After many attempts I cannot generate the proper files:
> Here is an digest of my CMakeLists.txt
>
> FILE(GLOB INCLUDE_FILES *.h)
> FILE(GLOB SOURCE_FILES *.txx *.cpp * cxx)
> FILE(GLOB UI_FILES *.ui)
> #...
> SET(FILES_TO_TRANSLATE ${FILES_TO_TRANSLATE} ${INCLUDE_FILES} ${UI_FILES}
> ${SOURCE_FILES})
> FILE (GLOB TRANSLATIONS_FILES *.ts)
> QT4_CREATE_TRANSLATION(QM_FILES ${FILES_TO_TRANSLATE}
> ${TRANSLATIONS_FILES})
>
> I have created two empty ts files in my source dir: CoreApp_es.ts and
> CoreApp_en.ts
>
> When I compile the project, Qt's lupdate tries to populate the ts files
> with the literals from my files:
>
> Generating
> /home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/CoreApp_es.ts
> Generating
> /home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/CoreApp_en.ts
> Scanning directory
> '/home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/Reporting'...
> Scanning directory
> '/home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/images'...
>
>
> although it seems to analyze as well my boost header files.
>
> /usr/include/boost/thread/future.hpp:3385: Unbalanced opening parenthesis
> in C++ code (or abuse of the C++ preprocessor)
> /home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/Scene.cxx:41:
> Discarding unconsumed meta data
>
>
> However, at the end, the ts files are still empty and 0 size so when
> lrelase attempts to compile the translations it complains:
>
> /usr/include/boost/thread/future.hpp:3385: Unbalanced opening parenthesis
> in C++ code (or abuse of the C++ preprocessor)
> /home/sergio/src/alma/HEAR-EU/hear-eu-planner/HiResViewer/CoreApp/Scene.cxx:41:
> Discarding unconsumed meta data
>
>
> I'm out of ideas ny now. Any help would be kidnly appreciated
> --
> Sergio Vera
>
> Alma IT Systems
> C/ Vilana, 4B, 4º 1ª
> 08022 Barcelona
> T. (+34) 932 380 592
> www.alma3d.com
>
--
Sergio Vera
Alma IT Systems
C/ Vilana, 4B, 4º 1ª
08022 Barcelona
T. (+34) 932 380 592
www.alma3d.com
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?
On Mon, May 26, 2014 at 5:08 PM, Dan Kegel wrote: > On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte > wrote: > > - Why can't I use the install command from CMake? My understanding is > that > > it's used to install the application in the system > > Not really. It's to massage the installed files into their final form -- > but not neccessarily into their final location. See > > http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake.27s_.22make_install.22_support_DESTDIR.3F Thanks for the precision. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] How to force cmake to omitt default LINUX pathes on FreeBSD
Hi How to force CMAKE to search for executables in /usr/local/bin first, not in /bin? I have: FIND_PROGRAM(FLEX_EXECUTABLE flex PATH /usr/local/bin DOC "path to the flex executable" NO_DEFAULT_PATH) But this is not proper way to. Regards niespodd -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte wrote: > - Why can't I use the install command from CMake? My understanding is that > it's used to install the application in the system Not really. It's to massage the installed files into their final form -- but not neccessarily into their final location. See http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake.27s_.22make_install.22_support_DESTDIR.3F -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?
My way of dealing with this problem is similar to other people here: 1. I have a separate Python post-build script designed to be driven through command line. This script read somewhere the list of direct binary dependencies of the target[1] and copy them in the output directory. The script also check that the dependency file is not already in that place. 2. I have CMake scripts that provide project definition macros which does the actual work of setting up the projects depending on the kind but it's all specific to my project/domain. 3. The CMake scripts will add a custom post-build command calling the Python post-build script with the correct arguments for the specific target. 4. Therefore, after build of any of MY projects of my Visual Studio solution, the post build script copy the necessary dependencies in what I call the "install" directory which is settup in a way similar to a normal install of the application. This happen after the target is generated into it's output directory; so first the project is compiled with it's dependencies, then all these binaries are copied in the "install" directory. 5. After generating my VS solution using CMake, the first thing I do is to change the debug paths of the executables projects so that debugging them will actually run the binaries in the "install" direction. This is because I want that directory to be as close as the final directory, so I can catch issues with missing dlls immediately (and in practice it helped a lot catch any kind of dependencies and configuration issues) It's also easier to generate a test build this way. Note that: - I don't want to polluate the developer's PATH with anything from the dependencies, which is one reason why I have so many constraints (that CMake only solve in half) - I want to be able to debug most of my dependencies (for a lot of reasons) so I NEED to have their sources (except if I have no choice) and I NEED to have their sources debuggable and visible from the debugger. - Why can't I use the install command from CMake? My understanding is that it's used to install the application in the system, which is NOT what I want to do here. It's one of the reasons I have found CMake frustrating, there is not much helping with these kind of contexts. [1] I didn't find a way to provide the dependencies automatically because some dlls are simply not part of the project, So I have a specific file with all the direct binary dependencies explicitely listed for each target. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Dependencies between static libraries
Jörg Kreuzberger wrote: Hi! i had a problem between depencendies of static libraris. Due to the used tools (qt, moc, uic) a library depends on another library, especially on header files generated by uic. This is a litte bit a broken design, but cannot fix it currently. On massive parallel builds ( 8 cores on ssd ) i get compiliation issues (missing header file) or broken dependencies ( header is updated later, lib already build). So i decided to use add_dependencies() macro for cmake to "clarify" these dependencies. Since then it seems that no more failure occured. Is this a correct way to handle this issue or are other solutions more reliable? Have you tried target_link_libraries(liba libb)? Even if that doesn't really "link", it should ensure proper dependencies. Eike -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Dependencies between static libraries
Hi! i had a problem between depencendies of static libraris. Due to the used tools (qt, moc, uic) a library depends on another library, especially on header files generated by uic. This is a litte bit a broken design, but cannot fix it currently. On massive parallel builds ( 8 cores on ssd ) i get compiliation issues (missing header file) or broken dependencies ( header is updated later, lib already build). So i decided to use add_dependencies() macro for cmake to "clarify" these dependencies. Since then it seems that no more failure occured. Is this a correct way to handle this issue or are other solutions more reliable? Mannheim HRB 504702 Geschäftsführer: Dipl.-Ing. (FH) Michael Brenk (Vorsitzender), Dipl.-Ing. (FH) Dipl.-Inf. (FH) Jens Heyen This e-mail may contain confidential and/or legally protected information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden. Thank you! -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
