Re: [CMake] Creating an installer using cpack

2015-01-09 Thread Gonzalo Garramuño
On 09/01/2015 05:55 p.m., J Decker wrote: the symlinks already exist in the source directory (it sounds like) the problem is they're not being packaged/extracted right... Correct. I changed my symlink script with one that copies the libraries and all problems are gone. Now I am tackling NSI

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread J Decker
On Fri, Jan 9, 2015 at 12:54 PM, Domen Vrankar wrote: > > install( PROGRAM ) will keep executable permissions... (as opposed > to > > using FILES or DIRECTORY ) not sure about symlinks > > Hm forgot about this one... Had problems with it years ago on AIX and > stopped using it back the

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread Domen Vrankar
> install( PROGRAM ) will keep executable permissions... (as opposed to > using FILES or DIRECTORY ) not sure about symlinks Hm forgot about this one... Had problems with it years ago on AIX and stopped using it back then (it removed baked in paths to libraries from executables)... Time

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread Hendrik Sattler
Hi, on Linux, libraries don't need the executable permission set. HS Am 9. Januar 2015 21:30:54 MEZ, schrieb J Decker : >need to use install( PROGRAMS ... ) then > > > >On Fri, Jan 9, 2015 at 7:52 AM, Gonzalo Garramuno >wrote: > >> On 08/01/15 21:56, J Decker wrote: >> >>> I don't think you sh

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread J Decker
need to use install( PROGRAMS ... ) then On Fri, Jan 9, 2015 at 7:52 AM, Gonzalo Garramuno wrote: > On 08/01/15 21:56, J Decker wrote: > >> I don't think you should install libraries like that... things in binary >> would be build products, can you possibly just install the libs as normal >> >

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread Domen Vrankar
> The lib files are not built by cmake but are dependencies for my program. You could move external libraries wih something like this: install(FILES /some/location/libsomething.so DESTINATION lib) > The lib files are symbolic links to the /usr/local/lib directory. For > example: > > Release/lib/l

Re: [CMake] Creating an installer using cpack

2015-01-09 Thread Gonzalo Garramuno
On 08/01/15 21:56, J Decker wrote: I don't think you should install libraries like that... things in binary would be build products, can you possibly just install the libs as normal INSTALL( Target <...> LIBRARY DESTINATION lib ) The lib files are not built by cmake but are dependencies for m

Re: [CMake] Creating an installer using cpack

2015-01-08 Thread J Decker
On Thu, Jan 8, 2015 at 12:46 PM, Gonzalo Garramuno wrote: > I have a cmake file to build my project (mrViewer). The project has > additional script files that are not mentioned in my cmake file. > The project also has dependencies on c libraries installed elsewhere > (/usr/local, etc). > > The t

Re: [CMake] Creating an installer using cpack

2015-01-08 Thread Daniel Schepler
) file(INSTALL \${libfile} DESTINATION \$ENV{DESTDIR}\${CMAKE_INSTALL_PREFIX}/gui/lib/${BUILD_PLATFORM_BASE}) if (IS_SYMLINK \${libfile}) get_filename_component(libfile_target \${libfile} REALPATH) file(INSTALL \${libfile_target

[CMake] Creating an installer using cpack

2015-01-08 Thread Gonzalo Garramuno
I have a cmake file to build my project (mrViewer). The project has additional script files that are not mentioned in my cmake file. The project also has dependencies on c libraries installed elsewhere (/usr/local, etc). The tgz,deb and rpm files currently contain just the main executable aft