Starting with CMake v3.11, it is now possible to aliasing an imported
target. So you can have something like that:
if (BUILD_MY_LIB)
add_library(my_lib SHARED )
add_library(MY_NAMESPACE::mylib ALIAS my_lib)
else()
add_library(system_lib SHARED IMPORTED GLOBAL)
set_property(TARGET syste
I've discovered that CMake is not correctly locating ar/strip/etc. if I
override the names of these tools on the command line. I've tried this
with 3.5.2 as well and I get the same incorrect behavior.
Here's an example (this is on a GNU/Linux system):
$ type -a my-ar
/work/bin/my-ar
$ my-ar --v
On Wed, Jun 13, 2018 at 9:46 PM Andrew White
wrote:
> J Decker wrote:
>
> You can define a variable to define the base of the sources
>
> set( SOURCE_ROOT /some/path )
>
>
>
> could be set relative to the current cmake path per cmake that uses those
>
> souces... and then just prefix it
>
>
>
I have a library that needs to be built on some platforms but on others is part
of the OS. I'd like to avoid putting "if platform" conditional code in the
places it is used, but instead hide it away in my platform-specific code.
One way to do this is define a variable mylib_targetname in each
J Decker wrote:
You can define a variable to define the base of the sources
set( SOURCE_ROOT /some/path )
could be set relative to the current cmake path per cmake that uses those
souces... and then just prefix it
add_library(my_lib
${SOURCE_ROOT}/src/a.c
${SOURCE_ROO
That could be. I'll have to see if I can figure a way to get MacPorts to
cough up more information about the commands it is issuing; the MacPorts
people ought to know.
--
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
On Wed, Jun 13, 2018 at 4:34 PM, Michael Jackson <
mike.jack...@bl
CMake is looking for .app package and my guess is that the package being built
is a "unix" style installation. If your project depends on just MacPorts you
should be able to just do "make install" after setting the
CMAKE_INSTALL_PREFIX=/opt/local.
--
Mike Jackson
On 6/13/18, 4:17 PM, "CMake
I’ve been trying to add the Radiance lighting simulation package to the
MacPorts package manager, and I am running into cmake problems. I can build
Radiance with cmake from the command line and from the CMake command line app,
but when I write a MacPorts to build it, it falls down on install.
Hello,
I want to add sub project to xcode generated project. I am adding xcodeproj
folder as a source file and it looks like the sub project is added
correctly to the parent project. But I can not add target dependency from
the parent to the sub project target.
Parent project is generated from cm
On Tue, Jun 12, 2018 at 7:22 PM Andrew White
wrote:
> I have a situation where I want my CMakeLists.txt in a different place
> than my source.
>
> e.g.:
>
> /some/path/project/CMakeLists.txt
> /other/path/source/src/a.c
> /other/path/source/include/a.h
>
> Is there an easy way to say "process th
On 06/13/2018 04:22 AM, Gerhard Olsson wrote:
> The build works on my PC, but not on the Jenkins server running Windows
> Server 2012R2: cmake.exe: error while loading shared libraries: ?: cannot
> open shared object file: No such file or directory
>
> Any steps required to get a binary that runs o
Trying to build lastest release, to get a preview for 3.12-rc1 that should
be released soon. The specific reason is to fix a problem with linking
failing due to response files not generated:
http://cmake.3232098.n2.nabble.com/No-RSP-FILE-if-generating-in-a-path-that-contains-quot-quot-tc7597671.htm
12 matches
Mail list logo
