Am 20.04.2011 22:09, schrieb Alexander Neundorf:
On Wednesday 20 April 2011, Oliver Buchtala wrote:
Hi Alex,
...
What would you expect there ?
Some structure that gives me acces to the sources of the targets.
I suppose, you try to achieve this with sub-projects, but it does not
work
Hi all,
We've recently started generating (debian) packages with CPack and
discovered that handling library dependencies for particular
distributions was not as smooth as it can be. The *_DEPENDS string
just gets copied over to the final package so it puts all the burden
on the user side to
We've recently started generating (debian) packages with CPack and
discovered that handling library dependencies for particular
distributions was not as smooth as it can be. The *_DEPENDS string
just gets copied over to the final package so it puts all the burden
on the user side to manage
2011/4/22 Rosen Diankov rosen.dian...@gmail.com:
Hi all,
We've recently started generating (debian) packages with CPack and
discovered that handling library dependencies for particular
distributions was not as smooth as it can be. The *_DEPENDS string
just gets copied over to the final
2011/4/22 Rolf Eike Beer e...@sf-mail.de:
We've recently started generating (debian) packages with CPack and
discovered that handling library dependencies for particular
distributions was not as smooth as it can be. The *_DEPENDS string
just gets copied over to the final package so it puts all
Hi again,
I assume this is kind of tricky seen the number of answer. hehe
Just a quick summary of my situation and what I want to achieve :
Currently I can produce 'sfml-system.framework' for debug and release
configuration. I use something like this :
# add the install rule
# if Mac
Hi Guys,
You are right about shlibdeps, but this is not the whole story.
Debian source packages required build dependencies to be
preinstalled before cmake even runs. This tells each distribution what
it needs so that cmake can find it with find_package.
Afterwards, it isn't necessary to
I have created an executable like this:
add_executable(ImageCompleter ${AppSources})
target_link_libraries(ImageCompleter ${LibrariesAlwaysUsed})
INSTALL( TARGETS ImageCompleter
RUNTIME DESTINATION ${INSTALL_DIR} )
When I run the one that is created with 'make', it works fine.
On Fri, Apr 22, 2011 at 9:48 AM, David Doria daviddo...@gmail.com wrote:
I have created an executable like this:
add_executable(ImageCompleter ${AppSources})
target_link_libraries(ImageCompleter ${LibrariesAlwaysUsed})
INSTALL( TARGETS ImageCompleter
RUNTIME DESTINATION ${INSTALL_DIR}
I think the CMake page on RPATHs might be what you are looking for.
http://www.cmake.org/Wiki/CMake_RPATH_handling
Marcus
Yea I read that, but I didn't really follow/see how to fix this
problem. Surely there is a just copy the executable option?
David
Hi all,
We just finished a new debian source package generator script for cmake:
https://openrave.svn.sourceforge.net/svnroot/openrave/trunk/modules-cmake/DebSourcePPA.cmake
This is based on the initial UploadPPA.cmake file (
http://purplekarrot.net/blog/dputCMake.html ) by Daniel Pfeifer,
On Fri, Apr 22, 2011 at 9:57 AM, David Doria daviddo...@gmail.com wrote:
I think the CMake page on RPATHs might be what you are looking for.
http://www.cmake.org/Wiki/CMake_RPATH_handling
Yea I read that, but I didn't really follow/see how to fix this
problem. Surely there is a just copy the
2011/4/22 Rosen Diankov rosen.dian...@gmail.com:
Hi Guys,
You are right about shlibdeps, but this is not the whole story.
Debian source packages required build dependencies to be
preinstalled before cmake even runs. This tells each distribution what
it needs so that cmake can find it with
Hi Eric,
Before I start running things, basically the script sets
CPACK_DEBIAN_PACKAGE_DEPENDS right? What does this effect have on
cpack?
Also, If we're generating debian source packages, i'm not sure if it
is a good idea to set DISTRO_CODENAME, DISTRO_RELEASE, AND DISTRO_ID
inside the cmake
Hi all,
There was a problem with the previous script on certain versions of
tar. I'm attaching a new file that fixes it.
rosen,
2011/4/22 Rosen Diankov rosen.dian...@gmail.com:
Hi all,
We just finished a new debian source package generator script for cmake:
Am working on CMake based project, using CPack for building
installers. On Windows, I'm using NSIS back-end for CPack. I'm
working now on a feature request, consisting of signing the
application executable itself, as well as installer exectuable, using
my company code signing certificate.
2011/4/22 Rosen Diankov rosen.dian...@gmail.com:
Hi Eric,
Before I start running things, basically the script sets
CPACK_DEBIAN_PACKAGE_DEPENDS right? What does this effect have on
cpack?
On CPack generic part none but the CPack Debian generator use it
when building the binary debian package
Hi Eric,
Thanks for the response. In another email to cmake.org, I sent a
DebSourcePPA.cmake file that shows what i'm doing to generate deb
source packages.
Your script sets CPACK_DEBIAN_PACKAGE_DEPENDS to Ubuntu-dep, so I
was confused how that adds the correct dependencies... what does a
user
Hi
Do we have something similar to BundleUtilities for Frameworks ?
Best Regards
Guillaume
On Wed, Apr 20, 2011 at 9:48 PM, David Cole david.c...@kitware.com wrote:
On Wed, Apr 20, 2011 at 11:38 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 97ed208db6818400933fd2d5e8b1eb5608a8a5f6 (commit)
from
20 matches
Mail list logo
