Please, I would like to see that script template. I'm also looking at the
source for BundleUtilities. It seems like it shouldn't be difficult to make a
module that provides the generic functionality across platforms.
> On Sep 12, 2015, at 9:09 PM, Michael Jackson
> wrote:
>
> I have a mix of
I have a mix of .app and command line executables for our project on OS X. I
wrote a templated .sh file that cmake uses to “configure_file()” by filling in
details needed. The Script itself does the “fix up” stuff by running otool,
parsing the output, looking for the libraries and then updating
On Sep 12, 2015 4:54 PM, "Seth Cantrell" wrote:
>
> I would prefer to not be required to use the .app bundle directory
structure at all. I'm not producing a .app. The program is a command line
program intended to be run directly from Terminal.app, not a GUI program
intended to be launched from Mac
>
> On Sep 12, 2015, at 5:28 PM, Dan Kegel wrote:
>
> On Sat, Sep 12, 2015 at 1:52 PM, Seth Cantrell
> wrote:
>> I have a project which uses fixup_bundle on Windows to package up the exe
>> with the third-party dlls it requires. On Mac OS X this same packaging
>> process fails. It looks like
I must have missed that, thanks!
2015-09-12 15:30 GMT+02:00 Nils Gladitz :
> On 12.09.2015 15:04, Wojciech Mamrak wrote:
>>
>> install(TARGETS foo
>> EXPORT FooTargets
>> ARCHIVE DESTINATION "${INSTALL_LIBDIR}")
>
>
> Your target's install DESTINATION is absolute which is why the
On Sat, Sep 12, 2015 at 1:52 PM, Seth Cantrell wrote:
> I have a project which uses fixup_bundle on Windows to package up the exe
> with the third-party dlls it requires. On Mac OS X this same packaging
> process fails. It looks like on Mac OS X this utility is assuming I want to
> producing a
I have a project which uses fixup_bundle on Windows to package up the exe with
the third-party dlls it requires. On Mac OS X this same packaging process
fails. It looks like on Mac OS X this utility is assuming I want to producing a
.app bundle.
I realize this utility originated on Mac OS X spe
On 12.09.2015 15:04, Wojciech Mamrak wrote:
install(TARGETS foo
EXPORT FooTargets
ARCHIVE DESTINATION "${INSTALL_LIBDIR}")
Your target's install DESTINATION is absolute which is why the exported
location is absolute as well.
e.g. using "DESTINATION lib" instead of "DESTINAT
Hello,
based on both wiki and this presentation:
https://archive.fosdem.org/2013/schedule/event/moderncmake/attachments/slides/258/export/events/attachments/moderncmake/slides/258/cmake_fosdem_2013.pdf
I have made this simple example. Its purpose is to test installing
projects and importing them
