Re: [CMake] ExternalProject_Add + imported targets: no rule to make yourlibrary.so

2016-05-03 Thread Bill Hoffman

On 4/28/2016 4:31 PM, SnakE wrote:

set_target_properties(foo PROPERTIES IMPORTED_LOCATION foo.so)

https://cmake.org/cmake/help/v3.0/prop_tgt/IMPORTED_LOCATION.html?highlight=imported_location

"Full path to the main file on disk for an IMPORTED target."

You need to use a full path to foo.so, works by luck with make.

-Bill


--

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://public.kitware.com/mailman/listinfo/cmake


[CMake] Automatic moc, uic and rcc every build

2016-05-03 Thread Jonas Collberg
Hi,

I'm using CMake to create project configuration files for Visual Studio
2015 (generator: "Visual Studio 14 2015 Win64") and Qt Creator (generator:
"CodeBlocks - NMake Makefiles").

The biggest remaining problem I have is that every time I build or run a
project using the CodeBlocks generator, CMake goes through some
time-consuming and unnecessary (?) processing for every project. The output
of this processing step are the three lines:

Automatic moc, uic and rcc for target X
Built target X_automoc
Built target X

This processing of the automoc targets is done even though no changes have
been made to the source.

I've created a small repository with a demonstration of the problem at
https://bitbucket.org/joncol/cmake_qt_test. I use CMake version 3.5.2.

When building (or running) the project via the CodeBlocks build
configuration, you get the
"Automatic moc, uic and rcc for target myapp" output every time.

In my linked minimal example, it doesn't take much time, but for my real
work (large existing code base with many projects) it takes a significant
amount of time to do this.

Does anyone know of a way around this seemingly unnecessary processing of
automatic targets?

Regards,
Jonas Collberg
-- 

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://public.kitware.com/mailman/listinfo/cmake