Re: [CMake] CMake Tools for Visual Studio 1.0 Released!
On 2013-08-27 00:47, David Golub wrote: It's there--you just need to configure it to use lowercase instead of uppercase. Go to Tools Options in Visual Studio and select the CMake Tools page. Then, then on the Commands In Lowercase option. David Golub Wonderful! Thanks David! Also thanks to marco1475 (at https://cmaketools.codeplex.com/workitem/2) and Marek Vojtko for mentioning this option :-) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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] CMake Tools for Visual Studio 1.0 Released!
On 2013-08-25 23:28, David Golub wrote: Having received no bug reports for RC3, I’ve finalized the 1.0 release of CMake Tools for Visual Studio, which provides syntax highlighting and IntelliSense support for CMake. It is available for download from the project web site at http://cmaketools.codeplex.com Thanks, David. Would you advise users of RC3 of CMake Tools for Visual Studio to upgrade to the final version? Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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] CMake Tools for Visual Studio 1.0 Released!
On 2013-08-26 14:33, David Golub wrote: The two version differ solely in their version number, as there were no bugs reported in RC3. Actually, I did report an issue on RC3, asking for lowercase code completion of CMake commands: http://cmaketools.codeplex.com/workitem/2 What do you think? Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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] Remove _MBCS
On 2013-02-18 10:00, YanmingZou wrote:
I am developing an application on windows with VS2012 and CMake
(2.8.10.2). I want to use unicode in my program, so I add UNICODE and
_UNICODE with ADD_DEFINITIONS. However, there is always a _MBCS marco in
the generated project file. The project can be compiled, but I am not
happy with that. Could someone can tell me how to remove the _MBCS?
On 2013-02-20 14:35, Patrick Johnmeyer wrote:
Did you try remove_definitions?
Still I'm surprised that in your case, add_definitions(-D_UNICODE) does
not automatically remove the definition of _MBCS. Do you even have _MBCS
for a simple CMakeLists.txt as follows?
# CMakeLists.txt
project( MyCMakeMfcUnicodeApp )
cmake_minimum_required(VERSION 2.8)
set(CMAKE_MFC_FLAG 2)
add_definitions(-D_UNICODE)
add_executable(${PROJECT_NAME} MySourceFile.cpp)
Having the following MySourceFile.cpp:
// MySourceFile.cpp
#ifdef _MBCS
# error _MBCS should not be defined!
#endif
Kind regards,
Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
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/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio Generator: Unable to show property page for custom build tool
Michael Guerrero wrote: Hi, I’ve been experimenting with using Visual Studio’s “Custom Build Tool” per cpp file to perform some specialized operations. However, the property page is not visible (not editable) when I generate a project with cmake. To see what this looks like, see here: http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/496e301c-de2e-49bf-bbfa-ea8de335a0a5 To reproduce: 1)Generate a c++ project for visual studio (I’m using vs2010) 2)Right click a .cpp file in the solution and go to properties 3)Under Configuration Properties/General, change “Item Type” to “Custom Build Tool” 4)Click Apply 5)Select Configuration Properties / Custom Build Tool / General I’ve attempted to hand edit the solution and project files to determine what is causing this but nothing I removed seemed to have any affect. Any ideas on how to fix this or where to look? Please have a look at the following issue that I reported last year: 0012570: VS10 property pages for single source file gone, http://public.kitware.com/Bug/view.php?id=12570 That's the issue, isn't it? I posted the following workaround at https://connect.microsoft.com/VisualStudio/feedback/details/635294/using-absolute-path-in-clcompile-item-prevents-property-pages-from-showing : Suppose the .vcxproj file is located at drive 'D:'. Now associate 'D:\' with a new (unused) drive letter, for example 'V:', using cmd.exe: subst V: D:\ Now open the project via drive 'V:', instead of drive 'D:'. And guess what, Visual Studio 2010 allows viewing the C/C++ properties of individual source files! HTH, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] FindDCMTK Not setting up DCMTK_INCLUDE_DIRECTORIES Correctly?
On 2011-11-29 18:19, kent williams wrote: While I'm whining -- FindDCMTK.cmake doesn't include liboflog.a in DCMTK_LIBRARIES either. Thomas Sondergaard wrote: New in dcmtk-3.6.0, I think. We need to file a bug against FindDCMTK.cmake to have it find that library too. FYI, Dan Thill did so already: 0012324: FindDCMTK: Does not fully support DCMTK 3.6.0 http://public.kitware.com/Bug/view.php?id=12324 Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMAKE_RUNTIME_OUTPUT_DIRECTORY best practice for Windows and Visual Studio
Mateusz Loskot wrote:
I have a CMake-based project which builds several shared libraries and
executables.
There are various run-time dependencies between those shared libraries
and executables.
On Windows, I use Visual Studio for development, so I have
CMake-generated .sln with projects. loaded into the IDE. I build.
Then, I'd like to run one
of executables
(e.g. test.exe) which links against the DLLs also built by the
project. Obviously, it is necessary to deal with the run-time search
path.
At the moment, I simplify things by outputting all .exe and .dll
binaries to common directory, so programs can find required DLLs:
set(MYPRJOUTDIR ${PROJECT_BINARY_DIR}/bin/${CMAKE_BUILD_TYPE})
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${MYPRJOUTDIR})
This is also required to launch such executables under debugger.
However, I have heard opinions it is some kind of a hack unnatural to
CMake.
On Linux, I do the same, but I imagine I could make use of rpath [1]
as CMake provides some degree of support in this area [2].
On Windows, there is no such concept as rpath. Isolated Applications
[3]
seems to be the closest idea available there.
Is it a good idea to have all-in-one CMAKE_RUNTIME_OUTPUT_DIRECTORY?
Is there any CMake best practice for dealing with run-time search path
on Windows?
For example, automatically setting PATH in project
- Configuration Properties - Debugging - Environment.
[1] http://en.wikipedia.org/wiki/Rpath
[2] http://www.vtk.org/Wiki/CMake_RPATH_handling
[3] http://msdn.microsoft.com/en-us/library/aa375190%28VS.85%29.aspx
On Windows, it looks fine to me to have all the DLL's built by the project
together with the executable that links against them, in one and the same
CMAKE_RUNTIME_OUTPUT_DIRECTORY. The alternative of setting the PATH looks
less reliable to me, because the PATH may easily be overruled by other
locations (current directory, system directory or Windows directory),
depending on that rather complicated Dynamic-Link Library Search Order
thing, http://msdn.microsoft.com/en-us/site/ms682586 And eventually I guess
you don't want your application to depend on the PATH at the end user
machine. However, I haven't yet tried to build an isolated application
according to your reference [3]
(http://msdn.microsoft.com/en-us/library/aa375190%28VS.85%29.aspx). Would
you recommend doing so?
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Scientific programmer at LKEB, Leiden University Medical Center
--
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/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6
Update: I think users can work around this issue (#12570, empty property pages in VS10), by having the directory where to build the binaries on a separate drive (different from the drive that has the source files). Please let me know if you think that's not a good idea! Or if it does not work on your VS10 installation! - Original Message - From: Niels Dekker - address until 2014 To: cmake at cmake.org Sent: Thursday, November 10, 2011 17:29 Subject: Re: [CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6 Thanks for your feedback so far on this subject. I have just reported the issue: 0012570: VS10 property pages for single source file gone http://public.kitware.com/Bug/view.php?id=12570 If you have any more comment or suggestion, please feel free to add a note to the report! A patch is highly appreciated, of course :-) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6
Update: I think users can work around this issue (#12570, empty property pages in VS10), by having the directory where to build the binaries on a separate drive (different from the drive that has the source files). Mateusz Loskot wrote: Separate drive may not be an option for some/many. I, for instance, don't use partitions, but I use CMakeas as main builder for my projects. In order to work around http://public.kitware.com/Bug/view.php?id=12570 I think it should be sufficient to have a different drive *letter* when specifying where to build the binaries than the drive letter(s) of the path names of the source files. So I guess one might work around this issue by mapping a new drive letter to the build/bin directory, even while this directory might be located at the same physical drive as the source files. Right? Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6
In order to work around http://public.kitware.com/Bug/view.php?id=12570 I think it should be sufficient to have a different drive *letter* when specifying where to build the binaries than the drive letter(s) of the path names of the source files. John Drescher wrote: You could also probably use the subst command to substitute the root drive. Thanks, John. My build/bin directory is at D:\Build. When I do 'subst B: D:\', and open a VS10 .sln file from B:\Build, Visual Studio 2010 allows me to view the C/C++ properties of individual source files. Cool! I think I'll add 'subst B: D:\' to my system startup :-) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6
When Visual Studio 10 vcxproj files are generated by CMake 2.8.5 or 2.8.6, it is typically impossible to view the C/C++ properties of a single source file. CMake 2.8.0 to 2.8.4 do not seem to have this issue. It looks like the issue is caused by the fact that CMake 2.8.5 started storing the absolute path names of the source files (even when CMAKE_USE_RELATIVE_PATHS is ON). Is that a known issue? Visual Studio 10 does not allow viewing the C/C++ properties of source files that are listed by their absolute path names. See VS10 bug report 635294, Using absolute path in ClCompile item prevents property pages from showing, by Niels M Hansen, 1/9/2011: https://connect.microsoft.com/VisualStudio/feedback/details/635294/using-absolute-path-in-clcompile-item-prevents-property-pages-from-showing However, it seems like Visual Studio 10 *does* correctly support absolute path names *without* drive letter! Would it be possible for CMake to write the source file names *without* the drive letter, when it generates Visual Studio 10 vcxproj files? (Especially when the generated vcxproj files are located at the same drive as the source files.) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio 10 property pages for single source file gone with CMake 2.8.5 and 2.8.6
Thanks for your feedback so far on this subject. I have just reported the issue: 0012570: VS10 property pages for single source file gone http://public.kitware.com/Bug/view.php?id=12570 If you have any more comment or suggestion, please feel free to add a note to the report! A patch is highly appreciated, of course :-) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Shouldn't CMAKE_VERBOSE_MAKEFILE add SuppressStartupBannerfalse/... to VS 2010 vcxproj files?
Update: I locally fixed CMake's support for CMAKE_VERBOSE_MAKEFILE on Visual Studio 10 (or higher), and submitted a bug report: 0012504: Fix CMAKE_VERBOSE_MAKEFILE for Visual Studio 10 vcxproj files http://public.kitware.com/Bug/view.php?id=12504 Committed by Brad King: http://cmake.org/gitweb?p=cmake.git;h=25116a3c Thank you, Brad! Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Shouldn't CMAKE_VERBOSE_MAKEFILE add SuppressStartupBannerfalse/... to VS 2010 vcxproj files?
Update: I locally fixed CMake's support for CMAKE_VERBOSE_MAKEFILE on Visual Studio 10 (or higher), and submitted a bug report: 0012504: Fix CMAKE_VERBOSE_MAKEFILE for Visual Studio 10 vcxproj files http://public.kitware.com/Bug/view.php?id=12504 It seems to me that only a few lines of code in cmVisualStudioGeneratorOptions::SetVerboseMakefile should be changed. I hope the fix can be included with the next release. I wrote on 20 September 2010: When I choose Visual Studio 9 (MSVC 2008) as generator, switching on CMAKE_VERBOSE_MAKEFILE causes an extra line in the generated vcproj file, saying: SuppressStartupBanner=FALSE However, when I choose Visual Studio 10 (MSVC 2010), switching on CMAKE_VERBOSE_MAKEFILE does not seem to have an effect. Right? I would have liked to have the following line added to section ClCompile of the generated vcxproj file: SuppressStartupBannerfalse/SuppressStartupBanner Doing so would trigger the compiler to print its commandline arguments onto the output stream or output window, while it is compiling. Which I find pretty helpful! Note that the fix I'm proposing now at public.kitware.com/Bug/view.php?id=12504 generates: SuppressStartupBanner/SuppressStartupBanner This fix does *not* trigger those annoying D9035 compiler warnings (option 'nologo-' has been deprecated). :-) Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center -- 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Bug fix requests for the *next* release of CMake...
http://public.kitware.com/Bug/view.php?id=12323 (FindDCMTK cannot find all includes for MSVC build of DCMTK, by Dan Thill) See also my note: http://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=12323#bugnotes Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center ___ 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Shouldn't CMAKE_VERBOSE_MAKEFILE add SuppressStartupBannerfalse/... to VS 2010 vcxproj files?
When I choose Visual Studio 9 (MSVC 2008) as generator, switching on CMAKE_VERBOSE_MAKEFILE causes an extra line in the generated vcproj file, saying: SuppressStartupBanner=FALSE However, when I choose Visual Studio 10 (MSVC 2010), switching on CMAKE_VERBOSE_MAKEFILE does not seem to have an effect. Right? I would have liked to have the following line added to section ClCompile of the generated vcxproj file: SuppressStartupBannerfalse/SuppressStartupBanner Doing so would trigger the compiler to print its commandline arguments onto the output stream or output window, while it is compiling. Which I find pretty helpful! FYI, I'm using cmake-gui 2.8.5. Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center ___ 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/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
