Yes, that is the only reason. They are bulky and useless, at least in
the case of CMake.
Come to think of it, however, it could be useful if CMake offered the
possibility to install the various parts as different COMPONENTS.
E.g., for ParaView it would make sense to install the Qt headers a
Hello all, I'm just getting going with CMake and qt, and I'm having a bit of
a problem.
I've assembled pretty much the simplest CMakeLists.txt file I can imagine
for a very simple example qt project. (I'm trying to build the qt 4.6
"states" example using CMake.)
When I build, I get the following l
Before the bug fixed, is there any way inside CMake to add "
around the filename? Use special commands?
Zhiwei
2009/12/3 Song Zhiwei :
> CMake 2.8.0 on Windows
>
> 2009/12/3 John Drescher :
>>> I use CMake to generate a Code::Blocks MinGW Makefiles for my project
>>> Module4Test. Module4Test.cbp
On Friday 04 December 2009 03:19:24 pm David Cole wrote:
> Do you have a good idea for how to implement "everything except the
> headers"...?
Maybe something like:
install(DIRECTORY ... REGEX Headers EXCLUDE)
>
> There's already some pretty gnarly CMake script code in the fixup_bundle
> routines.
Do you have a good idea for how to implement "everything except the
headers"...?
There's already some pretty gnarly CMake script code in the fixup_bundle
routines. I'd like to keep it as simple and understandable as possible.
I'm assuming your reason for not wanting the headers in there is simply
Everything except the headers, that is...
Michael
On 4. Dec, 2009, at 21:04 , David Cole wrote:
Sounds like we need the whole framework now instead of just the
libraries
from inside them... Does one of you have the time to create a bug
report for
this...?
Thx,
David
On Fri, Dec 4, 2009 a
Sounds like we need the whole framework now instead of just the libraries
from inside them... Does one of you have the time to create a bug report for
this...?
Thx,
David
On Fri, Dec 4, 2009 at 2:40 PM, Clinton Stimpson wrote:
>
> The problem is the CMakeIngestOSXBundleLibraries.cmake script doe
The problem is the CMakeIngestOSXBundleLibraries.cmake script doesn't copy the
Resource directory in the QtGui framework. It only copies the actual binary
within the framework.
And its a problem when using a cocoa based Qt.
It appears BundleUtilities.cmake has the same problem of not copying f
And just to follow up more, using the autoconf system to build and
install cmake does not work either. Still missing the qt_menu.nib
file. What is the officially supported Qt version for to build CMake?
--
Mike Jackson
On Dec 4, 2009, at 1:21 PM, Bill Hoffman wrote:
Michael Jackson wrote
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Dec 4, 2009, at 1:21 PM, Bill Hoffman wrote:
Michael Jackso
Michael Jackson wrote:
I tried to build CMake 2.8.0 from source on OS X 10.5.8 Intel in Release
mode with Qt 4.5.3 (as cocoa frameworks). I did a "make install" and
when I try to double click the CMake 2.8-0.app bundle I get the
following error:
Process: CMake 2.8-0 [33756]
Path:
I tried to build CMake 2.8.0 from source on OS X 10.5.8 Intel in
Release mode with Qt 4.5.3 (as cocoa frameworks). I did a "make
install" and when I try to double click the CMake 2.8-0.app bundle I
get the following error:
Process: CMake 2.8-0 [33756]
Path:/Users/Shared/
Tyler Roscoe wrote:
On Fri, Dec 04, 2009 at 12:09:09PM -0500, Bill Hoffman wrote:
Right now we just don't do that. However, we do have continuous builds
running on systems that wait for anything to be checked into the version
control system. Then they do a build and test. But, we have no w
On Thu, Dec 03, 2009 at 04:48:58PM -0600, Randy Hancock wrote:
> install(FILES
> ${CMAKE_CURRENT_BINARY_DIR}/\${CMAKE_INSTALL_CONFIG_NAME}/project_name.pdb
> DESTINATION ${SYMBOLS_DIR})
>
> where SYMBOLS_DIR is set to something like:
> set(SYMBOLS_DIR "${CMAKE_SOURCE_DIR}/dist/symbols")
>
> The
On Fri, Dec 04, 2009 at 09:00:14AM -0800, Tyler Roscoe wrote:
> Thanks for the reply. I'm going to try to carve out some time to give
> Hudson a test drive.
Btw, Randy, are any of your Hudson configs or other setup scripts
available somewhere for me to look at? Maybe you can send them to me
off-li
On Fri, Dec 04, 2009 at 12:09:09PM -0500, Bill Hoffman wrote:
> Right now we just don't do that. However, we do have continuous builds
> running on systems that wait for anything to be checked into the version
> control system. Then they do a build and test. But, we have no way
> to ask for
Tyler Roscoe wrote:
The solution we currently have sounds a lot like your setup: a cron that
updates the build scripts and then a cron that runs the build scripts.
Maybe I'm overreacting a bit since my CMake projects are fairly immature
and we still muck arouund with things quite a bit, but this
On Fri, Dec 04, 2009 at 08:53:19AM -0600, Randy Hancock wrote:
> We use Hudson for c++ CI. It works very well for us. Just point it to
> a script that kicks off the build (e.g. cmake --build) and have it
> archive the artifacts (build logs, test output, etc.). I'm sure there
> are fancier ways to s
On Thu, Dec 03, 2009 at 09:32:48AM -0500, Bill Hoffman wrote:
> We are working on being able to drive builds from CDash itself.
> However, it is not really that hard to manage the multiple test machine
> cronjobs. What we do at Kitware is create a version controlled script
> directory. Each m
On Fri, Dec 04, 2009 at 09:04:45AM -0600, Brian Davis wrote:
> What I would like to see is:
>
> PathToWherever/Debug/bin
> PathToWherever/Debug/lib
> PathToWherever/Debug/cfg
> ...
>
> PathToWherever/Release/bin
> PathToWherever/Release/lib
> PathToWherever/Release/cfg
> ...
>
> PathToWherever/P
OK, Really the last follow up. I guess I didn't clean the build
directory good enough last time. I now only get 2 tests based on using
CMAKE_OSX_ARCHITECTURES=i386;x86_64.
Sorry for the noise.
--
Mike Jackson
On Dec 4, 2009, at 11:10 AM, Michael Jackson wrote:
Just to follow up a bit on
Just to follow up a bit on this, here is what I am doing:
#
--
macro(MXA_ADD_TEST testname Exename)
if (NOT APPLE)
ADD_TEST(${testname} ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$
{Exename})
else()
forea
>> I only can reproduce this behavior if I have sources which are NOT under the
>> top-level >> source directory, i.e. something like this:
>> Am I assuming correctly that that's what you're doing? In that case you
>> could do
>> something like this:
Yes, that is exactly what we've been doi
On Fri, Dec 4, 2009 at 4:39 PM, Olivier Pierard
wrote:
> Dear all,
>
> In order to perform 32 bits compilation on 64 bits platform, how can I
> tell that all find_libraries for which no path is specified to look in
> /usr/lib instead of /usr/lib64 ? Is there a configuration variable for
> cmake p
Dear all,
In order to perform 32 bits compilation on 64 bits platform, how can I
tell that all find_libraries for which no path is specified to look in
/usr/lib instead of /usr/lib64 ? Is there a configuration variable for
cmake platform or a default searching directories variable ?
Thank you,
So the issue is to test OS X Universal binary with at least 3
different code paths: i386, x86_64 and PPC.
There is the "arch" command on the command line that can be used
launch an executable using the indicated architecture. I am wondering
how this might be used with CTest to test the diff
I was wondering if there is now a cleaner implementation of the following
issue (see prior attached email below from Philip) where the PREFIX HACK
must be used to remove Debug and Release from the ouput path.
What I would like to see is:
PathToWherever/Debug/bin
PathToWherever/Debug/lib
PathToWh
We use Hudson for c++ CI. It works very well for us. Just point it to
a script that kicks off the build (e.g. cmake --build) and have it
archive the artifacts (build logs, test output, etc.). I'm sure there
are fancier ways to set it up with plugins but we've gotten by with
this minimal setup for a
Rodolfo Lima wrote:
Michael Wild escreveu:
I once wrote a cmake-macro which created these symlink trees (only for
the headers, though). It was a huge PITA. With such symlink trees you
can never be really sure that they are consistent with the source tree.
I think I'm convinced now. The truth i
Hi,
I am building a software under osx. We use cmake + qt.
I was wondering what was the best solution to build the package?
I found a few pages about it:
http://www.cmake.org/Wiki/BuildingOSXApplications : this one give an example
with sh scripts
http://www.cmake.org/Wiki/CMake:CPackPackageGe
Michael Wild escreveu:
> I once wrote a cmake-macro which created these symlink trees (only for
> the headers, though). It was a huge PITA. With such symlink trees you
> can never be really sure that they are consistent with the source tree.
I think I'm convinced now. The truth is: I've always wor
On Thu, 03 Dec 2009 18:17:21 -0200, Rodolfo Schulz de Lima
wrote:
> How does emacs know all the project files? Or it is only looking
> backwards on the include list (this would only find header files)?
M-x visit-tags-table
I have a cmake command to generate tags in the *source* directory, I run
On 3. Dec, 2009, at 23:23 , Rodolfo Lima wrote:
John Drescher escreveu:
install screen
Thanks for the tip but that's not my point in this whole thread (i.e.
I'm not looking for solutions, I'm giving one).
CMake does so much complicate things to make working with software
projects a seamless
doooh, what a great start on this list.
Hendrik, thanks for the pointer, so I just didn't find it as I was
searching for CXX or Fortran but not for :(
Maybe one could mention that these variables are used for C/Fortran
linking with C++ static libraries.
-Tobias
Hendrik Sattler wrote:
Zitat
On 3. Dec, 2009, at 22:08 , Voisard, Shane S CIV NSWCDD, K54 wrote:
Is there a way to set the directory that cmake (2.8) uses for object
file generation? I haven't found an online resource for this.
There is a difference when we build the same project on a Windows
vs. Linux platform.
On
35 matches
Mail list logo
