Re: [CMake] Find module for the Subversion API
On Thu, Aug 13, 2009 at 4:32 PM, Robert Dailey rcdai...@gmail.com wrote:
In case no one knows this, the Subversion API requires over 10 separate
dependencies in order to build it into a fully-functional API. In other
words, there are certain dependencies that are optional, but I'm assuming a
case where they are all required as far as the Find module is concerned
(i.e. it can't assume the user won't use certain features and thus is not
allowed to omit those dependencies from its search). A list of a few that it
requires:
apr
apr-util
apr-iconv
neon
berkeleydb
openssl
There are many others it depends on. I had considered writing find modules
for all of these, but there is one major thing stopping me. I do not have
the knowledge or resources to write find modules for all of these myself. I
would love more than anything to be able to write find modules for these and
contribute them to the community. I have no experience with the MAC and no
development experience with Linux. Only on Windows. Additionally, some of
these libraries are so tricky to build on Windows that it would be difficult
to setup a reliable way for the Find module to find these libraries.
What I've been doing is maintaining a fixed list of libraries in my CMake
scripts and just moving those dependencies in a predictable location so that
I can hard-code the paths to those libraries and includes into my CMake
projects. What would you guys do in this situation? I obviously could not
reliably create find modules for these, given the reasons above. But also
because there is no bold standard for find modules. Even when you do know
what needs to be done to find these libraries, you have to know a standard
way of setting it up that is acceptable to the CMake project.
Nothing is ever easy. :)
Generally what I do is write my find modules to work out of the box on
Linux. Since nobody wants to find every library/include directory on
Windows manually, generally what we do is to keep dependencies per compiler
in a folder checked into CM. Then we manipulate CMAKE_PREFIX_PATH to assist
in finding all of the stuff (preserving it's original value so it can still
be used via -D or cache).
Depending on the dependency, we also find some of our Linux dependencies in
the same way.
===
set(DEPS_PATH CACHE PATH Path to the dependencies directory)
set(orig_CMAKE_PREFIX_PATH ${CMAKE_PREFIX_PATH})
# Wrap calls to each find_package() with the path hint
if(DEPS_PATH AND WIN32)
list(APPEND CMAKE_PREFIX_PATH ${DEPS_PATH}/foo-1.2.3)
endif()
find_package(Foo)
set(CMAKE_PREFIX_PATH ${orig_CMAKE_PREFIX_PATH})
===
--
Philip Lowman
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake .
Tested with cmake 2.6.4 on linux. It is the case with all my projects, probably we don't need a test case. The mentioned actions simply modify CMakeCache.txt (check with your running projects), while they should not, should they? Dominik Eric Noulard wrote: 2009/8/13 Dominik Szczerba domi...@itis.ethz.ch: Once again: I am calling 'ccmake .', 'cmake-gui.' or 'make edit_cache' just to inspect the build settings. I quit with no changes saved. Then 'make' rebuilds the project, which is an obvious bug or *extremely* unexpected behavior. Which CMake version? Which OS? etc... May be you can give us a reproducable testcase? -- d o m i n i k s z c z e r b a , p h d . . . . . . . . . . . c o m p u t a t i o n a l l i f e s c i e n c e g r o u p . . . . . . . i t ' i s r e s e a r c h f o u n d a t i o n . . . . . . . . . . . . . . . . . . . . http://www.itis.ethz.ch ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake .
I also noticed that ccmake always modifies the cache. But that in
itself should NOT cause a complete rebuild of your project. On the
next `make' it should only re-configure and regenerate the build
system, and then print a list of all targets as Make checks them all,
but nothing should be compiled or linked.
Is it possible that in your CMake code you unconditionally modify
(e.g. re-create) a central header file, such as config.h? If you do
that, Make will think everything else is out-of-date and recompile.
But if you either use configure_file or add_custom_command, things
should be fine. file(WRITE ${CMAKE_BINARY_DIR}/config.h ...) would
cause troubles!
Michael
On 14. Aug, 2009, at 9:20, Dominik Szczerba wrote:
Tested with cmake 2.6.4 on linux.
It is the case with all my projects, probably we don't need a test
case.
The mentioned actions simply modify CMakeCache.txt (check with your
running projects), while they should not, should they?
Dominik
Eric Noulard wrote:
2009/8/13 Dominik Szczerba domi...@itis.ethz.ch:
Once again: I am calling 'ccmake .', 'cmake-gui.' or 'make
edit_cache' just
to inspect the build settings. I quit with no changes saved.
Then 'make' rebuilds the project, which is an obvious bug or
*extremely*
unexpected behavior.
Which CMake version? Which OS? etc...
May be you can give us a reproducable testcase?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack Error: Not enough items on list: CPACK_INSTALL_CMAKE_PROJECTS
Your post solved it!
I use an environment variable for project name, which is set only for the
process running CMake, not CPack. So when i substitute this variable with a
string, it is ok.
Thank you!
Karl
From: David Cole [mailto:david.c...@kitware.com]
Sent: 13. august 2009 17:38
To: Karl Reite
Cc: cmake@cmake.org
Subject: Re: [CMake] CPack Error: Not enough items on list:
CPACK_INSTALL_CMAKE_PROJECTS
From CPack.cmake :
cpack_set_if_not_set(CPACK_INSTALL_CMAKE_PROJECTS
${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};ALL;/)
Looks like you do not have a PROJECT statement in your top level
CMakeLists.txt file. If you did, the second component of
CPACK_INSTALL_CMAKE_PROJECTS would not be the empty string.
HTH,
David
On Thu, Aug 13, 2009 at 8:50 AM, Karl Reite
karl.j.re...@sintef.nomailto:karl.j.re...@sintef.no wrote:
Hi,
My problem is that I can not get CPack to create an installer for my project. I
have done this before with success, but this time I can not figure out the
problem.
I work in Visual Studio 2005 SP1. The project compiles without errors. When i
try to build the PACKAGE project (this calls CPack), I get the error:
CPack Error: Not enough items on list: CPACK_INSTALL_CMAKE_PROJECTS.
CPACK_INSTALL_CMAKE_PROJECTS should hold quadruplet of install directory,
install project name, install component, and install subdirectory.
I have tried to remove all install commands and CPack commands except
INCLUDE(CPack), but still the same error. I notice that the file
CPackConfig.cmake contains the line:
SET(CPACK_INSTALL_CMAKE_PROJECTS
C:/_work/_SSR/IPR/projects/!Demo/build/dynamicvis;;ALL;/)
But the file CpackSourceConfig.cmake contains the coresponding line
SET(CPACK_INSTALL_CMAKE_PROJECTS )
I am hoping someone may have a clue to what is causing this.
Thanks,
Karl
___
Powered by www.kitware.comhttp://www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Useful feature: join_arguments() ?
Hi all, I was wondering whether it would be useful if join_arguments() were added to CMake (not as a macro, but as a built-in command), where join_arguments() does the oppositie of separate_arguments(); i.e. create a space separated string of the elements of a list. I know that several people have brewn their join_arguments() macro (or whatever they called it) in the past, and so did I. But it feels like such a fundamental operation that I think it deserves to be a built-in command. Best regards, Marcel Loose. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake .
2009/8/14 Michael Wild them...@gmail.com:
I also noticed that ccmake always modifies the cache. But that in itself
should NOT cause a complete rebuild of your project. On the next `make' it
should only re-configure and regenerate the build system, and then print a
list of all targets as Make checks them all, but nothing should be compiled
or linked.
Agreed same here.
CMake 2.6.4 on Linux.
I should add that on my side ONLY ccmake and make edit_cache do
unconditionnally modify the cache.
cmake-gui does NOT do that, Dominik can you confirm that your cmake-gui
does modify the cache?
The modification seems to concern, this var:
//Advanced flag for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1
ccmake and make edit_cache do suppress this var unconditionnally
and rewrite the CMakeCache.txt
Is it possible that in your CMake code you unconditionally modify (e.g.
re-create) a central header file, such as config.h? If you do that, Make
will think everything else is out-of-date and recompile. But if you either
use configure_file or add_custom_command, things should be fine. file(WRITE
${CMAKE_BINARY_DIR}/config.h ...) would cause troubles!
That may be the reason but I think Dominik is right the unconditionnal
modification
of the CMakeCache.txt is not an expected behavior and deserve a bug report.
Dominik would you like to file the bug report?
http://public.kitware.com/Bug/main_page.php
In the meantime, I think cmake-gui seems to be more CMakeCache.txt friendly
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] How to set suid for an executable with CMake and CPack?
Another question, how to set the owner of files for MacOSX PackageMaker packages? 2009/8/14 Dong Tiger idlecat...@gmail.com fakeroot make package solved my problem. 2009/8/10 Eric Noulard eric.noul...@gmail.com 2009/8/10 Dong Tiger idlecat...@gmail.com: Thanks. I'll take a look although I feel CPack should be able to take care of that automatically. That's your point of view and I respect it but... Especially the owner of files should not be the user who builds the package. this is precisely the jobs of the packager (or the final packaging tool, rpm, dpkg etc...) to chose that kind of thing. How would CPack decide to change ownership? root may be an option for your particular package and distros but other choices may be valid too. Moreover giving ownership to root mostly need to be root unless you use something like fakeroot (already pointed-out previously). That said some CPack generator (DEB, RPM) mostly relies on underlying tools (dpkg, rpmbuild) so the CPACK_DEBIAN_xxx or CPACK_RPM_xxx are used to control actual feature of the underlying tool. See: http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29 http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#RPM_.28Unix_Only.29 If you know the dpkg specific features or file from DEB format which should be used to tune the package build, do not hesitate to propose patches. Concerned file for CPack Deb generator are CMake/Source/CPack/cmCPackDebGenerator.cxx CMake/Source/CPack/cmCPackDebGenerator.h CMake/Modules/CPackDeb.cmake -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] .vfproj with cmake
Hi, I cannot create a Visual Frotran Project using Intel Fortran 11.0 on Visual Studio 9. When I press configure on the CMake GUI I have the following error: CMake Error at C:/PRogram Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestFortranCompiler.cmake:25 (MESSAGE): The Fortran compiler C:/Program Files/Intel/Compiler/11.0/061/fortran/Bin/IA32/ifort.exe is not able to compile a simple test program. My program is a simple Hello world program: program Console5 implicit none print *, 'Hello World' end program Console5 and my CmakeLists is: PROJECT(HelloW Fortran) add_executable (HelloW Console5.f90) Could you please help me with this problem. Créez votre adresse électronique prenom@laposte.net 1 Go d'espace de stockage, anti-spam et anti-virus intégrés. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] .vfproj with cmake
lokmane.abbas-turki wrote: Hi, I cannot create a Visual Frotran Project using Intel Fortran 11.0 on Visual Studio 9. When I press configure on the CMake GUI I have the following error: CMake Error at C:/PRogram Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestFortranCompiler.cmake:25 (MESSAGE): The Fortran compiler C:/Program Files/Intel/Compiler/11.0/061/fortran/Bin/IA32/ifort.exe is not able to compile a simple test program. What is in the CMakeError.log file? -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ccmake .
Filed under:
http://public.kitware.com/Bug/view.php?id=9418
Many thanks Eric and Michael.
PS. Indeed, cmake-gui does NOT modify the cache in vein, which is what I
would expect.
Dominik
Eric Noulard wrote:
2009/8/14 Michael Wild them...@gmail.com:
I also noticed that ccmake always modifies the cache. But that in itself
should NOT cause a complete rebuild of your project. On the next `make' it
should only re-configure and regenerate the build system, and then print a
list of all targets as Make checks them all, but nothing should be compiled
or linked.
Agreed same here.
CMake 2.6.4 on Linux.
I should add that on my side ONLY ccmake and make edit_cache do
unconditionnally modify the cache.
cmake-gui does NOT do that, Dominik can you confirm that your cmake-gui
does modify the cache?
The modification seems to concern, this var:
//Advanced flag for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1
ccmake and make edit_cache do suppress this var unconditionnally
and rewrite the CMakeCache.txt
Is it possible that in your CMake code you unconditionally modify (e.g.
re-create) a central header file, such as config.h? If you do that, Make
will think everything else is out-of-date and recompile. But if you either
use configure_file or add_custom_command, things should be fine. file(WRITE
${CMAKE_BINARY_DIR}/config.h ...) would cause troubles!
That may be the reason but I think Dominik is right the unconditionnal
modification
of the CMakeCache.txt is not an expected behavior and deserve a bug report.
Dominik would you like to file the bug report?
http://public.kitware.com/Bug/main_page.php
In the meantime, I think cmake-gui seems to be more CMakeCache.txt friendly
--
d o m i n i k s z c z e r b a , p h d . . . . . . . . . . .
c o m p u t a t i o n a l l i f e s c i e n c e g r o u p
. . . . . . . i t ' i s r e s e a r c h f o u n d a t i o n
. . . . . . . . . . . . . . . . . . . . http://www.itis.ethz.ch
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Tried this, ABCD_LIBRARY gets the correct path, but for some reason,
target_link_libraries likes to convert it to -Lxxx -lyyy on the link
line. (I've previously typed the name of the file directly into the
target_link_libraries() command too)
I'm seeing some of these properties like EXTERNAL_OBJECT, but it's not
really working either.
set_source_files_properties(
abcd.so
PROPERTIES
EXTERNAL_OBJECT true
GENERATED true
LOCATION /path/to/so
)
add_executable( sfitqd
sfitqd.cc
abcd.so
)
Michael Wild wrote:
Perhaps something like this:
set( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
set( CMAKE_SHARED_LIBRARY_PREFIX )
find_library( ABCD_LIBRARY abcd )
set( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
target_link_libraries( a.out ${ABCD_LIBRARY} )
HTH
Michael
On 14. Aug, 2009, at 0:16, Clinton Stimpson wrote:
How about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like abcd.so
instead of libabcd.so. Putting the name in
target_link_libraries( a.out abcd.so )
doesn't work because this generates -labcd on the link line and then
ld can't find it. What do I need to do to get this to link?
Thanks!
Kenny
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
What version of CMake are you using? Anything before 2.6 used to do
this, newer versions shouldn't.
Michael
On 14. Aug, 2009, at 18:23, Kenneth Chang wrote:
Tried this, ABCD_LIBRARY gets the correct path, but for some reason,
target_link_libraries likes to convert it to -Lxxx -lyyy on the link
line. (I've previously typed the name of the file directly into the
target_link_libraries() command too)
I'm seeing some of these properties like EXTERNAL_OBJECT, but it's
not really working either.
set_source_files_properties(
abcd.so
PROPERTIES
EXTERNAL_OBJECT true
GENERATED true
LOCATION /path/to/so
)
add_executable( sfitqd
sfitqd.cc
abcd.so
)
Michael Wild wrote:
Perhaps something like this:
set( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
set( CMAKE_SHARED_LIBRARY_PREFIX )
find_library( ABCD_LIBRARY abcd )
set( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
target_link_libraries( a.out ${ABCD_LIBRARY} )
HTH
Michael
On 14. Aug, 2009, at 0:16, Clinton Stimpson wrote:
How about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like abcd.so
instead of libabcd.so. Putting the name in
target_link_libraries( a.out abcd.so )
doesn't work because this generates -labcd on the link line and
then ld can't find it. What do I need to do to get this to link?
Thanks!
Kenny
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
kch...@fiji:~$ cmake --version
cmake version 2.6-patch 2
Michael Wild wrote:
What version of CMake are you using? Anything before 2.6 used to do
this, newer versions shouldn't.
Michael
On 14. Aug, 2009, at 18:23, Kenneth Chang wrote:
Tried this, ABCD_LIBRARY gets the correct path, but for some reason,
target_link_libraries likes to convert it to -Lxxx -lyyy on the link
line. (I've previously typed the name of the file directly into the
target_link_libraries() command too)
I'm seeing some of these properties like EXTERNAL_OBJECT, but it's
not really working either.
set_source_files_properties(
abcd.so
PROPERTIES
EXTERNAL_OBJECT true
GENERATED true
LOCATION /path/to/so
)
add_executable( sfitqd
sfitqd.cc
abcd.so
)
Michael Wild wrote:
Perhaps something like this:
set( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
set( CMAKE_SHARED_LIBRARY_PREFIX )
find_library( ABCD_LIBRARY abcd )
set( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
target_link_libraries( a.out ${ABCD_LIBRARY} )
HTH
Michael
On 14. Aug, 2009, at 0:16, Clinton Stimpson wrote:
How about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like abcd.so
instead of libabcd.so. Putting the name in
target_link_libraries( a.out abcd.so )
doesn't work because this generates -labcd on the link line and
then ld can't find it. What do I need to do to get this to link?
Thanks!
Kenny
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Try latest!
BTW I am doing such tricks for annoying bad-named stuff:
SET_SOURCE_FILES_PROPERTIES(
${FLEXLM_OBJECTS}
PROPERTIES
EXTERNAL_OBJECT true # if it should be compiled or only linked
GENERATED false # if the obj-files exist before build time
)
- Dominik
Kenneth Chang wrote:
kch...@fiji:~$ cmake --version
cmake version 2.6-patch 2
Michael Wild wrote:
What version of CMake are you using? Anything before 2.6 used to do
this, newer versions shouldn't.
Michael
On 14. Aug, 2009, at 18:23, Kenneth Chang wrote:
Tried this, ABCD_LIBRARY gets the correct path, but for some reason,
target_link_libraries likes to convert it to -Lxxx -lyyy on the link
line. (I've previously typed the name of the file directly into the
target_link_libraries() command too)
I'm seeing some of these properties like EXTERNAL_OBJECT, but it's
not really working either.
set_source_files_properties(
abcd.so
PROPERTIES
EXTERNAL_OBJECT true
GENERATED true
LOCATION /path/to/so
)
add_executable( sfitqd
sfitqd.cc
abcd.so
)
Michael Wild wrote:
Perhaps something like this:
set( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
set( CMAKE_SHARED_LIBRARY_PREFIX )
find_library( ABCD_LIBRARY abcd )
set( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
target_link_libraries( a.out ${ABCD_LIBRARY} )
HTH
Michael
On 14. Aug, 2009, at 0:16, Clinton Stimpson wrote:
How about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like abcd.so
instead of libabcd.so. Putting the name in
target_link_libraries( a.out abcd.so )
doesn't work because this generates -labcd on the link line and
then ld can't find it. What do I need to do to get this to link?
Thanks!
Kenny
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
d o m i n i k s z c z e r b a , p h d . . . . . . . . . . .
c o m p u t a t i o n a l l i f e s c i e n c e g r o u p
. . . . . . . i t ' i s r e s e a r c h f o u n d a t i o n
. . . . . . . . . . . . . . . . . . . . http://www.itis.ethz.ch
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] .vfproj with cmake
Please, find attached to this email the CMakeError.log file. Thank you. Lokman. Message du 14/08/09 14:17 De : Bill Hoffman A : lokmane.abbas-turki Copie à : cmake@cmake.org Objet : Re: [CMake] .vfproj with cmake lokmane.abbas-turki wrote: Hi, I cannot create a Visual Frotran Project using Intel Fortran 11.0 on Visual Studio 9. When I press configure on the CMake GUI I have the following error: CMake Error at C:/PRogram Files/CMake 2.6/share/cmake-2.6/Modules/CMakeTestFortranCompiler.cmake:25 (MESSAGE): The Fortran compiler C:/Program Files/Intel/Compiler/11.0/061/fortran/Bin/IA32/ifort.exe is not able to compile a simple test program. What is in the CMakeError.log file? -Bill Créez votre adresse électronique prenom@laposte.net 1 Go d'espace de stockage, anti-spam et anti-virus intégrés. CMakeError.log Description: Binary data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] DejaGNU.
A project has a large number of DejaGNU tests and it is unfeasible to translate them to CTest. So far I think it is possible to configure and drive DejaGNU from cmake for running all the test suite, but not parts or individual tests. Any experiences or advices on how to deal with DejaGNU from cmake is welcomed. -- Óscar Fuentes Desarrollo de Software ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Just downloaded 2.6.4, same behavior.
Do I have to mark the .so extension so it's recognized as a linkable item?
Kenny
Dominik Szczerba wrote:
Try latest!
BTW I am doing such tricks for annoying bad-named stuff:
SET_SOURCE_FILES_PROPERTIES(
${FLEXLM_OBJECTS}
PROPERTIES
EXTERNAL_OBJECT true # if it should be compiled or only linked
GENERATED false # if the obj-files exist before build time
)
- Dominik
Kenneth Chang wrote:
kch...@fiji:~$ cmake --version
cmake version 2.6-patch 2
Michael Wild wrote:
What version of CMake are you using? Anything before 2.6 used to do
this, newer versions shouldn't.
Michael
On 14. Aug, 2009, at 18:23, Kenneth Chang wrote:
Tried this, ABCD_LIBRARY gets the correct path, but for some
reason, target_link_libraries likes to convert it to -Lxxx -lyyy on
the link line. (I've previously typed the name of the file directly
into the target_link_libraries() command too)
I'm seeing some of these properties like EXTERNAL_OBJECT, but it's
not really working either.
set_source_files_properties(
abcd.so
PROPERTIES
EXTERNAL_OBJECT true
GENERATED true
LOCATION /path/to/so
)
add_executable( sfitqd
sfitqd.cc
abcd.so
)
Michael Wild wrote:
Perhaps something like this:
set( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
set( CMAKE_SHARED_LIBRARY_PREFIX )
find_library( ABCD_LIBRARY abcd )
set( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
target_link_libraries( a.out ${ABCD_LIBRARY} )
HTH
Michael
On 14. Aug, 2009, at 0:16, Clinton Stimpson wrote:
How about this:
target_link_libraries(a.out /path/to/abcd.so)
If you use find_library(), then you should be getting full names
already.
Clint
Kenneth Chang wrote:
Hi,
I have this third party library that has a .so named like
abcd.so instead of libabcd.so. Putting the name in
target_link_libraries( a.out abcd.so )
doesn't work because this generates -labcd on the link line and
then ld can't find it. What do I need to do to get this to link?
Thanks!
Kenny
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Kenneth Chang wrote: Just downloaded 2.6.4, same behavior. Do I have to mark the .so extension so it's recognized as a linkable item? Why not use target_link_libraries with a full path to the .so? -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
I did, then cmake broke the .so down into its component paths and library name, and used -Lpath -llibname, which caused the linker to look for path/liblibname.so -Kenny Bill Hoffman wrote: Kenneth Chang wrote: Just downloaded 2.6.4, same behavior. Do I have to mark the .so extension so it's recognized as a linkable item? Why not use target_link_libraries with a full path to the .so? -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
What does your cache entry say? When you did your testing, did you
always delete the cache? Otherwise you get strange effects...
Please show us the output of something like this in your CMakeLists.txt:
message( STATUS DEBUG: ABCD_LIBRARY = '${ABCD_LIBRARY}' )
and the link command you can see when doing a make VERBOSE=1.
Michael
On 14. Aug, 2009, at 22:25, Kenneth Chang wrote:
I did, then cmake broke the .so down into its component paths and
library name, and used -Lpath -llibname, which caused the linker
to look for path/liblibname.so
-Kenny
Bill Hoffman wrote:
Kenneth Chang wrote:
Just downloaded 2.6.4, same behavior.
Do I have to mark the .so extension so it's recognized as a
linkable item?
Why not use target_link_libraries with a full path to the .so?
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Kenneth Chang wrote: I did, then cmake broke the .so down into its component paths and library name, and used -Lpath -llibname, which caused the linker to look for path/liblibname.so It should not do that in 2.6.4, it should use the full path Do you have any policy warnings, or do you have the cmake minimum version set to something very old? -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] ENABLE_LANGUAGE(ASM_MASM) does not seem work correctly
I'm trying to compile a ASM file using cmake 2.6 (patch 4). I'm running visual
studio 2008, under 64-bit Vista. Neither Win32 or x64 build work.
I have a simple test app (attached), with a single CPP file and an asm file.
My cmakelists.txt looks like this (I have to include the .asm extension on the
asm file or I will get a cannot find source file error):
ENABLE_LANGUAGE(ASM_MASM)
PROJECT(AsmTest)
ADD_EXECUTABLE(AsmTest asmtest AsmTestFunc.asm)
On a win32 VS2008 command prompt the cmake step completes correctly, as shown
below, and the asm file is added to the project. But the custom build step for
the ASM file is completely empty, so the assembler is never run.
C:\testcode\asmtest\cmake_win32cmake -G Visual Studio 9 2008 ..
-- Found assembler: C:/Program Files (x86)/Microsoft Visual Studio
9.0/VC/bin/ml.exe
-- Loaded CMakeASM_MASMInformation - ASM_MASM support is still experimental,
please report issues
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio
9.0/VC/bin/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio
9.0/VC/bin/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio 9.0/VC/bin/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio 9.0/VC/bin/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.6)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run cmake --help-policy CMP.
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/testcode/asmtest/cmake_win32
On a x64 command prompt (using the compiler string -G Visual Studio 9 2008
Win64), the result is identical except the cmake command outputs the error
message Assembler not found (I'm guessing it still looking for ML.EXE instead
of ML64.exe ?).
Any ideas ? If I want to circumvent the cmake ASM system entirely and use set
up custom build myself (say associated with .s files), is there a tutorial on
how to do this (using add_custom_command I assume ?)
_
Windows Live Messenger: Happy 10-Year Anniversary—get free winks and emoticons.
http://clk.atdmt.com/UKM/go/157562755/direct/01/#pragma once
#include targetver.h
#include stdio.h
#include tchar.h
extern C int f(int n);
int _tmain(int argc, _TCHAR* argv[])
{
int n=f(2);
printf(%d\n,n);
return 0;
}
ENABLE_LANGUAGE(ASM_MASM)
PROJECT(AsmTest)
ADD_EXECUTABLE(AsmTest asmtest AsmTestFunc.asm)
; Listing generated by Microsoft (R) Optimizing Compiler Version 15.00.21022.08
include listing.inc
INCLUDELIB LIBCMT
INCLUDELIB OLDNAMES
PUBLIC f
; Function compile flags: /Odtp
_TEXT SEGMENT
n$ = 8
f PROC
; File c:\testcode\asmtest\testfunc.c
; Line 4
mov DWORD PTR [rsp+8], ecx
; Line 5
mov eax, DWORD PTR n$[rsp]
shl eax, 1
; Line 6
ret 0
f ENDP
_TEXT ENDS
END
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
I manufactured a simple setup to demonstrate what I have. I hope this
helps.
Thanks,
Kenny
CMakeLists.txt
~~
CMAKE_MINIMUM_REQUIRED( VERSION 2.6.4 )
ADD_EXECUTABLE( main
main.cc
)
SET( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
SET( CMAKE_SHARED_LIBRARY_PREFIX )
FIND_LIBRARY( THOST_LIBRARY thostmduserapi.so
PATHS /home/kchang/sandbox/thost )
SET( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
MESSAGE( STATUS DEBUG: THOST_LIBRARY = ${THOST_LIBRARY} )
TARGET_LINK_LIBRARIES( main
${THOST_LIBRARY}
)
output
~
kch...@fiji:~/sandbox/thost$ rm -rf CMakeCache.txt
kch...@fiji:~/sandbox/thost$ ../cmake-2.6.4/bin/cmake .
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- DEBUG: THOST_LIBRARY = /home/kchang/sandbox/thost/thostmduserapi.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/kchang/sandbox/thost
kch...@fiji:~/sandbox/thost$ make VERBOSE=1
/home/kchang/sandbox/cmake-2.6.4/bin/cmake -H/home/kchang/sandbox/thost
-B/home/kchang/sandbox/thost --check-build-system
CMakeFiles/Makefile.cmake 0
/home/kchang/sandbox/cmake-2.6.4/bin/cmake -E cmake_progress_start
/home/kchang/sandbox/thost/CMakeFiles
/home/kchang/sandbox/thost/CMakeFiles/progress.make
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory `/local/home/kchang/sandbox/thost'
make -f CMakeFiles/main.dir/build.make CMakeFiles/main.dir/depend
make[2]: Entering directory `/local/home/kchang/sandbox/thost'
cd /home/kchang/sandbox/thost
/home/kchang/sandbox/cmake-2.6.4/bin/cmake -E cmake_depends Unix
Makefiles /home/kchang/sandbox/thost /home/kchang/sandbox/thost
/home/kchang/sandbox/thost /home/kchang/sandbox/thost
/home/kchang/sandbox/thost/CMakeFiles/main.dir/DependInfo.cmake --color=
Dependee
/home/kchang/sandbox/thost/CMakeFiles/main.dir/DependInfo.cmake is
newer than depender
/home/kchang/sandbox/thost/CMakeFiles/main.dir/depend.internal.
Scanning dependencies of target main
make[2]: Leaving directory `/local/home/kchang/sandbox/thost'
make -f CMakeFiles/main.dir/build.make CMakeFiles/main.dir/build
make[2]: Entering directory `/local/home/kchang/sandbox/thost'
/home/kchang/sandbox/cmake-2.6.4/bin/cmake -E cmake_progress_report
/home/kchang/sandbox/thost/CMakeFiles 1
[100%] Building CXX object CMakeFiles/main.dir/main.cc.o
/usr/bin/c++ -o CMakeFiles/main.dir/main.cc.o -c
/home/kchang/sandbox/thost/main.cc
Linking CXX executable main
/home/kchang/sandbox/cmake-2.6.4/bin/cmake -E cmake_link_script
CMakeFiles/main.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC CMakeFiles/main.dir/main.cc.o -o main -rdynamic
-L/home/kchang/sandbox/thost -lthostmduserapi
-Wl,-rpath,/home/kchang/sandbox/thost
/usr/bin/ld: cannot find -lthostmduserapi
collect2: ld returned 1 exit status
make[2]: *** [main] Error 1
make[2]: Leaving directory `/local/home/kchang/sandbox/thost'
make[1]: *** [CMakeFiles/main.dir/all] Error 2
make[1]: Leaving directory `/local/home/kchang/sandbox/thost'
make: *** [all] Error 2
Bill Hoffman wrote:
Kenneth Chang wrote:
I did, then cmake broke the .so down into its component paths and
library name, and used -Lpath -llibname, which caused the linker
to look for path/liblibname.so
It should not do that in 2.6.4, it should use the full path Do
you have any policy warnings, or do you have the cmake minimum version
set to something very old?
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
On Fri, Aug 14, 2009 at 05:38:06PM -0400, Kenneth Chang wrote:
SET( CMAKE_SHARED_LIBRARY_PREFIX_bak ${CMAKE_SHARED_LIBRARY_PREFIX} )
SET( CMAKE_SHARED_LIBRARY_PREFIX )
FIND_LIBRARY( THOST_LIBRARY thostmduserapi.so
PATHS /home/kchang/sandbox/thost )
SET( CMAKE_SHARED_LIBRARY_PREFIX ${CMAKE_SHARED_LIBRARY_PREFIX_bak} )
MESSAGE( STATUS DEBUG: THOST_LIBRARY = ${THOST_LIBRARY} )
TARGET_LINK_LIBRARIES( main
${THOST_LIBRARY}
)
Maybe you need to wait until after you call target_link_libraries() to
reset CMAKE_SHARED_LIBRARY_PREFIX to its original value?
tyler
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] linking with .so w/ non-standard names
Kenneth Chang wrote: I manufactured a simple setup to demonstrate what I have. I hope this helps. ... Is /home/kchang/sandbox/thost/thostmduserapi.so a valid object? I was able to reproduce what you had if I did this: cmake_minimum_required(VERSION 2.6.4) add_executable(foo foo.c) target_link_libraries(foo /home/hoffman/foo/foo.so) If I copied a valid .so from /usr/lib cp /usr/lib/libmpi.so ../foo.so I get this: /usr/bin/gcc-o CMakeFiles/foo.dir/foo.c.o -c /home/hoffman/foo/foo.c Linking C executable foo /home/hoffman/CMake26-build/bin/cmake -E cmake_link_script CMakeFiles/foo.dir/link.txt --verbose=1 /usr/bin/gcc-fPIC CMakeFiles/foo.dir/foo.c.o -o foo -rdynamic ../foo.so -Wl,-rpath,/home/hoffman/foo make[2]: Leaving directory `/home/hoffman/foo/b' If I remove the file and create a bogus one: rm ../foo.so touch ../foo.so Then I get the split: make[2]: Leaving directory `/home/hoffman/foo/b' make -f CMakeFiles/foo.dir/build.make CMakeFiles/foo.dir/build make[2]: Entering directory `/home/hoffman/foo/b' Linking C executable foo /home/hoffman/CMake26-build/bin/cmake -E cmake_link_script CMakeFiles/foo.dir/link.txt --verbose=1 /usr/bin/gcc-fPIC CMakeFiles/foo.dir/foo.c.o -o foo -rdynamic -L/home/hoffman/foo -lfoo -Wl,-rpath,/home/hoffman/foo /home/hoffman/foo/libfoo.so: file not recognized: File truncated -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] How to set ownership for files in Mac Package built with CPack
Hi, The ownership of files is set to the account who builds the package. But I want to set it to root. For debian packages, I can use fakeroot to do that. Is there equivalent of fakeroot on Mac? Thanks! And what if I want to set the ownership to account other than root? Is this doable for debian and Mac with CPack? Thanks, -- Tiger ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
