Nope, sorry. We build android from mac and windows too. And again, I'm more
concerned with how protobuf's config.cmake scripts should be set up to
easily enable users to deal with this problem. I'm trying to get their
build scripts up to date before 3.0.0 leaves beta.
On Tue, May 24, 2016 at 6:05
Another "outside the box" solution that I have had success with is as
follows (Note this solution will only work with Linux):
You can use the Linux binfmt_misc driver to execute non-native executables
through an interpreter. If you google for qemu binfmt wrapper, you'll find
various suitable app
It occurs to me that, much like C++ itself, there are wide variety of ways
to do things in CMake, many of which exist only for legacy compatibility,
and the language had a lot of active develpment recently that allows much
safer, easier to read programs. C++ now has the Core Guidelines and lots of
Hi All,
I am trying to make a framework using a shared library. The docs say
that the target property PUBLIC_HEADER should be a list of interface
header files that install(TARGET ...) will populate
.../.framework/Headers/ with but I cannot get that to happen. I
have set the target property FR
@Hendrik - Yes, unfortunately it didn't help me too much.
Superbuilds are not really an appropriate solution here - The project I'm
working on is too heavily down an alternative path, and I'm trying to set
up the exported .cmake files in the protobuf 3.0 beta to properly support
any sort of option.
I prefer one for both installing and creating packages.
install(TARGETS bar
COMPONENT bar
DESTINATION "./" # This must be "./" not "/" as it has to be a relative path
)
Then set CMAKE_PREFIX_PATH=/Applications/Foo when you do an install.
CMAKE_PREFIX_PATH will be pre-pended to relative pa
In answer to my own question. One way to do it which seems quite neat is as
follows. Using multiple installs:
install(TARGETS bar
COMPONENT bar
DESTINATION "Applications/Foo"
)
install(TARGETS bar
COMPONENT bar-standalone
DESTINATION "./" # This must be "./" not "/" as it has to
On OSX we install an .app to /Applications/Foo/Bar.app. So the install() is set
like:
add_executable(bar
MACOSX_BUNDLE
bar.cpp
)
install(TARGETS bar
COMPONENT bar
DESTINATION "Applications/Foo"
)
When making DMG (DragNDrop) installers I really want the DMG to contain just
the .
This CMake feature is interesting, the first step i plan is to make the
project work first, then i will try to optimize it, and i think this feature
would be used next step. Thanks. :-)
Chuck Atkins wrote
> If you know the full path to the library then I'd suggest using it as
> /path/to/foo/libfo
On Tue, May 24, 2016 at 3:52 AM, Eric Eide wrote:
> As a CMake newbie, I was afraid that I was overlooking some sort of
> "prepackaged" version of this.
Doesn't look like it, but I agree it's the kind of thing that might be usefully
included with CMake.
--
Powered by www.kitware.com
Please ke
10 matches
Mail list logo
