Hello,
I am having some problem with FindQt4.cmake (both in v2.8.11.2 and
v2.8.10.2). I have localised the problem to a find_program call and added
message() calls around this find_program call.
message("env QTDIR $ENV{QTDIR}")
find_program(QT_QMAKE_EXECUTABLE NAMES ${QMA
Hi,
I have the same problem. I use source_group(s) and I can get rid of this
error by deleting some *.filters files manually after cmake generates the
projects. Obviously all groups in the the visual studio project tree are
lost.
Regards,
Paul
On Thu, Jan 31, 2013 at 3:53 AM, Andreas Mohr wro
I can also confirm that the problem also appears in custom targets where
the path is in the name of the output.
--
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 check the CMake FAQ at:
Hello,
I have the following in my Cmakelists.txt file:
set_target_properties( MyApp PROPERTIES STATIC_LIBRARY_FLAGS
"${SOME_LIB_FILENAME}")
If the SOME_LIB_FILENAME path includes white space such as
c:/Projects/Foo 4/Src/somelib.lib
the generated visual studio 2008 file includes the following
Hi all,
I have found the problem.
I have moved the call to add_custom_target to a line after project(). Now it
works.
Thanks,
Paul.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensour
Hi,
I have a custom target which basically calls the cmake install script. The
install script can install both debug and release configs so I define the
custom command with the -DBUILDTYPE=${CMAKE_CFG_INTDIR}, as follows:
add_custom_target(My_Install_After_Build ALL COMMAND ${CMAKE_COMMAND}
-DBUI
Thanks, the custom target works great.
___
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 check the CMake FAQ at:
http://www.cmake.org/Wiki/CMa
quot; dependency. This sounds kind of
unhealthy.
b. remove "install_after_all" from ALL_BUILD. What would be the appropriate
way of doing this?
Again, thanks for your help!.
Paul
On Mon, Mar 14, 2011 at 5:07 PM, David Cole wrote:
> On Mon, Mar 14, 2011 at 10:16 AM, Paul Baumer
> wro
Sorry for not being clear enough. I meant (2).
(2) included in the "Build Solution" command, executing after all
> other targets have been built, so that "F7" or "Build All" will
> actually build the INSTALL target?
>
>
___
Powered by www.kitware.com
Vi
Hello,
I use cmake most of the time with Visual Studio. By default the INSTALL
target is not selected in the Configuration Manager for a cmake solution.
I would like to change this default. Any suggestions ?
P.S. If this needs to make some changes to the generators, I have no problem
with that e
Hello,
I use cmake most of the time with Visual Studio. By default the INSTALL
target is not selected in the Configuration Manager for a cmake solution.
I would like to change this default. Any suggestions ?
P.S. If this needs to make some changes to the generators, I have no problem
with that e
11 matches
Mail list logo