Hi Jameson,
Good to know you are using Artichoke.
As you described Artichoke provides "ExternalProjectDependency", a CMake
module extending the capabilities of ExternalProject.
It could eventually by integrated into CMake once the API is stable, the
documentation is complete it is more widely ad
Hi Xianyi,
By updating FindBlas.cmake, did you mean that the module should try to find
OpenBlas if it could not find any other implementation ? Or do you want to
provide an easy for developer to import the OpenBlas library in their
project ?
Either way, as described by Eike, the first step would
Hi Eric,
While I don't have yet an example dealing with assets, here is an example
of project using emscripten. See https://github.com/commontk/dcmjs
May be you could re-use the macro "em_add_tracked_link_flag" like it is
done for --pre-js, etc See [1]
Hth
Jc
[1]
https://github.com/kripken
On Friday, November 07, 2014 03:50:32 PM Eric Wing wrote:
> I have a build and packaging system where I can distribute (mostly)
> standalone apps for Linux desktop. I am using the default CPack
> installer which creates .tar.gz, .Z, and .sh files.
>
> I like this opposed to the .deb/.rpm package s
I have a build and packaging system where I can distribute (mostly)
standalone apps for Linux desktop. I am using the default CPack
installer which creates .tar.gz, .Z, and .sh files.
I like this opposed to the .deb/.rpm package systems because users
don't need root access to install/use my stuff
I've solved my problem with special macroses. First saves all non-cache
variables (have to be called at the beginning of the function) and second
one propagates all the changed/added variables to the parent scope (have to
be called of at end of the function). If someone interested in code, it's
her
Thank you for advice Petr! I will go with this solution if can't find
another one. CMake macroses are slightly weird so I'm trying to avoid them
:)
On Fri, Nov 7, 2014 at 4:39 PM, Petr Kmoch wrote:
> Hi Andrey.
>
> As a workaround, you could make the calling context a macro instead of a
> funct
Hi Andrey.
As a workaround, you could make the calling context a macro instead of a
function. Macros don't introduce variable scope.
Petr
On Fri, Nov 7, 2014 at 4:23 PM, Andrey Upadyshev wrote:
> Hello!
>
> I'm writing a wrapper around find_package so I call find_package from my
> own function
Hello!
I'm writing a wrapper around find_package so I call find_package from my
own function. I found it's near impossible because all the variables set by
finders remain in the scope of my wrapper function, rather than in the
caller's scope. Is there any way to force find_package to set all varia
Hi all,
we used CMake 2.8 so far and had used the environment variable
CMAKE_ROOT to tell the cmake binary, where to find its Modules etc.
directories.
We used this in a multiplatform context to store the
architecture-independent files of CMake only once.
It seems, that CMake 3.0 does not hono
10 matches
Mail list logo