Hello,
The product is a cross-platform API that relies on CMake for the config part.
We ship static and dynamic libraries for Linux, Windows and macOS. Additionally
on macOS we want to provide frameworks to ease integration (headers and a few
dependencies in the bundle framework, etc). In addit
> Le 19 janv. 2018 à 20:01, J Decker a écrit :
>
>
>
>> On Fri, Jan 19, 2018 at 10:44 AM, Lucas Soltic
>> wrote:
>> Hello,
>> Should I conclude that there are no recommendations?
>>
> I would think if there were platform exceptions they would be modifications
> to this...
>
> https://ap
On macOS, the most usual thing is for your code to be self-contained in your
.app bundle. Perhaps if you described more what kind of thing you are building
and why you don't want to do the usual thing, people will have more advice...
On Fri, 19 Jan 2018 19:44:03 +0100, Lucas Soltic said:
>Hel
Hello,
Should I conclude that there are no recommendations?
Best regards,
Lucas
> Le 17 janv. 2018 à 23:49, Lucas Soltic a écrit :
>
> Hello,
>
> By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/local by
> default) as a base for relative install paths. But when you define
Are you just checking if the compiler is GCC? if so I would use
COMPILER_ID
https://cmake.org/cmake/help/v3.8/variable/CMAKE_LANG_COMPILER_ID.html
On Wed, Jan 17, 2018 at 6:19 PM, J Decker wrote:
> It's not entirely related other than Mac
>
> I had to test
>
> if( __COMPILER_GNU AND NOT CMAK
It's not entirely related other than Mac
I had to test
if( __COMPILER_GNU AND NOT CMAKE_COMPILER_IS_GNUCC )
instead of just CMAKE_COMPILER_IS_GNUCC (which was unset)
__COMPILER_GNU was found after doing a dump...
I suppose there's some modern way I'm supposed to test GCC that works on
all
Hello,
By default library install() command uses CMAKE_INSTALL_PREFIX (/usr/local by
default) as a base for relative install paths. But when you define install
rules for macOS frameworks, it doesn't make much sense to install them there.
I'd rather expect something like /Library/Frameworks.
On