Under what circumstances does cmake place a fixup_bundle command in
dependencies.cmake? I've got a problem where fixup_bundle is being created
without reference to DESTDIR, and install fails when DESTDIR is used.
This is the generated dependencies.cmake file:
function(gp_item_default_embedded_pat
--
> From: CMake [cmake-boun...@cmake.org] on behalf of Waldo Valenzuela via CMake
> [cmake@cmake.org]
> Sent: Wednesday, December 13, 2017 11:15 AM
> To: Miklos Espak
> Cc: cmake@cmake.org
> Subject: Re: [CMake] CMake fixup_bundle for ubuntu 16.04
CMake
> [cmake@cmake.org]
> Sent: Wednesday, December 13, 2017 11:15 AM
> To: Miklos Espak
> Cc: cmake@cmake.org
> Subject: Re: [CMake] CMake fixup_bundle for ubuntu 16.04
>
> Dear Miklos,
>
> thanks for the email, and your suggestions, but the problem with fixup_bundle
] on behalf of Waldo Valenzuela via CMake
[cmake@cmake.org]
Sent: Wednesday, December 13, 2017 11:15 AM
To: Miklos Espak
Cc: cmake@cmake.org
Subject: Re: [CMake] CMake fixup_bundle for ubuntu 16.04
Dear Miklos,
thanks for the email, and your suggestions, but the problem with fixup_bundle
in u
Dear Konstantin,
Thanks for the email, yes you are right, I was looking this tool time ago, but
the fixup_bundle is just a part of the bigger problem, meaning if I want to
create a DEB package with CMake/CPack, how I could tell CPACK to use
linuxdeployqt, in runtime.
CMake/CPack in windows
13.12.2017, 22:16, "Waldo Valenzuela via CMake" :Dear Miklos, thanks for the email, and your suggestions, but the problem with fixup_bundle in ubuntu is that is not fixing the libraries locations from the executables meaning: if I execute the idd command like this “ idd ./app” where “app” is the
Dear Miklos,
thanks for the email, and your suggestions, but the problem with fixup_bundle
in ubuntu is that is not fixing the libraries locations from the executables
meaning:
if I execute the idd command like this “ idd ./app” where “app” is the
executable, the locations of the library is st
Hi,
you need to add the directory where the Qt libs have been installed (along
with your application binaries) to the LD_LIBRARY_PATH. In your case it is
'/home/waldo/Developer/install/Release/bratumia/bin/', as I see.
Also, you do *not* need to add the Qt plugin directories to the library
path.
Dear All,
I am working on a multi-platform desktop app with Qt5-VTK8, on Windows and Mac
no problem to created the standalone app, but in Ubuntu 16.04 I have several
problems.
I am using CodeBlocks to compile and run the app, and from CodeBlocks when I
run the app there is no problem, it work
Hi,
I'd like to package a simple application on linux. One main executable, one
shared lib, a few Qt shared libs and the xcb platform plugin.
I could package the app, but I can launch the it only if I set the
LD_LIBRARY_PATH manually, or with a wrapper script that does that.
Moreover, all the dep
Hello,
I have found a reasonable workaround, override the call to
fixup_bundle_item (called by fixup_bundle) and mark the file as writable:
install(CODE "
INCLUDE (BundleUtilities)
macro (fixup_bundle_item resolved_embedded_item exepath dirs)
message (\"Making writable: \${resolv
Hello,
We use perforce for our source control system, which has a typical
configuration where files need to be explicitly checked out prior to them
being changed. If they are not checked the files are marked as read only.
When trying to use fixup_bundle with a dylib in the perforce depot it
fails
A multiple folder approach will be very difficult.
The basic assumptions are:
- On Windows, the "one executable path" is the destination path to
which to copy all of the DLLs that need to be copied, so they all end
up in the same directory. (You'd have to have multiple copies in
multiple location
FYI verifying_app failed with main.exe failed (3.4.3) because toptool
depends on topdool.dll located only in toptoolfolder. The workaround is to
include toptoolfolder in libs folder for fixup_bundle(main.exe...)
David your answer was helpful to me. I know it's an expected behavior.
Would a patch
Indeed I was lucky : It worked with 3.3.1 but not anymore with 3.4.3..
I've got a strang bug with one .NET dll generated near a tool :
CMake Error at C:/Program Files
(x86)/CMake/share/cmake-3.4/Modules/GetPrerequisites.cmake:798 (message):
106>C:/Program Files (x86)/Microsoft Visual Studio
12
It was designed originally with the assumption that all the
executables in a bundle are in the same directory. If you violate that
assumption, I don't think you can count on it to do the right thing
100% of the time.
If it works for you calling it multiple times with deepest first, then
maybe you
Hello
I'd like to discuss a problem I encountered today with the very useful
module BundleUtilities
We have an application on Windows with one main exe file in the top folder
and a few other exe in subdirectories, like that :
applicationfolder \
| main.exe
Hi all,
Does fixup_bundle() from BundleUtiltites works on linux in a similar
fashion as in OSX. Currently calling fixup_bundle on a .app folder with
some search dirs and libs it will scan the dependencies and produce a
portable package.
Is that possible in linux? I mean to generate distribution i
fixup_bundle can't resolve dynamic libraries with non-absolute
install_names. I'm linking my macosx cmake project against an sdk inside an
application bundle, the sdk libraries are relative to the application
bundle configuration. It seems as if the fixup_bundle uses the install name
even if it's n
I'm running fixup_bundle on macosx to fix up bundles and make them
standalone for distribution. I've got mostly Qt libraries and different
internal and external dependencies.
For some reason ALL dependencies except for Frameworks are copied into the
program.app/Contents/MacOS directory, any chance
When I use fixup_bundle as follows, I end up with all the dependent
dylibs under "App/.../MacOS" instead of "App/.../Libraries". How do I
make fixup_bundle copy the dependencies into the Libraries dir and fix
paths accordingly?
fixup_bundle(\"${install_location}/Applications/paraview.app\" \"\"
\"
p.s. This is with CMake 2.8.8.
Utkarsh
On Sun, Aug 19, 2012 at 11:42 AM, Utkarsh Ayachit
wrote:
> When I use fixup_bundle as follows, I end up with all the dependent
> dylibs under "App/.../MacOS" instead of "App/.../Libraries". How do I
> make fixup_bundle copy the dependencies into the Librari
I am trying to use the CMake function FIXUP_BUNDLE to fix up an application
bundle, but am getting install-time warnings and for lack of better
terminology, not a fixed-up bundle.
The installed bundle has the right structure, but the frameworks it uses
aren't correctly copied in. Only each framewo
Turns out that ImageMagick is only used by test routines in my
program. I just comment out those routines in CMakeLists.txt and the
main program builds and works fine. I don't have to worry about OpenCL
anymore.
I think this is ImageMagick's fault. If I need this library in the
future, I'll probab
It seems that this library is ONLY installed with Xcode which leads me to
believe that libclparser.dylib should ONLY be used during development and is
NOT a deployable library. Yes there are all sorts of ideas about copying it
from Snow Leopard but there are both technical and legal issues surro
My Lion has OpenCL framework too. But if you go down the path, there
is no 'libclparser.dylib' in
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/,
while it exits in Snow Leopard.
And by googling ImageMagick and libclparser.dylib, I found people
having this issue as well. The solu
You have a bad install of Lion (OS X 10.7.x). I just checked 3 different Lion
machines and ALL have OpenCL.framework installed. So I would suspect your Lion
Machine. Lion uses OpenCL for lots of system level calls so a Lion Install
without OpenCL is just plain Broken.
__
I have Lion 10.7.4 on my laptop and I do have an OpenCL.framework in
"/System/Library/Frameworks/OpenCL.framework/"
So the real question is: why doesn't it just work for you? Because it
should work without you having to copy the OpenCL framework into your
bundle.
Especially if the OpenCL.framewor
Sorry I forgot to mention what the framework is. I believe the OpenCL
framework is from MacOS since I checked two Snow Leopard machines and
both have the framework.
I am building my program in Snow Leopard. The program uses a library
called 'ImageMagick', which uses the OpenCL framework. In Snow
L
If you compile/install these 3rd party libraries yourself, and compile against
them, then they are automatically recognized as non-system libraries. That's
the approach I take instead of trying to overload the behavior to treat some
system libraries as non-system ones.
Clint
On Tuesday, May
I too am curios as to why you need to copy ANYTHING from /System/Frameworks.
Typically if a framework is in there then it is installed on OS X BY Apple. If
you are deploying your application to an OS X machine that does NOT have this
file then the version of the operating system (OS X) will NOT
My previous email was your first hint that this might not be a good idea.
This error message is the second hint that this might not be a good idea.
You can try setting "BU_COPY_FULL_FRAMEWORK_CONTENTS" to ON before calling
fixup_bundle. That will recursively copy the framework into the bundle
rat
After setting the framework type to 'other', the framework structure
is copied into my bundle, including the file OpenCL, but missing
libclparser.dylib.
And I got the following errors:
CPack: Create package using DragNDrop
CPack: Install projects
CPack: - Run preinstall target for: CISMM_VIDEO
CP
Yes, it's possible. But I would only advise it if you do it on a
per-framework basis, you built & installed it yourself, and you know for
certain that the framework in question works fine when moved from its
"/System/Library" location.
Is this an OpenCL that you built yourself, or did it come from
Thanks, David. It works!
Is it possible to do the other way around?
I want fixup_bundle() to treat
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libclparser.dylib
as an external library instead of a system lib. I looked at functions
in BundleUtilities.cmake and GetPrerequisites.
Rather than just doing a "fixup_bundle" as an INSTALL(CODE snippet, put it
in a separate CMake script, and use install(SCRIPT to execute it. You can
configure the script with configure_file if you need to put stuff in it
that depends on CMake variables.
Then, in your script:
# Define the functi
Thanks, this is exactly what I need.
Just one question. Why the function gp_resolved_file_type_override()
cannot be seen if it is implemented in my project's CMakeLists.txt? I
have to add it in GetPrerequisite.cmake module, but that's not good.
Thanks,
Joe
On Mon, May 7, 2012 at 11:04 AM, David
/usr/X11/lib/libglut.dylib should probably be considered a "system
library" that is not included in your final bundle.
Therefore, all users of your application will have to have the Mac OS
X version of X installed and available in order to run your program.
(Is that all Macs nowadays anyway...?)
Hi,
I use CMake to create an installer for a Mac program which uses GLUT.
The GLUT library that the program links against with is
/usr/X11/lib/libglut.dylib.
When I use fixup_bundle() to create an installer, I get the following
error message:
install_name_tool: changing install names or rpaths c
Thanks, this way works.
Ogre framework is pre-fixed up because it's from Ogre SDK, i.e. should be ready
for redistribution, I think.
On 25.01.2012, at 16:00, David Cole wrote:
>
>
> On Wednesday, January 25, 2012, Nikolay Kasyanov wrote:
> > Already tried, doesn't help.
> > example of output:
On Wednesday, January 25, 2012, Nikolay Kasyanov wrote:
> Already tried, doesn't help.
> example of output:
> warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' is not
absolute...
> warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre'
Already tried, doesn't help.
example of output:
warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' is not
absolute...
warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' does not
exist...
/usr/bin/otool: can't open file:
@executa
I think you need to feed BundleUtilities another argument that lists where to
find the ogre frameworks. I think.
___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.
Hi,
I'm trying to use fixup_bundle on OS X.
I had following problem with some of my dependencies (Ogre game engine & OIS):
they already have @executable_path in it (so, they already fixed up), so in my
executable there is no absolute path to library, so fixup_bundle cannot find &
copy Ogre's fra
Hi all,
We develop a cmake-based application.
We create several libraries which are linked to VTK and ITK libraries.
ADD_LIBRARY( *QGoGui*
${QGoGUILIB_SRC}
${QGoGUILIB_MOC}
${QGoGUI_QRC}
)
SET( QGoGUI_LIBS
ITKStatistics
...
)
TARGET_LINK_LIBRARIES( *QGoGui*
${QGoGUI_LIBS}
)
IN
hi all,
i am currently trying to adapt a cmake build system to build an osx app.
the specific code is:
INSTALL(CODE "
include(BundleUtilities)
fixup_bundle(\"${CMAKE_CURRENT_BINARY_DIR}/${myappbundlename}.app\" \"\"
\"${CMAKE_CURRENT_BINARY_DIR}\")
"
COMPONENT Runtime)
however it d
On Tue, Jan 11, 2011 at 11:00 PM, David Cole wrote:
> On Tue, Jan 11, 2011 at 4:21 PM, Crni Gorac wrote:
>>
>> [ ... ]
>>
>> I hope you guys don't mind if I jump in and re-ask related question I
>> posted couple days ago (I'm sure Michael will soon face the same
>> problem, if he's building als
On Tue, Jan 11, 2011 at 4:21 PM, Crni Gorac wrote:
> On Tue, Jan 11, 2011 at 6:22 PM, David Cole
> wrote:
> > On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
> > wrote:
> >>
> >> This is wonderful and I am making progress but I have a few more
> >> questions. Assume I am using CMake 2.8.3 (as
On Tue, Jan 11, 2011 at 6:22 PM, David Cole wrote:
> On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
> wrote:
>>
>> This is wonderful and I am making progress but I have a few more
>> questions. Assume I am using CMake 2.8.3 (as it will become the
>> requirement).
>>
>> For external Dylibs and
On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> This is wonderful and I am making progress but I have a few more questions.
> Assume I am using CMake 2.8.3 (as it will become the requirement).
>
> For external Dylibs and frameworks that my project depends
This is wonderful and I am making progress but I have a few more questions.
Assume I am using CMake 2.8.3 (as it will become the requirement).
For external Dylibs and frameworks that my project depends on will the new way
that bundle utilities work still copy the frameworks (like Qt frameworks
On Tue, Jan 11, 2011 at 10:31 AM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> Thanks for the explanation David it really helps to narrow down what might
> be going on. Couple of comments. Starting fresh this morning everything
> seems to be working correctly after simply deleting the b
Thanks for the explanation David it really helps to narrow down what might be
going on. Couple of comments. Starting fresh this morning everything seems to
be working correctly after simply deleting the build folder and starting over.
So maybe I had a stale cmake variable floating around.
Also
Do you get different results if you use CMake from git 'master' or 'next' ??
(Or CMake 2.8.2...?)
In 2.8.3, there was a change introduced that caused problems in *some*
projects. I suspect your project is one of them.
This commit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c2895f48a4e79af
And just to follow up a bit with something else, I added the following bit of
cmake code for the 2 libraries MXADataModel and AIMLib:
SET_TARGET_PROPERTIES(${targetName}
PROPERTIES
LINK_FLAGS "-current_version ${${CMP_PROJECT_NAME}_VERSION}
-compatibility_version ${${CMP_PROJECT_NAME}_VERS
CMake 2.8.3, OS X 10.6.6, Makefiles
I am attempting to use fixup_bundle() to create my OS X app bundle. The issue I
am running into is that under a certain case some common libraries that get
built by the project are not being resolved correctly. Here goes the
explanation:
I have a project "IP
I'm interested in this too. My CPack script is limping along now, but the
resulting bundle yields reams of log messages like:
1/6/11 5:50:49 PM [0x0-0x2d42d4].myspp[23814] objc[23814]: Class
QCocoaColorPanelDelegate is implemented in both
/Users/kcjones/projects/myspp/build/_CPack_Pa
Have CPack setup working great on my Qt-based project - fixup_bundle()
is able to find all required Qt libraries, together with needed
plugins, and include them into installer. However, these libraries
and plugin files are not stripped, so the resulting installer file is
rather large, and I'd real
That sounds fine for now, thanks.
But what would you do if you had multiple gui apps?
On Fri, Dec 31, 2010 at 11:21 AM, David Cole wrote:
> Another alternative is to put your command line executables into the
> bundle on the Mac, and then they'll be fixed up, too. One caveat is
> that the direct
Another alternative is to put your command line executables into the
bundle on the Mac, and then they'll be fixed up, too. One caveat is
that the directory nesting level of the executables should all be the
same within the bundle so that "@exectuable_path/.." style references
work from each fixed u
I ended up creating a variation on fixup_bundle for command line tools
on OS X. It basically copies the app into "bin/" and depended
libraries into "lib/" and then runs install_name_tool on the
executables to make them find the libraries in "lib/".
You can find examples of the cmake code and confi
Hello all,
My project is sprouting new executables, and the simple use case of
using fixup_bundle is no longer sufficient. At the moment, I have:
1. A Qt-based gui application.
2. A command line application.
Both of these apps share common 3rdparty library dependencies (boost,
Qt, etc.). And I an
On Wednesday 28 April 2010 04:29:29 am Martin Guillon wrote:
> Hi,
>
> I am having problems using fixup_bundle with qt plugins
>
> I use that code
> install(CODE "
> # glob for previously installed qt plugins to include in fixup_bundle
>file(GLOB_RECURSE QTPLUGINS
>
> \"${${TA
This is what I use. Note that this gets "configured" by cmake first.
Pay Attention to the notes in the file as the use case is _very_
specific.
#- Start --
message (STATUS "# Starting OS X Bundle Fixup
--")
Hi,
I am having problems using fixup_bundle with qt plugins
I use that code
install(CODE "
# glob for previously installed qt plugins to include in fixup_bundle
file(GLOB_RECURSE QTPLUGINS
\"${${TARGET_NAME}_OUTPUTPLUGINSDIR}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\")
include(Bun
65 matches
Mail list logo
