Can you attach that project? I'll test it out under similar conditions.
Are you using the free version of visual studio?
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Johannes Sasongko
Sent: Thursday, March 01, 2012 9:
you can import those properties into variables at
the parent scope.
Anyway, just a thought..
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
François Mauger
Sent: Thursday, February 23, 2012 6:11 PM
To: Jean-Christophe Fillio
g/Bug/print_bug_page.php?bug_id=9742 )
We used the patch titled:
0001-ms-external-project-.NET-project-support-GUID-fixed.patch
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Anders Backman
Sent: Tuesday, February 21, 2012 9:55 AM
To: cmake
Su
).
Aaron Meadows
From: Kevin Schmidt [mailto:ke...@eyesopen.com]
Sent: Tuesday, February 21, 2012 8:26 AM
To: Meadows, Aaron C.; cmake@cmake.org
Subject: RE: [CMake] Shared intermediary files
Yes, for clarity, we do generate the files at build time, not cmake
time.
Kevin
From
time.
Someone with more experience may be able to jump in hear and give a
better answer..
Aaron Meadows
From: Kevin Schmidt [mailto:ke...@eyesopen.com]
Sent: Tuesday, February 21, 2012 8:09 AM
To: Meadows, Aaron C.; cmake@cmake.org
Subject: RE: [CMake] Shared intermediary files
them, so they are all building together in
one project (i.e. Visual Studio Solution)?
Or
Doing something completely different?
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Kevin Schmidt
Sent: Monday, February 20, 2012 3:07 PM
To: cmake
7;etc', which seems wrong.. not sure why
that would have happened. I'm using CMake 2.8.7 on Windows 7. I wonder
if there is something else that is a problem. What version of CMake are
you using?
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org]
I would second that sentiment. We had more luck with writing a script
to generate CMakeLists.txt file from our source tree and knowledge of
what we wanted plus hand tuning the primary CMakeLists.txt file.
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun
ing else instead of a + in your
target name.
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Kozlovskiy, Alexey
Sent: Tuesday, February 14, 2012 5:38 AM
To: cmake@cmake.org
Subject: [CMake] $ in the add_custom_command()
Hi,
If the project
I think Eric's notion of creating a branch would be the way to go. An
alternative (if you're on an OS supporting it) would be to create the
hierarchy of files as symlinks to the actual files. You could surely
create a script to automate this.
Aaron Meadows
-Original Message
That's a nice method too. I suppose the hard coding wouldn't matter in a
UnitTest.
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Michael Jackson
Sent: Friday, February 10, 2012 10:37 AM
To: CMake ML
Subject:
any copies of identical data for each different
configuration type.
Hope that helps!
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Eric Noulard
Sent: Friday, February 10, 2012 2:42 AM
To: Stefan Fendt
Cc: cmake@cmake.org
S
I went through the slides; pretty good introduction-intermediate presentation.
I'm forwarding it to all the teams I work with here!
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Eric Noulard
Sent: Thursday, Februa
uilding C object CMakeFiles/main.dir/main.c.obj
main.c
Linking C executable main.exe
[100%] Built target main
c:\dev2\TestProgs\CMake_Rebuild\b>main.exe
1
-8<-
---
One interesting difference I noticed was that when I went
Ah, that makes sense. Wonder how hard it would be to add a
Pseudo-target to CMake for the targets it will build, and allow the
scripts to set some properties on them which would be imported later as
they are created...
Aaron Meadows
From: david_bjorn...@agilent.com [mailto:david_bjorn
I wonder if you could do something like:
set_target_properties(INSTALL PROPERTIES EXCLUDE_FROM_DEFAULT_BUILD 0
)
Aaron Meadows
From: david_bjorn...@agilent.com [mailto:david_bjorn...@agilent.com]
Sent: Wednesday, February 08, 2012 9:44 AM
To: Meadows, Aaron C.; cmake@cmake.org
uldn't want my build to automatically install all the time, which is
probably why the INSTALL project is excluded by default.). Depending on
what you are doing, you might want that auto install behavior to only be
tied to a "Release" build, or possibly introduce and "Release a
_varName} ${_value})
foreach(_arg IN LISTS ARGN)
set(_desc "${_desc} ${_arg}")
endforeach()
set(${_varName} "${_outvar}" CACHE ${_type} "${_desc}")
endfunction(CheckAndAppendCache)
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun..
ot;)
add_executable(TestExe main.cpp)
Here is the relevant difference in the generated TestExe.vcxproj:
87c87
< EditAndContinue
---
> ProgramDatabase
Aaron Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Robert Dailey
Oops! Found a newer message from you regarding what I need to do on the
patch.. I'll get cracking on that!
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
Sent: Friday, February 03, 2012 8:08 AM
To: da
d
debug. The global property DEBUG_CONFIGURATIONS was not populated by default
(which might make sense..) so I had to do that.
I think that about sums it up. Hopefully that's useful to someone. If you
think there's a better way to handle this, I'm happy to discuss it!
Aaron Meadows
Hi David,
I know this is a fairly old bug fix by internet standards. I was
delayed from getting any further on it by my day job...
What do I still need to do to get this pushed in? Thanks!
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org
${CMAKE_CURRENT_LIST_DIR}/file4.cpp
)
#[...]
/foo/foo_test/CMakeLists.txt
#[...]
add_executable(foo_test ${fooTestFiles} ${FilesToIncludeInTestExe} )
#[...]
Some other alteratives might be to set a Global or target property in
the parent CMakeLists.txt and read it in the child one.
Aaron Meadows
arantee it only runs with VS?
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
Sent: Tuesday, September 06, 2011 3:18 PM
To: David Cole
Cc: cmake@cmake.org
Subject: Re: [CMake] Bug #12189
Sounds good. I beli
ng to document
_SBCS there, but was unable to find it in the documentation. If you want to
point me to the right location to add documentation, I'm happy to write some.
(I can write some for _UNICODE as well, if you like.)
Aaron Meadows
-Original Message-
From: David Cole [mail
I'm happy to assist in any way I can. Where do I need to add a test? Also,
where would it be appropriate to document this?
Aaron Meadows
-Original Message-
From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, August 31, 2011 11:02 AM
To: Meadows, Aaron C.
Cc:
Any of you CMakers want to comment on this bug and patch? I'd like to
be able to switch my company back to the public version of CMake instead
of compiling my own flavor every time there is a release...
Aaron Meadows
From: Meadows, Aaron C.
Sent: Thursday, June 23, 2011 2:23
Ah, so does that mean that it is escaping the space, similar to --username\
MyUserName ?
Aaron Meadows
-Original Message-
From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, July 13, 2011 4:09 PM
To: Meadows, Aaron C.
Cc: cmake@cmake.org
Subject: Re: [CMake] Issues with
That works! Thanks!
Any idea why the other way was causing issues?
Aaron Meadows
-Original Message-
From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, July 13, 2011 1:06 PM
To: Meadows, Aaron C.
Cc: cmake@cmake.org
Subject: Re: [CMake] Issues with execute_process and
That's not what I'm using it for, but thanks for the suggestion.
Aaron Meadows
From: Jean-Christophe Fillion-Robin [mailto:jchris.filli...@kitware.com]
Sent: Wednesday, July 13, 2011 1:49 PM
To: David Cole
Cc: Meadows, Aaron C.; cmake@cmake.org
Subject: Re: [CMake] I
mmands to a file and execute that. (in
which case you'll get svn: '.' is not a working copy and not the invalid
option issue)
Thanks for any help you can provide!
Aaron Meadows
Software Engineer
Thomson Reuters
Phone: 314.468.3530
Mobile: 636.
to control
stuff.
_LIBRARY Name of Library. A User may set
this and _INCLUDE_DIR to ignore to force non-use of .
__LIBRARY Name of library that is part of
the system. It may or may not be required to use .
_INCLUDE_DIR Where to find xxx.h, etc.
(_INCLUDE
here to find xxx.h, etc.
(_INCLUDE_PATH was considered bad because a path includes an
actual filename.)
__INCLUDE_DIR Where to find xxx_.h, etc.
Aaron Meadows
Software Engineer
Thomson Reuters
Phone: 314.468.3530
Mobile: 636.541.6139
aaron.mead...@thomsonreuters.com
thomsonreuters.com
___
--non-interactive log -r BASE ${dir}
OUTPUT_VARIABLE ${prefix}_LAST_CHANGED_LOG
ERROR_VARIABLE Subversion_svn_log_error
RESULT_VARIABLE Subversion_svn_log_result
Aaron Meadows
Software Engineer
Thomson Reuters
Phone: 314.468.3530
Mobile: 636.541.6139
aaron.mead...@thomsonreuter
is still available and
otherwise CharacterSet="0". In that case the user can remove the _MBCS
macro by remove_definitions and select this way the SBCS. If the user
adds _UNICODE by add_definitions CharacterSet="1" should be selected and
the conflicting _MBCS macro
So, you are manually running your tests, for example, the
'test_julian.exe' or 'testcpp.exe'? Running them from a command prompt
gives you that same error about the application has failed to start?
And the name of the dll's exactly match? And you have tried copying the
.dll into the same director
Hope it helps. I’m not completely clear on what you are talking about with the
overloading. Are you saying you have the same function defined in multiple
static libraries?
Aaron C. Meadows
From: Leila Baghdadi [mailto:baghd...@phenogenomics.ca]
Sent: Thursday, June 23, 2011 1:55 PM
To: M
Oh, sorry.. I missunderstood about the line 76. =D
Ok, looking at your CMakeLists.txt, I see the ADD_SUBDIRECTORY(libctsim). I’m
assuming there is a CMakeLists.txt in there which does the ADD_LIBRARY. The
ADD_SUBDIRECTORY() calls are before you’re doing a bunch of ADD_DEFINITIONS().
The
Unless "ImageFileArrayConst" is a typedef for "double **", there is not
an ImageFile::statistics() function which takes a double** as the first
parameter. (Line 288 and 296 have the two versions of
ImageFile::statistics())
If you look in views.cpp at the function ImageFileView::OnProperties()
f
Can you post your CMakeLists.txt? Did you get different errors for each
of the 3 solutions you tried, or were they all the same error? What was
the exception code?
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Stephen Torri
Sent: Wednesday, Jun
This sounds like poorly formed c++, not a CMake issue. Can you include
your CMakeLists.txt, a copy of the error, and possibly a simple example
which shows the problem?
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Leila Baghdadi
Sent: Wednesday,
I use this exact code to determine 64bit vs. 32bit for visual studio
2005/2008/2010.
Aaron C. Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Rolf Eike Beer
Sent: Thursday, June 23, 2011 1:08 AM
To: cmake@cmake.org
Subject: Re: [CMak
This may be an issue with CMake being 32bit. 32bit programs on 64bit
windows get run in a sort of sandbox (you probably already know this, so
don't be offended if you do!). To a 32bit program on 64bit windows, I
believe the c:/windows/system32 directory is secretly the
c:/windows/syswow64 directo
ot;0". In that case the user can remove the _MBCS
macro by remove_definitions and select this way the SBCS. If the user
adds _UNICODE by add_definitions CharacterSet="1" should be selected and
the conflicting _MBCS macro must be deleted by the code generator.
-
ot;0". In that case the user can remove the _MBCS
macro by remove_definitions and select this way the SBCS. If the user
adds _UNICODE by add_definitions CharacterSet="1" should be selected and
the conflicting _MBCS macro must be deleted by the code generator.
---
Looking at FindCurses.cmake, it looks like it will prefer libcurses if
it finds it (line 33). Specifically, it will try to determine if
libcurses provides ncurses by seeing if libcurses contians the function
wsyncup() (line 60). Here is the logic that does this (lines 47-71):
# Not sure the l
string(REGEX MATCH "Build Engine Version
[0-9]+.[0-9]+.[0-9]+.[0-9]+"
+_cl_version "${_output}")
+endif()
+
if(_cl_version)
string(REGEX MATCHALL "[0-9]+"
_cl_version_l
>-Original Message-
>From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Michael Wild
>Sent: Monday, May 23, 2011 9:12 AM
>To: cmake@cmake.org
>Subject: Re: [CMake] Newbie question: Static linking
>
>On 05/23/2011 03:25 PM, Sanatan Rai wrote:
>> On 23 May 2011 13:38,
48 matches
Mail list logo
