On 2018 M01 22, Mon 15:16:50 CET Sik wrote:
> Hello CMake users and devs,
>
> In openmeeg we are reviewing our MKL package finder to make it more
> maintainable for ourselves and others who had adopted our solution.
> Therefore I'm writing you requesting comments and feedback so that is
> useful f
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 CMake users and devs,
In openmeeg we are reviewing our MKL package finder to make it more
maintainable for ourselves and others who had adopted our solution.
Therefore I'm writing you requesting comments and feedback so that is
useful for everyone.
Here is the project we have set up in orde
Hi,
I need to integrate an externally built (shared) library as a logical
build target into my CMake configuration which consists of several
shared library files (dlls/dylibs).
Usually I'd do the following:
find_path(MyLib_INCLUDE_DIR mylib.h HINTS ${MyLib_PATH}/include)
find_library(MyLi
