Can you use "Find_File()" to get the path to the file. Then use the
install(FILES ... ) command to place the file in your app bundle. Not tried any
of that but it might work.
___
Mike Jackson www.bluequartz.net
Principa
The qt_menu.nib package can be located in either the QtGui.framework that gets
copied into your application bundle or in
MyApp.app/Contents/Resources/qt_menu.nib. Either of those locations should
allow your application to work. Do you need to also add a qt.conf file into the
Contents/Resources
Me again, with another issue:
On Mac, I'm running into the problem described in QTBUG-5952:
http://bugreports.qt.nokia.com/browse/QTBUG-5952 where my CPack generated D&D
installer yields an installed app fails with a log message like "Qt internal
error: qt_menu.nib could not be loaded." This
I'm building an app on Mac, Linux, and Win.
My application requires that a helper application, built outside of my project,
be installed along with it. On Linux and Win, its sufficient to copy the
helper app to the same directory as my app. On Mac, it needs to be copied into
the bundle in the
On 2011-01-06 03:02- luxInteg wrote:
just curious,
but I wondering if anyone on list has ever built gcc with cmake.
(or at least had a go)
I did it by hand years ago (1996 when I started with Linux and needed
to add g77 to the slackware version of gcc that I had at the time.) It
was pret
just curious,
but I wondering if anyone on list has ever built gcc with cmake.
(or at least had a go)
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
On 2011-01-05 16:43-0800 Ekaterina Sanina wrote:
Hi,
I was wondering if it's possible to ignore errors and continue the build with
cmake (for example if one wants to find out
how many failures the project has). Is there option similar to -i (
--ignore-errors) or -k (--keep-going) option of GN
Hi,
I was wondering if it's possible to ignore errors and continue the build
with cmake (for example if one wants to find out how many failures the
project has). Is there option similar to -i ( --ignore-errors) or -k
(--keep-going) option of GNU make?
I scanned the documentation and can't find any
Well DUH on me for that one. Thanks!
___
Mike Jackson www.bluequartz.net
On Jan 5, 2011, at 2:39 PM, David Partyka wrote:
> You override this behavior by setting CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP
> to ON and then
On Jan 5, 2011, at 2:36 PM, David Partyka wrote:
> FYI, I just merged removal of setting CMAKE_INSTALL_DEBUG_LIBRARIES from
> ParaView.
>
> On Wed, Jan 5, 2011 at 2:24 PM, Michael Jackson
> wrote:
>> That is where I pulled the code from so I must have grabbed that version.
>> But I think I a
You override this behavior by setting CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP
to ON and then providing your own install rules. See the following chunk
from ParaView.
# Add install rules for required system runtimes such as MSVCRxx.dll
SET (CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP ON)
INCLUDE(InstallR
FYI, I just merged removal of setting CMAKE_INSTALL_DEBUG_LIBRARIES from
ParaView.
On Wed, Jan 5, 2011 at 2:24 PM, Michael Jackson wrote:
> That is where I pulled the code from so I must have grabbed that version.
> But I think I am misunderstanding what should be used when with respect to
> Bun
>From the CMake 2.8.3 release I am using inside the
>InstallRequiredSystemLibraries.cmake file all the way at the bottom is this:
IF(WIN32)
INSTALL_PROGRAMS(/bin ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS})
ELSE(WIN32)
INSTALL_PROGRAMS(/lib ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS})
E
That is where I pulled the code from so I must have grabbed that version. But I
think I am misunderstanding what should be used when with respect to
BundleUtilities and INSTALL when on MSVC.
From the looks of it, if I am "installing" on my local machine then by
definition I have all the neede
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Jan 5, 2011, at 2:01 PM, Bill Hoffman wrote:
> On 1/5/2011 1:01 PM, Da
On 05.01.11 12:34:09, David Cole wrote:
> cmake-gui needs some further work to be automatically testable.
>
> If we launched it as-is on a test run, then it would just hang there
> forever, waiting for user input as gui apps will do, and the test
> would timeout.
There are also tools out there to
This might be my fault If you're building a paraview app. I had SET
(CMAKE_INSTALL_DEBUG_LIBRARIES ON) from a month ago that I didn't remove.
I'll do that right now.
On Wed, Jan 5, 2011 at 1:54 PM, Michael Jackson wrote:
> OK.So how do I NOT package them? So far they _are_ getting put into the
>
On 1/5/2011 1:01 PM, David Cole wrote:
Exactly. It needs further work.
I'm not about to be the brave volunteer who adds a test that adds the
"window server must be running" requirement. And whoever does should
probably add a setting "CMAKE_ENABLE_GUI_TESTS" that is OFF by
default. Then, only on
OK.So how do I NOT package them? So far they _are_ getting put into the
installer even if I set Visual Studio to "Release". I have this at the top of
my CMake code that sets up CPack:
if (MSVC)
SET (CMAKE_INSTALL_DEBUG_LIBRARIES OFF)
INCLUDE (InstallRequiredSystemLibraries)
endif()
Just as an FYI:
The Debug libraries for MSVC are not redistributable components. Do
not build them into an installer. People who need to use them are
required to have a corresponding Visual Studio installation on their
machine.
We provide access to those for INSTALL simply for testing the make
in
I am working on my CPack code for my project. What I have noticed is that the
MSVC runtime libs for both Debug and Release are included when I do an INSTALL
and are NOT included when I try to run the PACKAGE project. Again, this is
probably something simple to solve but I just am not sure what a
Exactly. It needs further work.
I'm not about to be the brave volunteer who adds a test that adds the
"window server must be running" requirement. And whoever does should
probably add a setting "CMAKE_ENABLE_GUI_TESTS" that is OFF by
default. Then, only on dashboard machines that explicitly say th
Testing: You can launch the gui from the command line by passing the absolute
path to the executable inside the app bundle:
509:[mjack...@ferb:CMake]$ /private/tmp/CMake-2.8.3/CMake\
2.8-3.app/Contents/MacOS/CMake\ 2.8-3
Qt internal error: qt_menu.nib could not be loaded. The .nib file should b
cmake-gui needs some further work to be automatically testable.
If we launched it as-is on a test run, then it would just hang there
forever, waiting for user input as gui apps will do, and the test
would timeout.
We'd need to add something like:
- "--configure" "--generate" and "--exit" command
Note that I am using the ./configure to configure CMake itself. Not CMake to
configure CMake. So maybe there is something missing from those installs. The
interesting part (with all the discussions with putting in bug reports) is that
I even provided a patch for 2.8.0. Something got put into CVS
If it works with a nightly tarball, or from git master, then it will
work with 2.8.4...
On Wed, Jan 5, 2011 at 12:12 PM, Michael Jackson
wrote:
> Sure. And _that_ does work. Just curious how that bug fell through versions
> 2.8.0, 2.8.1, 2.8.2, 2.8.3? I guess there isn't a test for actually ver
This should have been fixed with the switch to using BundleUtilities
for CMake's bundle.
The 2.8.3 BundleUtilities should copy in the Resources necessary for
this to work.
So I think that was done (switch to using built in BU) just *after* 2.8.3.
Unless there's still a missing qt.conf file
Sure. And _that_ does work. Just curious how that bug fell through versions
2.8.0, 2.8.1, 2.8.2, 2.8.3? I guess there isn't a test for actually verifying
that the built Qt app actually launches during the test or the CMake GUI is
always guilt with carbon during the testing which would alleviate
Try the download from the CMake website, source download that is. Then
configure and build and then install it.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuart
On 1/5/2011 10:05 AM, Michael Jackson wrote:
Reopened the bug because this is _still_ an issue with CMake 2.8.3.
Just tried to configure, build and install and got the same crash.
Can you try it with the current master branch?
___
Mike
2011/1/5 Michael Wild :
> On 01/05/2011 02:13 PM, Reinhard Thies wrote:
>> On Wednesday 05 January 2011 12:32:52 David Cole wrote:
>>> You can't depend on "package", but you can do this as your custom
>>> target's command:
>>>
>>> cmake --build . --target package --config Release
>>> scp ...
>>
Reopened the bug because this is _still_ an issue with CMake 2.8.3. Just tried
to configure, build and install and got the same crash.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@blu
On 01/05/2011 02:13 PM, Reinhard Thies wrote:
> On Wednesday 05 January 2011 12:32:52 David Cole wrote:
>> You can't depend on "package", but you can do this as your custom
>> target's command:
>>
>> cmake --build . --target package --config Release
>> scp ...
>>
> that the way I have it
> ADD
On Wednesday 05 January 2011 12:32:52 David Cole wrote:
> You can't depend on "package", but you can do this as your custom
> target's command:
>
> cmake --build . --target package --config Release
> scp ...
>
that the way I have it
ADD_CUSTOM_TARGET(delivery
You can't depend on "package", but you can do this as your custom
target's command:
cmake --build . --target package --config Release
scp ...
HTH,
David
On Wed, Jan 5, 2011 at 5:44 AM, Reinhard Thies wrote:
> Hi,
>
> i like to create a custom target "delivery" which depends on package and
At Wed, 5 Jan 2011 11:44:59 +0100,
Reinhard Thies wrote:
>
> Hi,
>
> i like to create a custom target "delivery" which depends on package and
> simply copies the package file using scp to our server.
>
> Any ideas are apreciated.
>
> Thx,
> Reinhard
> __
Hi,
i like to create a custom target "delivery" which depends on package and
simply copies the package file using scp to our server.
Any ideas are apreciated.
Thx,
Reinhard
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
h
Dear all,
I working on windows and use "Cmake 2.8" + "MinGw"
I am try to build .dll from "pthreads-win32" sources
(http://sourceware.org/pthreads-win32/)
by writing CMakeLists.txt (attached) and putting them to src directory
he creates makefile i run it, and after invoking of command:
gcc-
Hi,
Thanks for the reply.
I had seen 'TAG' file but somehow thought that it is under every new
directory created using timestamp (e.g. 20110104-2359/). So, I had started
using below code. However, your solution looks more elegant, so will use it.
file(REMOVE_RECURSE ${CTEST_BINARY_DIRECTO
Thanks a lot! Exactly what I was looking for ;-) I really missed that chapter
Original-Nachricht
> Datum: Wed, 05 Jan 2011 10:12:07 +0100
> Von: Michael Wild
> An: cmake@cmake.org
> Betreff: Re: [CMake] How to get rid off predefine "XXX_EXPORTS"
> @add_library(XXX SHARED ...)
On 01/05/2011 10:05 AM, "Sören Freudiger" wrote:
> Hi
> I have a problem. After running CMake (VS 2003/2008 project) there's always a
> EXPORT preprocessor define in my project setting that I don't need.
>
> add_library(XXX SHARED ...)
>
> --> predefine XXX_EXPORTS
>
> I manually set this prede
Hi
I have a problem. After running CMake (VS 2003/2008 project) there's always a
EXPORT preprocessor define in my project setting that I don't need.
add_library(XXX SHARED ...)
--> predefine XXX_EXPORTS
I manually set this predefine in a correct way (means in upper case!). CMake
generate somet
42 matches
Mail list logo
