On Tue, Nov 8, 2016 at 10:28 AM, wrote:
>
>
> - On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org
> wrote:
>
>> On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote:
>>>
>>> On 11/03/2016 06:04 PM, John Drescher wrote:
>>>
I opened a project in cmake-gui using the open project button from a
vc 2010 build of a project. The open project opened the project in
Visual Studio 2010. Later I opened the same project but a different
build tree for Visual Studio 2013 CMake-gui had all of the correct
information for the Visual S
On Fri, Oct 9, 2015 at 9:53 AM, Laura Médioni wrote:
> Hi,
>
> I am facing a problem with CMake 3.4 under Windows.
> My CMake project is using Qt. Recently I uninstalled Qt and reinstalled it.
> Since then, the previous Qt install keeps on appearing in the
> CMakeCache.txt, leading to link edition
> I have been successful with
>
> Src\build.32 and src\build.64 so that on svn update effects both.
>
> The problem, for my automated build flow, I was hoping to make a mix, 32/64
> installer.. it’s a lot harder to do with two completely separate build trees
> :(
For this I just make separate in
> However, once the solution is created, does the "path" of the shell matter
> at all?
No.
John
--
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 mo
On Fri, Feb 27, 2015 at 10:44 AM, Scott Aron Bloom
wrote:
> Is it possible with cmake, to build a VS 2013, win32 and win64 vsproj
> solution file set?
>
> If not, I understand, then I have a follow on question..
>
No create 2 independent trees. I keep the source in a separate tree
also. For examp
On Thu, Jan 1, 2015 at 11:27 PM, Scott Aron Bloom
wrote:
> For windows Visual Studio using CMake with google test, one of the
> complaints my team has, is the project name “RUN_TESTS” gets lost in the
> numerous projects.
I am not sure about renaming that however I find it helpful to
organize my
> does CMake run on 64-bit OS (e.g. Ubuntu 14.10 64-bit) without problems
> or are there some workarounds necessary to get it run? If so, is there a
> description available?
>
I have not had any real issue with cmake (32 or 64 bit binary) on 64
bit linux or windows.
John
--
Powered by www.kitwa
Did you try runing cmake-gui from a VisualStudio 2010 x64 command prompt?
John
On Tue, Sep 23, 2014 at 1:08 PM, lanhz wrote:
> Hi,
>
> I'm trying use CMake to build VTK, but got error as below. I searched the
> internet and tried many ways suggested, but they didn't work. The OS is
> Windows 7 w
> So CMAKE can't control the options int he *.user files I guess :-\? Would a
> potential workaround be to find a command line tool that can edit these and
> run it as a post-build script?
CMake gives you the functionality needed to edit these via your own
script. I mean reading and writing files
On Fri, Jul 11, 2014 at 10:33 AM, Edward Diener
wrote:
> Shouldn't there be a way to change the current generator in the CMake GUI ?
> It seems like I can only do this if I choose a new "Where to build the
> binaries" path. But what if I just want to change the current generator to
> something els
> Ok, run cmake -G "MinGW Makefiles"
> -DCMAKE_C_COMPILER=/c/mingw-w64-4.9.0/mingw64/bin
> I got this error:
> CMake Error: the source directory does not appear to contain
> CMakeLists.txt
>
> What I am missing?
>
You are not passing the folder of the source.
John
--
Powered by www.kitware
On Thu, May 1, 2014 at 2:16 PM, Matthew Woehlke
wrote:
> On 2014-05-01 13:35, John Drescher wrote:
>>>
>>> I thought they probably were. My question was really if the behaviour
>>> that
>>> results from that was desirable. I can't see any reason why
On Thu, May 1, 2014 at 1:54 PM, Glenn Coombs wrote:
> What I am saying is that project("foo") should internally execute the
> equivalent of set(foo_SOURCE_DIR "/path/to/source") rather than set(foo
> "/path/to/source" CACHE STRING). That way it would fail on every run if you
> referenced a projec
> I thought they probably were. My question was really if the behaviour that
> results from that was desirable. I can't see any reason why they should be
> cached as they aren't user configurable variables. Would it break anything
> badly if they were not stored in the cache ? It would result i
Is there some option to export automatically some methods without using
__declspec(dllexport)?
>>
>> No. There are workarounds like in
>> http://stackoverflow.com/questions/225432/export-all-symbols-when-creating-a-dll
>> but it's too much work.
>> Basically you want to define a macro tha
> Why not just write your own batch ('buildit.bat') file that does:
>
>call vcvarsall.bat
>nmake
>
> (or whatever the command to build in the VS command prompt is...)
>
> And then your command to build is:
>
>C:/full/path/to/buildit.bat
>
> It's presumably in a Windows-specific chunk of
On Sat, Dec 28, 2013 at 9:05 AM, Ansis Māliņš wrote:
> Yes, I'm using Visual Studio 11 (aka 2012) generator.
Did you try running cmake-gui from a Visual Studio 2012 x64 Command
Prompt so that the compiler environment variables are set?
John
--
Powered by www.kitware.com
Please keep messages on
On Sat, Dec 28, 2013 at 8:35 AM, Ansis Māliņš wrote:
> The minimal CMakeLists.txt with content
>
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
> PROJECT(CMakeTest)
>
> on CMake 2.8.12.1 on Windows 7 64 bit with Visual Studio 2012 produces the
> result
>
> CMake Error at C:/Program Files (x86)/CMake
> 2.8/
> +1 for updating cmake-gui to work equally to ccmake
>
> But my opinion regarding CMAKE_MODULE_PATH is different. The problem is that
> alot of the default find-modules don't work because the dependency is not in
> the location where the find-module expects it. Currently there are only two
> worka
On Fri, Oct 4, 2013 at 10:34 AM, John Drescher wrote:
>
> Deleting cache and reconfiguring doesn't help... I get the same errors
>> repeatedly! Why does it say that it can't recognize the C and CXX
>> compilers? Do you think I should try with some vanilla Visual St
>
> Deleting cache and reconfiguring doesn't help... I get the same errors
> repeatedly! Why does it say that it can't recognize the C and CXX
> compilers? Do you think I should try with some vanilla Visual Studio 12 as
> opposed to the "Ultimate" I got from MS?
>
>
>
Wait a minute. You said Visual
> Configuration of VTK with cmake-gui was ok. Don't know how it was fixed.
>
> Does it help if I send the output of the minimal test case?
>
I suspect deleting the cache in cmake-gui then running cmake-gui from
the windows shortcut will break it again.
BTW, I usually run cmake-gui from a visual s
> Any idea who has subscribed pir...@teamspeakusa.com to this list?
>
I have seen this spam on multiple email lists not just cmake. This is
getting very annoying.
John
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
K
On Thu, May 30, 2013 at 1:53 PM, Michael Jackson
wrote:
> I am trying to group some of my targets for my Visual Studio users and I am
> using the following code:
>
> #
> add_executable(StructArrayTest ${DREAM3DTest_SOURCE_DIR}/StructArrayTest.cpp)
> target_link_libraries(StructArrayTest
On Tue, May 28, 2013 at 10:16 AM, Zamir Khan wrote:
> We have a project where multiple modules rely on ITK. Most modules have been
> upgraded to ITK 4.31, but one still relies on ITK 3.20 and it would take a
> significant effort to upgrade it. In the meantime, is there a way for us to
> keep these
> Qt 4.5.0 or greater not found. Please check the QT_QMAKE_EXECUTABLE
> variable.
Did you follow the above advice?
I mean go in cmake-gui and make sure this variable contains the path
to the qmake executable.
John
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:
> It states that...
>
> "To start work on a custom NSIS script, simply create a file (or copy) into
> your module path (e.g. CPACK_MODULE_PATH) called NSIS.template.in."
>
> Checking the cmake documentation, there is no predefined variable named
> "CPACK_MODULE_PATH".
>
> I could find a "NSIS.templ
On Thu, May 2, 2013 at 3:35 PM, Laszlo Papp wrote:
> Hi,
>
> I tried to install the following redistributable package after seeing the
> issue below, but it did not help, not even after a reboot.
>
> Got a clue?
It looks like you were not supposed to install the redistributable but
to put it some
On Wed, Apr 24, 2013 at 3:31 PM, Gabriel Santiago
wrote:
> Actually my CMake is 2.8.7, ITK is 3.20.1 and QT is the latest...
>
I believe this file should work. Although I really do not have any
more time to help if it does not.
project(test)
cmake_minimum_required(VERSION 2.8 FATAL_ERROR)
find
On Wed, Apr 24, 2013 at 3:13 PM, Gabriel Santiago
wrote:
> I did it, but still not working... Getting the same error message as before.
>
Are you using very old versions of Qt, ITK and CMake? I ask because of this line
cmake_minimum_required(VERSION 2.4.0)
The current version of CMake is 2.8.10
> I put all the folders in the CMakeLists.txt, but still not working...
>
> TARGET_LINK_LIBRARIES(test ITKCommon ITKIO ITKBasicFilters ITKAlgorithms
> ITKNumerics ITKSpatialObjetcs ITKReview ITKPatented ${QT_LIBRARIES})
>
Again the missing header files problem has nothing at all to do with
linking
> I just did what you said, but still getting the same error message...
That is expected. The problem you just mentioned is not a linking
problem. You are missing several includes in your CMakeLists.txt
John
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.k
On Wed, Apr 24, 2013 at 2:06 PM, Jean-Christophe Fillion-Robin
wrote:
>
> Hi,
>
> What about adding: find_package(ITK REQUIRED)
>
> If you use ITKv4, you could change:
> TARGET_LINK_LIBRARIES(test ITKCommon ITKIO ITKBasicFilters)
> into
> TARGET_LINK_LIBRARIES(test ${ITK_LIBRARIES})
>
> As a b
> project(test)
>
> cmake_minimum_required(VERSION 2.4.0)
>
> find_package(Qt4 REQUIRED)
>
> SET(qtproject_UIS mainwindow.ui)
>
> QT4_WRAP_UI(qtproject_UIS_H ${qtproject_UIS})
>
> include_directories(${CMAKE_
> CURRENT_BINARY_DIR})
>
> add_executable(test ${qtproject_SRCS} ${qtproject_UIS_H} main.c
> The purpose of -rc releases is for people to try them and report back
> any regressions for building their projects. John, did you report
> this anywhere earlier that we missed?
>
I did not. Sorry. I wanted to try to better track down the cause. I
initially thought it was based on having more t
> Here it is:
> #---
> project(test)
>
> cmake_minimum_required(VERSION 2.4.0)
>
> find_package(Qt4 REQUIRED)
>
> SET(qtproject_UIS mainwindow.ui)
>
> QT4_WRAP_UI(qtproject_UIS_H ${qtproject_UIS})
>
> include_directories(${CMAKE_CURRENT_BINARY_DIR})
>
> add_executable(test ${qtproject_SRCS} ${qtpro
> I installed it and it ran one time and I didn't see the error, but it's
> intermittent so that's not definitive. Unfortunately one of my cmake
> files failed (later on; this is a cmake file from a smaller
> sub-project):
>
> CMake Error at CMakeLists.txt:190 (TARGET_LINK_LIBRARIES):
>
> I already have CMake 2.8.1 installed. Sorry for not specifying that earlier.
> I also have installed the GIT repository version of VTK.
>
If CMake is not found then it is either not properly installed or not
in your path.
John
--
Powered by www.kitware.com
Visit other Kitware open-source proj
On Thu, Mar 21, 2013 at 10:20 AM, Martin Koller wrote:
> In my win project, when I use the visual studio generator (64bit), I always
> get the /D _MBCS flag in the compiler options
> (started with msbuild).
> When I generate Makefiles with the same project (JOM NMakefiles), _MBCS is
> not define
> I use cmake 2.8.10 on windows.
>
>
>
> I would like to build several targets with cmake --build so the
> underlying build tool to do parallel jobs.
>
>
>
> Currently it only seems to be possible to build one target at a time, using
> --target .
> (http://www.cmake.org/cmake/help/v2.8.10/cmake.h
On Tue, Mar 5, 2013 at 10:58 AM, David Cole wrote:
> Is your VS 2010 up to date with respect to available service packs?
>
I was going to ask that because Visual Studio 2010 RTM has a nasty
optimizer bug that caused me some pain in the past. SP1 fixed that
issue.
John
--
Powered by www.kitware
On Fri, Mar 1, 2013 at 10:52 AM, John Drescher wrote:
>> If CMake developers say that the code is simply not structured like that, or
>> it is too much work to rewrite these parts (and a few others that might
>> depend on it), then I leave this subject be and not bother again
> If CMake developers say that the code is simply not structured like that, or
> it is too much work to rewrite these parts (and a few others that might
> depend on it), then I leave this subject be and not bother again with it.
David led the CMake development for years.
John
--
Powered by www.k
On Thu, Feb 28, 2013 at 6:31 AM, John Drescher wrote:
>> There are multiple posts in multiple forums asking this question, so
>> naturally there is public need for this feature. How come CMake never aimed
>> at creating a solution for this? I suspect there is some great de
> There are multiple posts in multiple forums asking this question, so
> naturally there is public need for this feature. How come CMake never aimed
> at creating a solution for this? I suspect there is some great design issue
> that prevents implementing it in CMake. There are several platform and
On Thu, Feb 21, 2013 at 2:46 PM, Martin Koller wrote:
> Hi all,
>
> I found an old cmake bug entry (see below) for the problem I have:
>
> I downloaded and installed the 32bit cmake exe on a 64bit windows
> and wanted to build our project as 64bit executable. However in our
> cmake files (which ar
On Wed, Feb 20, 2013 at 2:07 PM, amitsuveer wrote:
> I am using cmake-2.8.10.2-win32-x86 and vtk-5.10.1.
>
> I am trying to configure VTK, I have installed Visual Studio 10 (not the
> express version, the full one along with SP1), with x64 support. However,
> when selecting Visual Studio 10 (for 3
> Thought I'd ping the CMake mailing lists one last time before I have to give
> up "david.c...@kitware.com"... ;-)
Thanks for all your hard work on this..
John
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please k
> Hey there. I created a bare minimum cmake project
>
>
>
> ADD_LIBRARY (foo foo.c)
>
>
>
> When I open that solution in VS2010 and right click on foo.c and select
> properties, the properties dialog comes up but when I try to view each
> property (C/C++ > General, Optimization, Preprocessor, etc…)
> The suggestion in the bug report looks somewhat reasonable to me, but then
> again, we don't actually create separate debug info, and the 'Release'
> configuration would be no different to the 'RelWithDebInfo' configuration,
> so it's sort of a 'lie'.
>
> The real need for it though is probably t
> I didn't try running any examples, but I also ported it to Qt 5. My patch
> for that is attached. John, the patch for older VTK versions should be
> similar if you wish to try it.
>
I will see what I can do this weekend.
Thanks,
John
--
Powered by www.kitware.com
Visit other Kitware open-sour
> The question is: what is the location of the make program?
>
> If I remember correctly, on Windows XP, I did not have to install MinGW to
> compile VTK. Just Visual Studio Express was required.
>
> Do I have to install MinGW?
Not unless you want to move your development to MinGW.
>Or is it prov
On Wed, Dec 12, 2012 at 4:03 AM, Benoît Thiébault wrote:
> Hi everyone,
>
> I sent this question on CMake mailing list a week ago and never had any
> answer.
>
> As it deals with compiling VTK, I'm thinking maybe some of you have a
> solution.
>
Can't you specify the location of the make program
> In VTK 5.10, there were some other configure time options (I'd have to go
> look them up or try it out) to control building the Qt-related bits...
>
In vtk-5.X you needed to enable VTK_USE_GUISUPPORT then that gave you
the ability to enable VTK_USE_QT
John
--
Powered by www.kitware.com
Visit
On Tue, Dec 11, 2012 at 2:24 PM, John Drescher wrote:
> My goal is to a specific definition to the Debug and RelWithDebInfo
> configurations for all targets in the project but not to the Release
> configuration when using VisualStudio. I believe that
> COMPILE_DEFINITIONS appears to
On Tue, Dec 11, 2012 at 12:02 PM, Stephen Kelly wrote:
> John Drescher wrote:
>
>>> I emailed before about reviewing Config files that are being shipped with
>>> Qt 5 and got great feedback:
>>>
>>>
> http://thread.gmane.org/gmane.comp.kde.devel.build
> A colleague mentioned that with the same setup he was getting the same
> error, and then installed SP1 for VS 2010 and things started working.
I also remember that Visual Studio 2012 RTM had an optimizer bug that
caused Qt applications to crash so the first thing I always do after
installing VS
> I emailed before about reviewing Config files that are being shipped with Qt
> 5 and got great feedback:
>
> http://thread.gmane.org/gmane.comp.kde.devel.buildsystem/7165/focus=41551
>
> Now that Qt 5 beta 2 is out, I'd like to ask for feedback again on anything
> that can still be changed befor
> Right, perhaps complex inter-project dependencies halt the processes.
I believe this is part of the reason. Projects like ITK with hundreds
of small utilities tend to utilize the cores after the dependent
libraries are built however my code that has very few utilities and
significantly more inte
On Tue, Nov 27, 2012 at 9:41 AM, Mateusz Loskot wrote:
> On 27 November 2012 14:23, John Drescher wrote:
>>
>> On Tue, Nov 27, 2012 at 7:21 AM, Michael Jackson
>> wrote:
>> >
>> >
>> > On Nov 27, 2012, at 12:46 AM, Titus von Boxberg wrote:
On Tue, Nov 27, 2012 at 7:21 AM, Michael Jackson
wrote:
>
>
> On Nov 27, 2012, at 12:46 AM, Titus von Boxberg wrote:
>
>> Am 27.11.2012 05:24, schrieb Michael Jackson:
>>> That will teach me to hit enter in GMail..
>>>
>>> My question is this: What is the magic CMake incantation to get Visual
>>>
> Thanks for your help。 but now i am in another trouble.
> In Windows，i am trying to build a shard library,It needs to link dynamic
> library and static library。
> when i want to link a dynamic library，it comes：
> (fatal error U1073：does not know how to generate "ACE.lib")
>
> AUX_SOURCE_DIR
> Having CMAKE_SYSTEM_PROCESSOR be "x86" for a 64-bit build is very
> inconvenient when detecting machine-dependent compiler flags, constructing
> directory names for outputs based on configuration, configuring third party
> search directories, etc. It's always possible to work around (among ot
> Except that you have CMAKE_SYSTEM_PROCESSOR == "x86" (event for "Win64"
> generators) in your CMake files along with all search paths which sometimes
> very inconvenient.
I am not sure that has ever caused me a problem on any of the 64 bit
applications I have written. The only problem I had with
> I noticed that there is cmake binary package for Windows x64. Should a
> 32-bit cmake (under syswow6432) be adequate for all cmake tasks? If
> not, what is the right way to build cmake for 64-bit. I tried building
> it on a 32-bit build server using the 64 bit generator (this build
> server routi
On Tue, Oct 2, 2012 at 9:11 AM, Arindam Mukherjee
wrote:
> Hi,
>
> I want to define a single variable in a top-level CMakeLists.txt and
> use it in multiple CMakeLists.txt in sub-directories to specify
> target_link_libraries for executables built in these subdirectories. I
> tried defining a cust
On Mon, Oct 1, 2012 at 4:35 PM, Arindam Mukherjee
wrote:
> Hi,
>
> I have a Windows XP build setup with Visual Studio 2008 SP1 and
> Windows SDK 6. I have set up a CMake project for a source base that is
> built on Linux, Solaris, AIX and Windows. So far I have managed to get
> the Windows 32-bit
On Tue, Sep 4, 2012 at 6:33 AM, Zein Salah wrote:
> Hi,
>
> Previously, i used to build fltk 1.1.7 with Cmake for VS2008 and
> everything (ITK, InsightApplication, etc.) worked fine.
>
> I try now to make the same using Cmake 2.8.9 for VS2010.
> Building FLTK 1.1.7 works fine (No error!). But Cma
On Mon, Sep 3, 2012 at 11:05 AM, Klaim - Joël Lamotte wrote:
> Hi,
>
> Is there any way in CMake to get a list of all binaries related to one
> target?
> What I mean is that assuming I have a target, say a library lib_a, that
> depends on lib_b and lib_c which are either SHARED or MODULE (so they
On Thu, Aug 23, 2012 at 4:55 PM, Robert Dailey wrote:
> I'm not sure if my eyes are playing tricks on me, but after upgrading
> to 2.8.9 I'm seeing EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH in
> my list of cache variables now, I don't remember seeing them before.
>
> Is this a feature? I didn
On Thu, Aug 23, 2012 at 11:39 AM, Jason T. Slack-Moehrle
wrote:
> A few questions on formatting the CMakeLists file.
>
> Is there sort of a "template" that everyone uses to ensure not
> overwriting options, etc?
>
> Second, when using commands like:
>
> SET( CORE_SOURCE_FILES "main.cpp" )
>
> can
> Is the separation between configuration & generation really necessary
> for cmake-gui? I ask because several of my co-workers are confused
> between the differences in the two, even though I explain it.
>
> Honestly there isn't really a reason that I can think of to do a
> configure without a gen
On Sun, Aug 12, 2012 at 10:33 AM, John Drescher wrote:
> On Sun, Aug 12, 2012 at 10:30 AM, Toronto Andrew
> wrote:
>> I get the following errors when trying to build my Qt project:
>>
>> CMake Error at C:/Program Files (x86)/CMake
>> 2.8/share/cmake-2.8/Modu
On Sun, Aug 12, 2012 at 10:30 AM, Toronto Andrew
wrote:
> I get the following errors when trying to build my Qt project:
>
> CMake Error at C:/Program Files (x86)/CMake
> 2.8/share/cmake-2.8/Modules/FindQt4.cmake:595 (MESSAGE):
> Could NOT find QtCore. Check
>
> And I need to manually point the
On Tue, Jul 31, 2012 at 2:54 PM, Toronto Andrew
wrote:
> Thank you John, this did work. I get the idea now, thank you.
>
> I have another concern though, that I hope I can be helped with though it's
> doesn't fall under the original problem.
>
> So I am using a project within my project: http://i.
On Tue, Jul 31, 2012 at 2:21 PM, Toronto Andrew
wrote:
> Include it using the flags? Like so:
>
>
> TARGET_LINK_LIBRARIES(CppSampleQt01 ${QT_LIBRARIES} SIMPLONLIB
> SIMPLONIMGPROC) ?
>
> Because when I did this, the libs were not found either.
>
I think it should be:
TARGET_LINK_LIBRARIES(CppSam
> The qt libraries are included in the target link flag (this project uses qt
> of course), however the two lib files that exist in the lib folder in the
> same directory are either not recognized. They draw up linker issues in the
> compiler, even though I can tell through the cmake gui that it do
> well this is created and doesn't exist from the beginning:
> _CPack_Packages/win32/ZIP/libhello-1.0.9
>
> when I try to go in and delete this folder by hand I can't. The libhello is
> locking up the hole thing. It just says I can't remove it and I have tried
> everything.
> I can create things in
> file cannot create directory:
> C:/JenkinsCI/jobs/te/workspace/_CPack_Packages/win32/ZIP/libhello-1.0.9
> /lib. Maybe need administrative privileges.
Does this folder exist? Can you create this using your user account?
John
--
Powered by www.kitware.com
Visit other Kitware open-source
On Thu, Jul 12, 2012 at 2:31 PM, Mateusz Loskot wrote:
> On 12 July 2012 18:44, Yixun Liu wrote:
>> BTW, do you know how to set CMakeList to make it produce a window-based
>> application rather than a console-based application?
>
http://www.cmake.org/pipermail/cmake/2008-March/020577.html
John
-
On Sun, Jun 24, 2012 at 5:57 AM, Heena Mahur wrote:
> Hey,I need to that what should i do in
> cmakelists.txt http://pastebin.com/raw.php?i=BGV9NAmQ since i am getting
> this error (target_link_libraries): Cannot specify link libraries for
> target "ptedit_1" which is not built by this proje
> I have a project that depends on 3rd party dll's (libxml2).
>
> Is there a 'best practice' to deal with associated files, .h, .lib .dll of
> such within a CMake project?
>
> My library needs to link to the 3rd party lib, and needs its dll for
> execution (obviously), so I feel the need for copyin
> I’ve
> had issues in the past trying to perform a configure command in CMake-gui
> when the buidl directory already existed..?
I do this all the time for years. No problems at all.
John
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensourc
> A good rule of thumb is to try just upgrading CMake and running it on
> existing build trees. It's obviously quicker than a re-configure from
> scratch.
>
> But then, before complaining about something not working, try it in a fresh
> build tree first, then if it's still wrong, complain. :-)
>
>
On Mon, Apr 23, 2012 at 1:46 PM, Robert Dailey wrote:
> I am wondering what a good rule of thumb is when upgrading CMake. Should I
> delete my cache after each upgrade? I'm on Windows.
> --
I never ever do that on windows. And I have done 100s of builds with
CMake and many upgrades since CMake 2.
> OK, but it does try to fill in the CMAKE_C_COMPILER value. What are you
> suggesting? That this is a bug or some kind of mistake on my part thinking
> that the value in CMAKE_C_COMPILER is somehow relevant for Visual Studio
> targets?
>
CMAKE_C_COMPILER is not used for Visual Studio targets
--
> I would have to say that I didn't dig into the QT4_WRAP_CPP macro at all. If
> I had I would have probably answered my own question. I will give you idea a
> shot and report back if it works or not. Thanks for the idea.
>
Please do so. I would be very interested in your findings on this one..
> I download the cmake-2.8.7-win32-x86.exe , but it failed when it works with
> visual studio 2008 win64 and give the message below:
>
> Check for working C compiler using: Visual Studio 9 2008 Win64
>
> Check for working C compiler using: Visual Studio 9 2008 Win64 -- broken
>
> CMake Error at C:/
On Thu, Mar 1, 2012 at 10:01 AM, Johannes Sasongko wrote:
>> Are you using CMake 2.8.7? If not, please upgrade and try with that
>> version. If there's still a problem after that, let us know.
>
>
> Yes, I'm using 2.8.7. I've tested it on a very simple project (essentially
> just a Hello World wit
> Ah yes you're right, last time I checked I didn't see them..
> Anyway my extra_commands don't appear anywhere in the nsi file, is that
> normal?
I can't help with that part. I do add components also executables with
shortcuts for my executables by setting the CPACK_PACKAGE_EXECUTABLES
variable.
> By the way, how do I see the actual paths NSI configuration that generates
> the final exe?
> It seems that if NSIS works the file used get all removed..
>
It does not get removed for me using Visual Studio 2010. All of the
NSIS stuff exists in a _CPack_Packages folder inside of the build
tree.
> 2. Do batch building. I do this option. Look at the cmake --build command
>
Here is an example of this for one of my current projects (not exactly
what I do but close enough):
rem configure
pushd .
cd X:\64Bit\VC.100\Qt\StudyManager
cmake X:/CMakeBased/Qt/StudyManager
popd
rem build the nsis p
> The SLN solution contains all possible build-types. The user just have to
> select which one they want (i.e. in Visual Studio, not cmake)
>
Continuing on this subject. The default configuration in Visual Studio
is Debug so that is why debug is selected.
There are many ways around this:
1. You
> but my point
> here is that we really need a CMake CookBook or snippet repository. I always
> hit the FAQ first, but that /explains/ when what a coder tends to need in
> that frame of mind is a living example.
Maybe some user committed examples in the wiki just like what has been
done for the vt
On Thu, Feb 23, 2012 at 10:33 PM, John Drescher wrote:
>> You probably want to do some type of file GLOBBING for that
>>
> Here is an example of file globbing (along with its pitfalls):
>
> http://www.cmake.org/pipermail/cmake/2010-September/039558.html
>
I am sorry. I
> You probably want to do some type of file GLOBBING for that
>
Here is an example of file globbing (along with its pitfalls):
http://www.cmake.org/pipermail/cmake/2010-September/039558.html
--
John M. Drescher
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:
On Thu, Feb 23, 2012 at 9:57 PM, Oliver Smith wrote:
> So it's late, and suddenly I find I can't remember how to configure cmake to
> compile any .xml file in a specific directory with an xml-to-header script
> we have. More importantly, I can't think of the right terms to find an
> answer, so I'v
On Thu, Feb 23, 2012 at 6:19 PM, Yang, Jinzhong wrote:
> Hi All,
>
>
>
> I was trying to configure InsightApplications in CMake with USE_FLTK turned
> on, but I continuously got the error message:
>
>
>
> CMake Error at CMakeLists.txt:128 (INCLUDE):
>
> include called with wrong number of argument
> Just to make you laugh I found the source of the problem.
> Apparently if you try to run an installer from a directory which is on a
> shared directory (with the virtualbox
> sharing) it just won't run :D
>
> Copying it somewhere else works perfectly, quite amazing issue.
>
Thanks for reporting
1 - 100 of 536 matches
Mail list logo
