jmerkow schrieb:
>I am trying to use configure_file but I get a permissions denied error.
>
>Code:
>configure_file(${TestProj_SOURCE_DIR}/CMake/developer-core-script.in
>${TestProj_BIN_DIR}/mysim)
>
>Error:
>CMake Error: Could not open file for write in copy operation /mysim.tmp
>CMake Error: :
I am trying to use configure_file but I get a permissions denied error.
Code:
configure_file(${TestProj_SOURCE_DIR}/CMake/developer-core-script.in
${TestProj_BIN_DIR}/mysim)
Error:
CMake Error: Could not open file for write in copy operation /mysim.tmp
CMake Error: : System Error: Permission deni
Hi,
I have a custom command to copy over some javascript files from the source
to the build tree and along with that run them through a javascript lint
tool. The main point of the lint is to catch syntax errors and the like
early on.
Unfortunately the lint tool also reports all kinds of warnings
Hello,
I know how to create bundles for applications, but how can I create bundles for
libraries. For example when I want to create a plugin for an adobe product
(Illustrator => plugin.aip)?
The add_library command does not except MACOSX_BUNDLE, only MODULE, SHARED and
STATIC are allowed. The
Hi,
I've been working with CPack for about two weeks now and am having a hard
time finding answers for some of my questions. I'm trying to use CMake to
generate an installer via PackageMaker on OS X. So far, I've got it
creating a valid installer that installs the app in the specified path.
What I
I have a function that makes simpler to implement a find script for simple
libraries.
mesh_find_package
(
ExampleModule
MODULE_PRETTY_NAME "Example Module - for demonstration purposes only"
INCLUDE_SEARCH_FILE ExampleModule/ExampleClass.hpp
INCLUDE_PATH_HINTS */usr/local/include
On Jan 23, 2014, at 4:17 PM, Stephen Kelly wrote:
> Andreas Schuh wrote:
>
>>
>> On Jan 23, 2014, at 1:11 PM, Andreas Schuh
>> wrote:
>>
>>>
>>> On Jan 23, 2014, at 9:40 AM, Stephen Kelly
>>> wrote:
>> Another example: You have code for adding scripts as executables. What
>>
On Thu, 2014-01-23 at 11:40 -0500, Brad King wrote:
> On 01/23/2014 11:36 AM, Paul Smith wrote:
> > I see. That's a shame :-(.
>
> Unfortunately it is an Xcode limitation that CMake cannot work around.
>
> > Kind of unpleasant. Anyone have any ideas?
>
> Add an "empty.c" source protected by if
On Thu, 2014-01-23 at 10:22 -0500, Brad King wrote:
> On Thu, Jan 23, 2014 at 8:03 AM, Paul Smith wrote:
> > add_library(mylib STATIC $)
> [snip]
> > The Makefile generators work fine
> >
> > For Xcode, though, the link fails:
>
> This is a known limitation. From the add_library documentation:
On 01/23/2014 11:36 AM, Paul Smith wrote:
> I see. That's a shame :-(.
Unfortunately it is an Xcode limitation that CMake cannot work around.
> Kind of unpleasant. Anyone have any ideas?
Add an "empty.c" source protected by if(XCODE).
Also be sure to set the POSITION_INDEPENDENT_CODE target p
Andreas Schuh wrote:
>
> On Jan 23, 2014, at 1:11 PM, Andreas Schuh
> wrote:
>
>>
>> On Jan 23, 2014, at 9:40 AM, Stephen Kelly
>> wrote:
>>>
> Another example: You have code for adding scripts as executables. What
> are the generic (non-BASIS related) use cases for that?
>
Andreas Schuh wrote:
>> Yes, that's what I was referring to. I see why you have it. I'm not
>> convinced it should be upstreamed.
>
> I guess most people can live with defining a CMake macro for it if they
> want to.
I thought it might make sense for unit tests, but something else generally
intr
On Thu, Jan 23, 2014 at 8:03 AM, Paul Smith wrote:
> add_library(mylib STATIC $)
[snip]
> The Makefile generators work fine
>
> For Xcode, though, the link fails:
This is a known limitation. From the add_library documentation:
http://www.cmake.org/cmake/help/v2.8.12/cmake.html#command:add_li
On Jan 23, 2014, at 1:11 PM, Andreas Schuh wrote:
>
> On Jan 23, 2014, at 9:40 AM, Stephen Kelly wrote:
>>
Another example: You have code for adding scripts as executables. What
are the generic (non-BASIS related) use cases for that?
>>> You can define dependencies among them
On 01/23/2014 02:51 PM, NoRulez wrote:
I know I can use CMAKE_CL_64 to detect 32/64 bit and MSVC12 if the Visual
Studio 2013 generator is used.
I use CMAKE_SIZEOF_VOID_P which is "8" for 64-bit and "4" for 32-bit builds.
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and
I know I can use CMAKE_CL_64 to detect 32/64 bit and MSVC12 if the Visual
Studio 2013 generator is used.
But what about other compilers/IDEs?
> Am 23.01.2014 um 08:19 schrieb NoRulez :
>
> Hello,
>
> at the moment I test with if("${CMAKE_GENERATOR}" STREQUAL "Visual Studio 12")
>
> in the up
On Jan 23, 2014, at 9:40 AM, Stephen Kelly wrote:
> Andreas Schuh wrote:
>> How often have you seen CMake code as the following
>>
>> add_executable(foo foo.cpp)
>>
>> ?
>
> I see executables with a single source file only in dummy test code, and
> even then
>
> add_executable(foo main.cpp
Find one minor correction to my previous post below.
On Jan 23, 2014, at 1:11 PM, Andreas Schuh wrote:
> For example, in case of Python, you can “wrap” the script and have it act as
> both Windows NT Script and Python script by adding the following line at the
> top
>
> @setlocal enableextens
Hi all. I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. I've
discovered a bug in the Xcode generator when dealing with OBJECT and
STATIC libraries. This example works fine on Linux, and on MacOS with
the Makefile generator. I also haven't noticed a problem on Windows
(MSVC).
What I'm do
Hi Lucas.
There's no portable way to do that, simply because not all systems support
something like this (e.g. Windows doesn't ). For Linux, you can look into
the various options of handling RPATH (such as BUILD_WITH_INSTALL_RPATH,
SKIP_BUILD_RPATH, INSTALL_RPATH etc.).
Petr
On Thu, Jan 23, 201
Hello,
Is there a CMake rule to tell an executable where to look for its dynamic
libraries when running? So that the dependencies are correctly loaded at
runtime.
Regards,
Lucas SOLTIC
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.o
Andreas Schuh wrote:
> How often have you seen CMake code as the following
>
> add_executable(foo foo.cpp)
>
> ?
I see executables with a single source file only in dummy test code, and
even then
add_executable(foo main.cpp)
is more common.
>
> The basis_add_executable supports this use c
Andrew Hundt wrote:
>>
>> > Website: http://opensource.andreasschuh.com/cmake-basis/index.html
>> > GitHub: https://github.com/schuhschuh/cmake-basis/
>>
>> The repo is surprisingly large (67 mb) for something like this. I
>> consider such large files in a git repo to be bad practice. This is just
23 matches
Mail list logo
