On Fri, 2013-04-12 at 18:07 -0400, Jean-Christophe Fillion-Robin wrote:
> Since the syntax can change between version of Visual Studio, you
> could try to use cmake directly:
>
> cd C:\path\to\project-build
> cmake.exe --build . --target INSTALL --config Release
That worked perfectly; I wa
I usually use:
msbuild /p:Configuration=Release INSTALL.vxproj
Which seems to work on VS 2010 SP1
___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.jack...@bluequ
Hi,
Since the syntax can change between version of Visual Studio, you could try
to use cmake directly:
cd C:\path\to\project-build
cmake.exe --build . --target INSTALL --config Release
See http://www.cmake.org/cmake/help/v2.8.10/cmake.html#opt:--builddir
Alternatively, you could also open
On Fri, 2013-04-12 at 17:04 -0400, Jean-Christophe Fillion-Robin wrote:
> Hi Paul,
> Set option CMAKE_INSTALL_PREFIX to a location of your choice
> Then, build INSTALL target
Hi; thanks a lot for your answer! I was able to set
CMAKE_INSTALL_PREFIX; thanks for that.
Can you give a specific exa
Bringing this thread back to the cmake list...
- Original Message -
> Hi Clint,
> On Fri, Apr 12, 2013 at 9:28 AM, Clinton Stimpson < clin...@elemtech.com >
> wrote:
> > Ok, I now see what is special about it.
>
> > It uses "productbuild" to generates a .pkg (which is then put inside a
Hi Paul,
Set option CMAKE_INSTALL_PREFIX to a location of your choice
Then, build INSTALL target
Hth
Jc
On Fri, Apr 12, 2013 at 4:46 PM, Paul Smith wrote:
> Hi all; I need to rebuild cmake to incorporate a fix that has been added
> since the last release (I could get a nightly build but I wa
Hi folks,
While we're talking Python, I wrote a small patch to FindPythonLibs
that looks to see if PYTHON_VERSION_MAJOR and PYTHON_VERSION_MINOR are
set (by FindPythonInterp), and if so, it puts them in the python
versions list, after the user specified versions, but before the
Python3, Python2, a
Hi all; I need to rebuild cmake to incorporate a fix that has been added
since the last release (I could get a nightly build but I was hoping to
use released cmake with just the fix I need to reduce risk) and which is
causing my builds to fail sometimes. For Linux and MacOS this was quite
simple u
Hi Eric,
On Fri, Apr 12, 2013 at 12:58 AM, Eric Noulard wrote:
>
> Some ##end documentation markup where missing one '#' which makes the
> corresponding CPACK_APPLE_xxx var
> not appearing in the command line doc.
> The doc parser is almost dumm so that it's almost impossible to detect
> that safe
I find addig this line helps.
set_property(CACHE CMAKE_BUILD_TYPE PROPERTY STRINGS
${CMAKE_CONFIGURATION_TYPES} debug release RelWithDebInfo MinSizeRel )
which makes cmake_build_type a drop list to chose.
On Fri, Apr 12, 2013 at 11:53 AM, liulewes wrote:
> I'm using cmake to build my own pro
On Friday 12 April 2013, Lloyd wrote:
> Hi,
>
> I am new to Cmake and at present exploring its features for migrating our
> projects build system to use it.
>
> I have main source folder inside that another folder contains the source
> for our custom library.
>
> I understand that the problem is
I'm using cmake to build my own project under centOS 6. During configuration,
cmake asked me to choose the type of build; however, whatever I typed in for
CMAKE_BUILD_TYPE, it won't let me proceed. Anyone can give a hint?
I using cmake 2.8.10.2 compiled in centOS 6. Thanks.
Best,
Lewes
Brad King wrote:
> On 04/11/2013 04:05 PM, Yngve Inntjore Levinsen wrote:
> > On 11. april 2013 21:31, Matthew Woehlke wrote:
> >>> Where do I submit the merge request? Open a bug report?
> >>
> >> I would recommend following the 'share a topic' instructions at
> >> http://www.cmake.org/Wiki/CMake
On 04/11/2013 04:05 PM, Yngve Inntjore Levinsen wrote:
> On 11. april 2013 21:31, Matthew Woehlke wrote:
>>> Where do I submit the merge request? Open a bug report?
>>
>> I would recommend following the 'share a topic' instructions at
>> http://www.cmake.org/Wiki/CMake/Git/Develop.
>
> Thanks for
of course... This is the source of my test cmake file
#Cmake file of Tests
cmake_minimum_required (VERSION 2.6)
SET(TST_SRC test_rev.cpp test_runner.cpp)
FIND_PACKAGE(Boost REQUIRED COMPONENTS unit_test_framework)
INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SO
1. Can you post tests/CMakeLists.txt (or at least the parts relevant to
creating test_rev)?
2. Does it work if you use the enhanced signature of add_test? I mean
'add_test(NAME Test COMMAND test_rev)'
Petr
On Fri, Apr 12, 2013 at 1:18 PM, Lloyd wrote:
> Yes I built the test and it is in
>
> E
Yes I built the test and it is in
E:\CMakeDemo\BuildDir\tests\Debug\test_rev.exe
I don't know the right way to locate this test executable for cmake
Thanks,
Lloyd
On Fri, Apr 12, 2013 at 4:42 PM, Petr Kmoch wrote:
> Hi Lloyd.
>
> Do you actually have a target (executable) named "test_rev"?
Hi Lloyd.
Do you actually have a target (executable) named "test_rev"? And have you
built it before running RUN_TESTS? RUN_TEST (or its Makefile equivalent
'make test') doesn't automatically build the test executables before
running them.
Petr
On Fri, Apr 12, 2013 at 1:08 PM, Lloyd wrote:
> H
Hi,
I was successful in creating and compiling a simple project C++/Visual
studio using cmake. I have also included one unit test project. All these
projects builds successfully. The test project source and main project
source resides in the root directory of the project. When I try to run
"RUN_TE
Thanks Jc and Eike, it solved my problem
On Fri, Apr 12, 2013 at 12:31 PM, Jean-Christophe Fillion-Robin <
jchris.filli...@kitware.com> wrote:
> Hi Lloyd,
>
> Seems you have a small typo, target name case should be consistent.
>
> Try to use:
>
>TARGET_LINK_LIBRARIES(Tutorial Reverse)
>
> in
2013/4/12 Brian Milco
> Hi,
>
> I've added a CPack package generator for the Mac App Store for your
> consideration. You can find it on github:
> https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
>
> This is a first draft, but it should work to get a basic application
> uploade
Hi Lloyd,
Seems you have a small typo, target name case should be consistent.
Try to use:
TARGET_LINK_LIBRARIES(Tutorial Reverse)
instead of
TARGET_LINK_LIBRARIES(Tutorial reverse)
Hth
Jc
On Fri, Apr 12, 2013 at 2:48 AM, Lloyd wrote:
>
>
>
> On Fri, Apr 12, 2013 at 11:58 AM, Rolf Ei
22 matches
Mail list logo