Hi all,
I have problems with the following cmake build script:
find_program(CCP_EXECUTABLE cpp REQUIRED HINTS /opt/local/bin)
find_program(ASN1C_EXECUTABLE asn1c REQUIRED HINTS /opt/local/bin)
if(ASN1C_EXECUTABLE AND CCP_EXECUTABLE)
set(ASN1C_OUTPUT_DIR "${CMAKE_CURRENT_BINARY_DIR}")
###
Hi Brad,
Firstly, thanks for your attention and I really appreciate you're
working through the issue with me.
Thanks for your explanation of cmLocalGenerator::Convert.
My source tree roughly looks like this:
C:\dev\root\src\CMakeLists.txt -- root cmake lists file
C:\dev\root\src\build\ -- This is
Hi all,
After Brad’s feedbacks, I did the following:
- fix + clean the documentation
- remove any unwanted message, added a variable in order to print diagnostic
- cleaned variable/function names
- changed macros to function
- added components: mex compiler, eng/mx libraries, matlab program
- prop
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14871
==
Reported By:vitaut
Assigned To:
=
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14870
==
Reported By:Melven Roehrig-Zoellner
Assigned To:
On 2014-03-26 13:22-0400 Robert Maynard wrote:
I am proud to announce the CMake 3.0 third release candidate.
With some trepidation (because of the possibility of backwards
incompatibilities, and the usual concerns about "*.0" releases), I
gave it a try.
The bootstrap build worked with no issu
On 28/03/14 15:16, Stephen Kelly wrote:
> The target_compile_features topic in my clone is almost ready to merge to
> next.
Having looked through the docs for the topic, the thing that is missing
that I'd like to see is a way (probably a variable) to specify the
default enabled features for all t
On 04/08/2014 08:13 PM, Josh Green wrote:
> I have gone back and re-read the commit message of the commit that I
> linked earlier:
>
>> Most CMake generators produce relative paths within the build tree and
>> full paths to files outside the build tree. Make VS 10 and VS 11
>> project files consi
On 04/08/2014 08:00 PM, Stephen Kelly wrote:
> adb96ae67e2ae5d8ab543fc60f11750a42ed0c41 (after latest optimization)
[snip]
> My new optimizations make the VTK time comparable with before-refactor on my
> machine.
Great! In my VTK test case posted previously the times are now:
real0m17.653s
