Hi Eric,
> Variable values shoud be retrieve with curly brace, i.e.
>
> $LIBS --> ${LIBS}
Yick, I had done that but not cited it correctly in my mail, sorry about
that.
> Then when you have a list of something you usually use LIST(APPEND
>
> LIST(APPEND LIBS "libN")
>
> even if
>
> SET(LIBS "
On 31. Aug, 2009, at 7:08, King, Steven R wrote:
Can't you put all executables and shared libraries in one
directory, so they
are all local to each other?
In the top level CMakeLists.txt file just add
SET(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
SET(CMAKE_LIBRARY_OUTPUT_DIRECTO
2009/8/31 Eike Kroemer :
> Hi there,
>
> using cmake-2.6.4-Linux-i386, I'd like to use
>
> set(LIBS lib1)
> set(LIBS "$LIBS lib2")
> [...]
> set(LIBS "$LIBS libN")
>
> target_link_libraries(target $LIBS)
>
> instead of writing explicitely
>
> target_link_libraries(target lib1 lib2 [...] libN)
Hi there,
using cmake-2.6.4-Linux-i386, I'd like to use
set(LIBS lib1)
set(LIBS "$LIBS lib2")
[...]
set(LIBS "$LIBS libN")
target_link_libraries(target $LIBS)
instead of writing explicitely
target_link_libraries(target lib1 lib2 [...] libN)
but while cmake gives no error messages,
2009/8/31 Antonio Bulgheroni :
> Dear Eric,
>
> thanks for the fast reply.
>
>
> In the example the selected generator for the Mac was PackageMaker, and this
> is what I'm using. Yes, it is working w/o components.
Then I think the PackageMaker generator maintainer/contirbutors may be the right
p
Hi Marcel,
[...]
> See tiny example below (hope this helps).
Yes, it does, thank you very much for the detailed walkthrough.
Based on your suggestion I've experimented a bit and found that my key
issues were:
- introducing a separated build-directory structure - should have done
that long befo
MAKE_OSX_SYSROOT /Developer/SDKs/android-sdk-mac_x86-1.5_r2
Yep, there is the problem. CMake looks in the /Developer/SDKs for all
available SDKs and then greps for some information to try and figure
out which one to use. Get rid of anything OTHER than official Apple
SDKs that are in /Develo
Dear Eric,
thanks for the fast reply.
In the example the selected generator for the Mac was PackageMaker, and this
is what I'm using. Yes, it is working w/o components.
Cheers,
toto
--
Antonio Bulgheroni, PhD
http://unico-lab.blogspot.com
“There are 10 ki
> Can't you put all executables and shared libraries in one directory, so they
> are all local to each other?
> In the top level CMakeLists.txt file just add
> SET(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
> SET(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
>
> The executab
On Sun, Aug 30, 2009 at 9:30 PM, John Drescher wrote:
> > Well problem is why doesn't it print the std::cout that I've put inside
> > main? while it's running main
> >
>
> I believe not printing any stdout from your application is intentional
> so not to interfere with the CTest output. I prefer
> this person also has the problem <
> http://stackoverflow.com/questions/1349886/cmake-settings-on-snow-leopard>
>
> Yup, that was also me :-)
> Please post the following variables from your project after a first run of
> cmake on your project from a clean build directory.
>
> CMAKE_OSX_ARCHIT
I'm creating a custom target to get XML output from my Boost.test test
cases for use in Hudson, and I want the output for all tests to be
generated even if some fail.
Unfortunately there are two blockers:
1. cmake makes the first test case to fail stop the build.
2. cmake offers no way
Just to follow up a bit more. The "innards" that I was referring to
are NOT in CMake 2.6.4 but in CMake CVS. If you can, checkout the
latest CMake from CVS build it and then see if your project will
configure.
Mike
On Aug 30, 2009, at 9:48 PM, Michael Jackson wrote:
I don't think CMake aut
I don't think CMake automatically builds Universal Binaries. CMake
will look at the arch of the host system and try to build that arch,
which is i386 on intel or "ppc" on anything else. Unless there is
something in your project where you are setting the
CMAKE_OSX_ARCHETECTURES to i386;ppc t
> Well problem is why doesn't it print the std::cout that I've put inside
> main? while it's running main
>
I believe not printing any stdout from your application is intentional
so not to interfere with the CTest output. I prefer it this way. There
could be a way to activate this, I do not know.
Well problem is why doesn't it print the std::cout that I've put inside main?
while it's running main
> Date: Sun, 30 Aug 2009 17:20:26 -0400
> Subject: Re: [CMake] weird output with ctest
> From: dresche...@gmail.com
> To: aditya15...@hotmail.com; cmake@cmake.org
>
>> I have the following
Hello,
I recently installed Snow Leopard, and I am having trouble building my
application with CMake. The Unix Makefile generator fails while checking for
a working gcc compiler with the following output:
CMake Error at /Applications/CMake
2.6-4.app/Contents/share/cmake-2.6/Modules/CMakeTestCComp
> I have the following command in my CMakeLists.txt and I run the test using
> the command ctest -VV -R test. However the test results doesn't print
> anything that I defined on the test code, it just shows the test passed.
> add_test(test ../build/gbc 0.1 0.3 0.5 0.7 0.9)
>
That is all it is suppo
2009/8/30 Antonio Bulgheroni :
[...]
> (http://www.cmake.org/Wiki/CMake:Component_Install_With_CPack) for making
> component installation using CPack, but it was unsuccessful. I was thinking
> of a problem with my configuration and then I downloaded and compiled the
> example given on the Wiki
Dear all,
I'm quite new to the CMake world and even if I like it very much, there
are still a few things quite mysterious to me. I've just started the
development of a new project and I would like to exploit all the benefit
coming from CMake & Co. I was following the HowTo (
http://www.cmake.o
I have the following command in my CMakeLists.txt and I run the test using the
command ctest -VV -R test. However the test results doesn't print anything that
I defined on the test code, it just shows the test passed.
add_test(test ../build/gbc 0.1 0.3 0.5 0.7 0.9)
When I run ./gbc 0.1 0.3 0.5
On Tue, Aug 25, 2009 at 1:32 PM, j s wrote:
> I am using the Visual Studio generator from the cmake binary distribution.
> If I change flags using ADD_DEFINITIONS, I notice that it doesn't trigger a
> rebuild of all the affected files.
>
> Is this by design?
I've known and worked around this li
On Sat, Aug 29, 2009 at 8:01 PM, Alex H wrote:
> I have a test.cpp file and the test file needs to be linked with another
> .h file... they are all in the same directory, however when I run the
> Makefile that is generated by CMake, it shows this error:
> CMakeFiles/bcoin.dir/test.cpp.o: In func
On 30. Aug, 2009, at 2:01, Alex H wrote:
I have a test.cpp file and the test file needs to be linked with
another .h file... they are all in the same directory, however when
I run the Makefile that is generated by CMake, it shows this error:
CMakeFiles/bcoin.dir/test.cpp.o: In function `ma
$ grep -r Wno-long-double cmake-2.6.4
cmake-2.6.4/Utilities/cmcurl/CMakeLists.txt: CHECK_C_COMPILER_FLAG(-
Wno-long-double HAVE_C_FLAG_Wno_long_double)
cmake-2.6.4/Utilities/cmcurl/CMakeLists.txt:
SET(MPRINTF_COMPILE_FLAGS "${MPRINTF_COMPILE_FLAGS} -Wno-long-double")
cmake-2.6.4/Utilities
25 matches
Mail list logo
