Hello,
I am working with cross-compiling code using CMake. I am able to get
the following CMakeLists.txt to work:
# --
SET(CMAKE_TOOLCHAIN_FILE ../toolchain/Prizm.cmake)
project(example1)
file(GLOB EXAMPLE1_SRC "src/example1/*.c*")
add_executable(example1 ${EXAMPLE1_SRC})
# --
Hi,
On Tue, Jul 31, 2012 at 02:30:16PM -0400, cmake-requ...@cmake.org wrote:
> Date: Tue, 31 Jul 2012 11:30:14 -0700 (PDT)
> From: festner
> Subject: [CMake] Valgrind does not find tests
> To: cmake@cmake.org
> Message-ID: <1343759414478-7581046.p...@n2.nabble.com>
> Content-Type: text/plain; cha
On Tue, Jul 31, 2012 at 1:45 PM, J Decker wrote:
> what about using CMAKE_INSTALL_CONFIG_TYPE instead?
>
OK, don't know that one, nor is it in my CMake documentation. But, the
#pragma suggested by the bug report saved me, so off I go...
Thanks,
- Steve
--
Powered by www.kitware.com
Visit other
On Tue, Jul 31, 2012 at 4:45 AM, David Cole wrote:
> Also,
>
> see this outstanding "bug" report:
>
> http://public.kitware.com/Bug/view.php?id=12566
>
Thanks David, that did it for me. A lot of things would be simpler in
the project I have if we could have per-configuration target
properties.
> Call CONFIGURE_FILE() twice, once for the installation
> and once for the build-tree:
Thanks, Michael! That's what I was looking for!
Kyle
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topi
what about using CMAKE_INSTALL_CONFIG_TYPE instead?
On Tue, Jul 31, 2012 at 4:45 AM, David Cole wrote:
> Also,
>
> see this outstanding "bug" report:
>
> http://public.kitware.com/Bug/view.php?id=12566
>
>
> On Tue, Jul 31, 2012 at 7:42 AM, David Cole wrote:
>> CMAKE_BUILD_TYPE is not set for
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.
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.imgur.com/bqqnp.png, and
I found a custom
https://qextserialport
On Tuesday 31 July 2012, Fabio Fracassi wrote:
> Hi,
>
> I ran into some problems when I tried to set a cmake internal variable
> (CMAKE_MODULE_PATH) from a function.
> I understand that when I use list() commands an new local scoped
> variable is created that I have to "export" to the parent scop
tion:Site:olmenhorn
SetCTestConfigurationFromCMakeVariable:BuildName:CTEST_BUILD_NAMESetCTestConfiguration:BuildName:Linux_Standart_Valgrind
Site: olmenhorn
Build name: Linux_Standart_Valgrind
Determine Nightly Start Time
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
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.
--
View this message in context:
http://cmake.3232098.n2.nabble.com/Why-are-my-static-libs-not-being-read-tp758104
> 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
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 does find
Hi,
On Tue, Jul 31, 2012 at 6:25 PM, rainman110.de
wrote:
> Hello together,
>
> this is my first post to this mailing list as I am a new cmake user and
> trying to learn it. I already posted the message but somehow it was not
> accepted by nabble...
>
> I have a multiplatform project which requir
Current if I run
make help Output look likes:
make help
The following are some of the valid targets for this Makefile:
... all (the default if no target is provided)
... clean
... depend
... edit_cache
... rebuild_cache
... a
... b
... ba
Where ba is subject of b. I want to modify output generate
Hello together,
this is my first post to this mailing list as I am a new cmake user and
trying to learn it. I already posted the message but somehow it was not
accepted by nabble...
I have a multiplatform project which requires the CURL package. On Linux the
package is found by cmake as it is lo
Hi Steve,
that was it!
> Set Boost_USE_STATIC_RUNTIME OFF. You're using shared runtime:
> http://www.boost.org/doc/libs/1_50_0/more/getting_started/windows.html#library-naming
Yep, my fault. When I turn off Boost_USE_STATIC_RUNTIME everything works.
Thanks again!
Christian
--
Powered by www.
On Jul 31, 2012, at 9:48 AM, Christian Henning wrote:
> Hi Mike,
>
> On Mon, Jul 30, 2012 at 9:24 PM, Michael Jackson
> wrote:
>> Where is your boost installed at? What operating system are you using? Is
>> this boost precompiled or compiled by you?
>> If you set BOOST_ROOT as a cmake variable
Hi Mike,
On Mon, Jul 30, 2012 at 9:24 PM, Michael Jackson
wrote:
> Where is your boost installed at? What operating system are you using? Is
> this boost precompiled or compiled by you?
> If you set BOOST_ROOT as a cmake variable and point it to the top level
> directory of your boost installat
Hi Steve,
I think you got me a step further. Thanks. See below:
On Mon, Jul 30, 2012 at 9:11 PM, Steve deRosier wrote:
> On Mon, Jul 30, 2012 at 5:44 PM, Christian Henning
> wrote:
>> Hi there, I'm trying to figure why cmake cannot find my boost
>> installation. Actually, I'm working of some o
Weird; for me, ZERO_CHECK goes into the folder as well.
The rationale for ALL_BUILD is that cmake wants it to be the default
project when no .suo exists, which means it has to be the first one in
the solution and cannot be in a solution filter. It's a pity this
behaviour can't be turned off :-( I'
Also,
see this outstanding "bug" report:
http://public.kitware.com/Bug/view.php?id=12566
On Tue, Jul 31, 2012 at 7:42 AM, David Cole wrote:
> CMAKE_BUILD_TYPE is not set for Visual Studio or Xcode generators...
>
> It's a build-time choice.
>
>
> On Tue, Jul 31, 2012 at 5:03 AM, Brett Delle
CMAKE_BUILD_TYPE is not set for Visual Studio or Xcode generators...
It's a build-time choice.
On Tue, Jul 31, 2012 at 5:03 AM, Brett Delle Grazie
wrote:
> On 31 July 2012 01:05, Steve deRosier wrote:
>> I need a way to have the WIN32_EXECUTABLE property set off for debug
>> builds and on for
2012/7/31 m.hergarden :
> On 07/30/2012 11:28 PM, Xavier Besseron wrote:
>>
>> This is quite independent of CMake. It works with other build systems
>> like autotools/makefile as well.
>>
>> CFLAGS="-m32" CXXFLAGS="-m32" tells CMake to pass the '-m32' to the C
>> and C++ compilers.
>> It tells the
Hi Fabio.
With ALL_BUILD, you're out of luck, but other default cmake targets go
to a group if you set the global property PREDEFINED_TARGETS_FOLDER.
I am afraid I can't help with the other points.
Petr
On Tue, Jul 31, 2012 at 12:02 PM, Fabio Fracassi
wrote:
> Hi,
>
> I am currently cleaning u
Forgot to cc list... (sorry!)
Hi Fabio,
On 31 July 2012 10:26, Fabio Fracassi wrote:
> Hi,
>
> I ran into some problems when I tried to set a cmake internal variable
> (CMAKE_MODULE_PATH) from a function.
> I understand that when I use list() commands an new local scoped variable is
> created th
Hi,
I am currently cleaning up our build system and stumbled over some minor
things, where I did not find a way to accomplish them. Are they at all
possible?
I wanted to contain all cmake generated targets (like ALL_BUILD,
ZERO_CHECK, INSTALL, ... ) in a Project group, but I cannot set the
Hi,
I ran into some problems when I tried to set a cmake internal variable
(CMAKE_MODULE_PATH) from a function.
I understand that when I use list() commands an new local scoped
variable is created that I have to "export" to the parent scope. I tried
to do that but it seems that the scope of cm
Hi Christian,
(see below)
On 31 July 2012 07:50, Andrew Maclean wrote:
> Hi Christian,
>Mike's comment about setting BOOST_ROOT should work. If this doesn't,
> make sure that your directories look like this:
>
> C:\boost
> C:\boost\include
> C:\boost\include\boost-1_50
I've also had problem
On 31 July 2012 01:05, Steve deRosier wrote:
> I need a way to have the WIN32_EXECUTABLE property set off for debug
> builds and on for release builds when using the IDE.
>
> Here's the deal: For debug our code uses the standard main()
> construct, and for release we use the WinMain(). Lets just s
31 matches
Mail list logo
