On Sunday 22 July 2012 17:20:32 Michael Jackson wrote:
> I have a project very similar to yours and with a post installation script I
> was able to create symlinks in the .app bundle that point to the Qt
> frameworks and my own support libraries in folders outside of the .app
> package that the com
Hi all.
I try to set install/package a cmake project on MacOSX. Questions first,
please find the details below.
- does cmake support multiple .dylib in a single framework? (do Frameworks
support this at all?)
- does cmake support Umbrella Frameworks (umbrella Frameworks may contain
othe
On Friday 13 April 2012 20:21:39 Daniel Franke wrote:
> Consider:
> include (GNUInstallDirs)
> set (PREFIX $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_BINDIR})
> file (GLOB PLUGINS "${QT_PLUGINS_DIR}/imageformats/*.dll")
> install
Hi all.
I try to use DeployQt4(fixup_qt4_executable) to build a zip/nsis package that
includes all the dependencies of the executable. After some struggling I got
this working for `make install`, but `make package` still eludes me.
Consider:
include (GNUInstallDirs)
set (PREFIX $ENV{DESTDI
Hi Eric.
On Monday 18 July 2011 09:36:37 Eric Noulard wrote:
> http://public.kitware.com/Bug/view.php?id=11808
Thanks for the link.
> > Maybe I should have provided an example. At 3am, things start to get
> > fuzzy around the edges ...
> >
> > I defined a bunch of macros, e.g.
> >
> >myp
Hi Andreas.
On Sunday 17 July 2011 21:36:26 Andreas Mohr wrote:
> to me it sounds like all the effects can simply be described as
> happening due to including CPack way too early.
> Verdict: Don't Do That (tm)
Maybe. See below for more details.
> IMHO install stuff is ideally (i.e., usually) s
Hi all.
I try to build a NSIS package for a largish project with many components and a
plethora of local and imported binaries. One of the last steps would be to add
Start menu entries for the binaries of the selected components [*].
The problem I face: due to the size of the project, we abstr
On Tuesday, October 12, 2010, John Drescher wrote:
> On Tue, Oct 12, 2010 at 8:58 AM, Mr Shore wrote:
> > Can I restrict the scope so that this setting is only for one specific
> > target?
>
> If the targets are all in 1 CMakeLists.txt I am not sure how to do
> that. I am not saying its not possi
On Tuesday 10 August 2010 01:24:13 David Cole wrote:
> Or this variable prior to defining any targets:
> http://cmake.org/cmake/help/cmake-2-8-
docs.html#variable:CMAKE_RUNTIME_OUTPUT_DIRECTORY
>
> ...to put all the runtime (exe and dll) output files in the same directory
> with each other...
Dav
Hi all.
I wrote some unit tests for a library target in my project. A driver
application links the library and runs the tests. This works fine with
Makefile targets on Linux. With MinGW Makefiles on Windows, the driver
properly links, but when running `make test`, the system complains that it
On Friday, June 11, 2010, Martin Costabel wrote:
> -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=""
> -DCMAKE_OSX_SYSROOT:PATH="/"
Hi Martin,
thanks for the pointer!
set (CMAKE_OSX_ARCHITECTURES "")
in the main CMakeLists.txt did the trick. Phew :)
Cheers
Daniel
___
Hi all.
I got gcc-4.4.4 for target i386-apple-darwin9.8.0 from fink. First I used
cmake-2.6 (also from fink) and everything worked. Later, after an update to
cmake-2.8 (again, from fink), and trying to rebuild my package, I got:
f951: error: unrecognized command line option "-arch"
As
On Thursday 19 November 2009 09:46:29 Marcel Loose wrote:
> # --
> # join_arguments(var)
> #
> # Join the arguments in the (semi-colon separated) list VAR into one
> # space separated string. The string will be returned in the vari
Hi all,
I'd like to break overly long lines in CMakeLists.txt into something more
readable. But breaking a string into two as shown below generates a list,
which -- in this case -- breaks the compilation.
-- 8< --
if (${CMAKE_Fortran_COMPILER_ID} STREQUAL "GNU")
set (CMAKE_Fortran_FLAGS
Hi all,
I'm new to Mac, but would like to use cmake's capabilities to create a nice
installer/package for a project. I read up on Bundles on developer.apple.com
and I have a fair idea of what I'd need.
There are some command-line tools that should go to /usr/bin or /usr/local/bin
and one grap
On Wednesday 03 December 2008 11:28:02 Mathieu Malaterre wrote:
> > 2.
> > Fortran does not have any concept of preprocessing. However, by
> > convention, files with a capital suffix (.F, .FOR, .FPP, .F90, F03, ...)
> > are preprocessed, usually by a C-preprocessor.
>
> How do you do that on case-
Hi all.
After years of automake, I only recently starting looking into CMake. Setting
up a multi-language project (C/C++/Fortran) was simple and everything just
works. Impressive!
Two nitpicks/suggestions:
1.
As CheckCSourceCompiles and CheckCXXSourceCompiles macros are available, one
would
17 matches
Mail list logo