I'm developing a cross platform application written in C++, and I'm
using CMake to configure the build settings for each platform.
The project has common include files that need to be applied to all the
targets built in the project. To that end, the beginning of my main
CMakeList.txt script loo
s and
everything worked fine. I could try testing CMake 2.8.2 with Visual C++
2008 Express to see if it still works.
I suspect it will and the problem lies with the generator for new 2010
version of Visual C++ Express.
On 08/16/2010 06:59 PM, John Drescher wrote:
On Mon, Aug 16, 2010 at 9:53 PM,
On 08/16/2010 10:38 AM, Brian Davis wrote:
First off, I don't know the answer to your question, but I am curious
how you are getting CMake to create inherited projects. What are the
commands you are suing to create an inherited project in CMake? This
is something I think I can use in my proje
I am using CMake 2.8.2 on a 64-bit version of Windows 7 Enterprise.
When I try to configure my project to build for Visual Studio 2010
Express, I get compiler warnings building the projects because none of
the projects are set to inherit from parent or project defaults for
include directories.
I am running the 64-bit version of Windows 7 Enterprise, and I have been
using CMake 2.8.1 to configure my cross platform project to build with
the express version of Visual C++ 9 2008.
I recently install the express version of Visual C++ 2010 on the system,
and upgraded to CMake 2.8.2. Now w
I currently have a project that I configure using CMake 2.8, and because
of a problem with Xcode on the Macintosh I need to add some checks and
adjust things in the CMake scripts to change the build configuration
when Xcode is the intended build tool. I would like to restrict these
changes spe
I have a development project I've created which uses CMake 2.8.1 to
configure the project to be build on Mac OS X 10.6.4 using Xcode 3.2.1.
The project has several targets in it. Two targets share some source
code files. One of those targets links to some frameworks. The other
target used t
05/03/2010 09:02 AM, Sean McBride wrote:
On Sat, 1 May 2010 23:15:03 -0700, Tron Thomas said:
It looks like:
set (CMAKE_OSX_ARCHITECTURES "i386 ppc")
will build a universal binary for a debug build on any platform. How
can someone configure things so that Xcode will build a platform
ure request for CMAKE_OSX_ARCHITECTURES_ in the bug
tracker...
Michael
On 2. May, 2010, at 23:39 , Tron Thomas wrote:
Hello Werner,
It is not just a simple matter of setting the architectures to either i386 or
ppc. For debug, the project should create an architecture specific build. For
relea
equartz.net
On Sun, May 2, 2010 at 11:41 AM, Tron Thomas wrote:
Before when I was using an earlier version of CMake, it would configure the
project to build a 32-bit version of all the project target's regardless of
which version of Mac OS X I was using. It would also build just the
pla
the -arch x86_64 flag, and I'm not sure how well things will work if the
-arch x86_64 is used with the -m32 flag.
Hi Thomas,
On 5/2/10 5:41 PM, Tron Thomas wrote:
Before when I was using an earlier version of CMake, it would configure
the project to build a 32-bit version of all the p
I don't think this will work. The first approach relies on
CMAKE_BUILD_TYPE, which is only applicable to make based generators. I
build my project on Mac OS X using Xcode, which is not make based, at
least in this context.
The second solution just reverses the problem. By this I mean that,
eing 32-bit. So,
what is it exactly that you want?
Michael Wild
On Sun, May 2, 2010 at 8:15 AM, Tron Thomas <mailto:tron.tho...@verizon.net>> wrote:
It looks like:
set (CMAKE_OSX_ARCHITECTURES "i386 ppc")
will build a universal binary for a debug build on any pla
ay 1, 2010, at 15:33, Tron Thomas wrote:
I am writing a cross platform application using CMake that builds on
Mac OS X. I just upgraded to CMake 2.8-1. When I configure and
build my project on my Power Mac G5 system running Mac OS X 10.5.8,
the project builds just fine.
When I try to con
Quartz Software Dayton, Ohio
On May 1, 2010, at 15:33, Tron Thomas wrote:
I am writing a cross platform application using CMake that builds on
Mac OS X. I just upgraded to CMake 2.8-1. When I configure and
build my project on my Power Mac G5 system running Mac OS X 10.5.8,
the proj
ke Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On May 1, 2010, at 15:33, Tron Thomas wrote:
I am writing a cross platform application using CMake that builds on
Mac OS X. I just upgra
I am writing a cross platform application using CMake that builds on Mac
OS X. I just upgraded to CMake 2.8-1. When I configure and build my
project on my Power Mac G5 system running Mac OS X 10.5.8, the project
builds just fine.
When I try to configure the project on my MacBook Pro running
Tyler Roscoe wrote:
On Sat, May 09, 2009 at 10:23:44PM -0700, Tron Thomas wrote:
What is involved in writing a patch?
This article looks like a pretty good summary if you have a Linux-like
environment available:
http://www.linuxforums.org/applications/using_diff_and_patch.html
tyler
What is involved in writing a patch?
Tyler Roscoe wrote:
On Fri, May 08, 2009 at 05:34:19PM -0700, Tron Thomas wrote:
I looked at the FindDevIL.cmake file, and if I understand it correctly
it might be wrong for Windows. On Linux, the main library is called
libIL.so. On Windows, however
Tron Thomas wrote:
Tyler Roscoe wrote:
On Fri, May 08, 2009 at 01:43:16PM -0700, Tron Thomas wrote:
I am trying to use CMake to configure a project for Windows. The
project has dependencies on 3rd party packages. Most of these packages
are resolved successful with the FIND_PACKAGE
Tyler Roscoe wrote:
On Fri, May 08, 2009 at 01:43:16PM -0700, Tron Thomas wrote:
I am trying to use CMake to configure a project for Windows. The
project has dependencies on 3rd party packages. Most of these packages
are resolved successful with the FIND_PACKAGE command. However, CMake
I am trying to use CMake to configure a project for Windows. The
project has dependencies on 3rd party packages. Most of these packages
are resolved successful with the FIND_PACKAGE command. However, CMake
is unable to resolve a recent package that was added to the project,
even though the f
I am trying to define an operation in a custom targt that varies on
different platforms and take different command line arguments. I
tried defining the command using something like:
set(Command "command_name -flags")
Then using it like:
set_custom_target(TargetName ${SomeOtherCommand} COMM
I am trying to use CMake to configure a cross platform project I'm
developing. On platforms that have IDE's such as Mac OS X and Windows,
the configuration work fine in that programs can be built with debug
information for development purposes. On Linux, I am just using
Makefiles and no speci
isguised as a single application
file. I knew the file could simple be embedded into the bundle, and I
thought perhaps I could apply a similar strategy to other platforms.
My solution now it to just use name of the application for the
configuration file.
Philip Lowman wrote:
On Thu, Jan 29, 2009 at
hilip Lowman wrote:
On Tue, Jan 27, 2009 at 10:34 PM, Tron Thomas <mailto:tron.tho...@verizon.net>> wrote:
I want to use CMake to configure a project that will build several
applications. I would like things such that each built program
ends up in a direc
I want to use CMake to configure a project that will build several
applications. I would like things such that each built program ends up
in a directory path like:
.../BuildDirectory/Debug/ApplicationName/AppliationName(.exe)
What is needed to cause CMake to configure this kind of build outpu
I want to use CMake to configure a project so that all programs and
libraries are built into the same directory. So for a debug build of
the project the directory might be something like ProjectName/build/
Debug.
This works fine for most targets. However built Mac OS X framework
bundles
What is the --build-run-dir for CTest supposed to do?
I tried to use it to run a unit test from a specific directory and that
did not work.
How can someone specify the working directory for a unit test?
___
CMake mailing list
CMake@cmake.org
http://w
I need to be able to run a certain unit from a specific directory so
that it will be able to find some supporting file that are needed for
the test. However CTest insists on launching the test from a different
location.
I tried using the --build-run-dir and --build-exe-dir flags. Neither of
Hey Philip,
I tried both the flag and exporting the environment variable. Neither
method produced the output from the test application when the test
failed.
What is needed to used this feature?
Philip Lowman wrote:
On Sun, Dec 7, 2008 at 5:44 PM, Tron Thomas <tron.tho...@verizon.net>
I am trying to use CMake to configure a project that has unit tests.
One unit test requires supporting XML files to perform its test. It was
assumed that the test would be executed from the directory where the
test application exists, so a target was added that copies the XML files
to that lo
_PATH}/
Debug when building the debug version the application.
How can I get the copied files and built executable to appear in the
same directory.
On Dec 11, 2008, at 8:44 o'clock, Tron Thomas wrote:
I have a project configured with CMake that needs to have set of
XML files copied to the
I have a project configured with CMake that needs to have set of XML
files copied to the directory where executables are built so that a
unit test that relies on these files can execute.
I tried to create a custom command that should copy the files and
tried to set that command up as depen
I have a project configured by CMake that uses a macro to create an
executable from a generated source file using code like the following:
macro(CreateProgram Name)
set(SourceFile ${Name}.cpp)
add_custom_command(OUTPUT ${SourceFile}
COMMAND
DEPENDS ${ARGN}
WORKING_DI
Philip Lowman wrote:
.. Original Message ...
On Mon, 08 Dec 2008 10:50:28 -0500 "Bill Hoffman"
<[EMAIL PROTECTED]> wrote:
I still think it looks ugly and hard to see the tests that failed.
Not all testing suites are going to be as verbose as CxxTest. It's also not going
That looks like it would work. What can someone do to make sure that
the test get run every time a build is performed?
Philip Lowman wrote:
On Sun, Dec 7, 2008 at 5:44 PM, Tron Thomas <[EMAIL PROTECTED]>
wrote:
It
would be nice if the original "test" and RUN_TESTS
produced when a test is successful. If there is not a lot then it might
not be that big of an issue. Otherwise it would be nice if there were a
way to produce verbose output during a failure and maybe normal output
when a test succeeds.
Bill Hoffman wrote:
Tron Thomas wrote:
I thin
;test" and RUN_TESTS targets could be
configured this way without having to create and additional target that
replaces them.
Bill Hoffman wrote:
Tron Thomas wrote:
Hey Bill,
The command listed below looks like it is something that would be
issued from a command line in a terminal, and
wrote:
Philip Lowman wrote:
On Sat, Dec 6, 2008 at 9:00 PM, Tron Thomas <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I know that if I type ctest -V from the command line, I can get
output that include the CxxTest information. I'm not sure what I'm
Yes, that it what I want. Who knows of any way this might be done?
Philip Lowman wrote:
On Sat, Dec 6, 2008 at 9:00 PM, Tron Thomas <[EMAIL PROTECTED]>
wrote:
I
know that if I type ctest -V from the command line, I can get output
that include the CxxTest information. I'm no
Sat, Dec 6, 2008 at 7:22 PM, Tron Thomas <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I am creating a CMake configured project that uses the CxxTest
unit testing framework for testing various components.
When I build the test target that runs the test, and
I am creating a CMake configured project that uses the CxxTest unit
testing framework for testing various components.
When I build the test target that runs the test, and there are
failures, CTest will report that the test fail, and it doesn't provide
the details about what the failures wer
output make it much more clear what happened when the test was run, that
the original output. How can I configure the project so output like
this will occur rather than the default output?
Bill Hoffman wrote:
Tron Thomas wrote:
Okay, I changed the add_test command to:
add_test(${Name
set=US-ASCII; format=flowed; delsp=yes
You might want to try:
ADD_TEST(${Name} ${EXECUTABLE_OUTPUT_PATH}/${Name})
Mike
On Nov 27, 2008, at 5:42 PM, Tron Thomas wrote:
I am trying to use CMake to configure a project on Mac OS X that
contains different subdirectories where various libraries a
to be used by this project on the Windows platform.
David Cole wrote:
I think the problem here was that you were giving
"${CMAKE_SOURCE_DIR}/" where you should have had "to Perl>"
CMAKE_SOURCE_DIR is your source tree. Is perl really under your source
tree?
On Thu, Nov
. I'm hoping this proves my configuration will
work without Cygwin.
Alexander Neundorf wrote:
On Friday 28 November 2008, Tron Thomas wrote:
When I remove the PATHS entry from the find_library library, CMake
succeeds. This is because I have Cygwin installed, and CMake finds the
install it for configuring the project on their system.
What can I do so I can test how well this configuration will work on a
system that does not have Cygwin installed?
Alexander Neundorf wrote:
On Thursday 27 November 2008, Tron Thomas wrote:
Since Perl is not typically included with
I am trying to use CMake to configure a project on Mac OS X that
contains different subdirectories where various libraries and such are
built. These subdirectories will also contain unit tests for the
built components. In the root CMakeLists.txt file, I have defined a
macro that will help
refers to the root directory of the Perl
installation (i.e. the directory that contains the bin, lib, etc.
subdirectories). I don't know if it needs to include the path to the
actual executable.
Alexander Neundorf wrote:
On Thursday 27 November 2008, Tron Thomas wrote:
I am tryi
I am trying to configure a CMake project which requires Perl for
building on Windows. I have added the find_package command specifying
that Perl is required and providing the path for where the Perl binaries
are located. Despite this, I get output like the following when trying
to configure u
I corrected the directory name and tried it again. I get the same results.
Martin Costabel wrote:
Tron Thomas wrote:
[]
1/ 1 Testing TestRunnerCould not find
executable TestRunner.app/Content/MacOS/TestRunner
Looked in the following places:
TestRunner.app/Content/MacOS
I filed bug 8139 against the issue. I tried using the
get_target_property command and that did not fix the problem.
Bill Hoffman wrote:
Tron Thomas wrote:
I tried that originally, and it does not work. When add_executable
is used to create an application bundle on MacOS X, it does not
this bundle; it expects a runnable executable as the name
for the second argument to add_test.
Bill Hoffman wrote:
Tron Thomas wrote:
On Mac OS X, I want to build a graphical test application to be added
as a test in a project configured by CMake. However, I am unable to
add this application
On Mac OS X, I want to build a graphical test application to be added as
a test in a project configured by CMake. However, I am unable to add
this application as a test in CMake because it Mac OS X builds the
program as an application bundle, and CMake is unable to find the
correct path to the
I am trying to configure a project with CMake that uses the CxxTest
testing framework. CxxTest will generate source files that may be added
into application that test the software. A macro has been written that
will create custom commands for generated the needed source file.
However, when I
I have made some progress, and I'm still having problems.
The first difficulty I had was with the Info.plist file. It seems that
CMake was specifying it's own Info.plist even though I tried to include
one as a source file to the target.
I eventually got the build to use the proper Info.plist
I was able to figure out how to build a Mac OS X framework using
CMake. Now, I would like to know how I can build a NIB based Cocoa
application on the same platform. The BundleTest example included with
the CMake source code only shows how to create a Carbon bundle.
Where can I find informa
What directory are you referring to when you mention
CMake/Tests/Framework? Where do I find this information?
Date: Tue, 21 Oct 2008 12:42:58 -0400
From: "David Cole" <[EMAIL PROTECTED]>
Subject: Re: [CMake] Mac OS X frameworks
To: "Michael Jackson" <[EMAIL PROTECTED]>
Cc: cmake@cmake.org
Messag
The only thing I found was a wiki that had proposals for how CMake might
be able to build a framework if the functionality was added. I don't
know if this functionality has actually been added to the current
version of CMake. Where can I find definitive documentation on how to
build a framewo
I tried posting this question earlier, and I never saw it. It could be
that I posted before I was fully added to the mailing list.
Anyway, I've been trying to look into what it would take to build a Mac
OS X framework using CMake to configure the build system, and it is
unclear to me how well t
61 matches
Mail list logo
