Could be a change in ninja. Our machine updates ninja each build.
- sent from my open source android phone.
On May 22, 2012 6:55 PM, "Claus Klein" wrote:
> But it works for each variant:
>
> claus-kleins-macbook-pro:My Tests clausklein$ mkdir ninja
> claus-kleins-macbook-pro:My Tests clausklein
But it works for each variant:
claus-kleins-macbook-pro:My Tests clausklein$ mkdir ninja
claus-kleins-macbook-pro:My Tests clausklein$ cd ninja/
claus-kleins-macbook-pro:ninja clausklein$ pwd
/Users/clausklein/Downloads/cmake/My Tests/ninja
claus-kleins-macbook-pro:ninja clausklein$ "/usr/local/C
Yes, you changed the test configuration and that configuration will work.
However, for other generators, you do not need to add the -DMAKE_SUPPORTS_SPACES
Richard
On May 22, 2012, at 5:18 PM, Claus Klein wrote:
> claus-kleins-macbook-pro:CompileCommandOutput clausklein$ "/usr/local/CMake
> 2.8
it works on my macbook:
"/usr/local/CMake 2.8-8.app/Contents/bin/cmake" --version
cmake version 2.8.8.20120520-g4742e
claus-kleins-macbook-pro:CompileCommandOutput clausklein$ "/usr/local/
CMake 2.8-8.app/Contents/bin/cmake" -G Ninja -DMAKE_SUPPORTS_SPACES=1
-- The CXX compiler identification
Thanks for the information!
On Tue, May 22, 2012 at 3:27 PM, David Cole wrote:
> It is customary, but not enforced, to have only one project command in a
> CMakeLists.txt file.
>
> The project command maps to generated *.sln files for the Visual Studio
> generators.
>
> All targets defined after
You're welcome.
Be careful with that technique, though.
If somebody configures your project with CMAKE_INSTALL_PREFIX set to
C:/Put/Stuff/Here, they'll end up with your main install tree underneath
that, and then all your custom dir files in "C:/Put/Stuff/CustomDir".
On Tue, May 22, 2012 at 3:3
It is customary, but not enforced, to have only one project command in a
CMakeLists.txt file.
The project command maps to generated *.sln files for the Visual Studio
generators.
All targets defined after the project command in the same CMakeLists.txt
file, or any included by virtue of add_subdire
On Monday 14 May 2012, Mario Bensi wrote:
> Hi,
>
> The last file with all change requested is correct for you ?
>
> Do you think it's possible to integrate it in cmake ?
I'd say it looks good now.
Did you follow these steps already ?
http://www.cmake.org/Wiki/CMake/Git/Account#Git
Alex
--
Po
Turns out that ImageMagick is only used by test routines in my
program. I just comment out those routines in CMakeLists.txt and the
main program builds and works fine. I don't have to worry about OpenCL
anymore.
I think this is ImageMagick's fault. If I need this library in the
future, I'll probab
I got it to work.
Under windows/NSIS I set the destination to "../CustomDir" instead of
$CustomDir.
With this and a custom nsis script which knows the location it is possible to
run CPack.
In the NSIS script I've the following
Var $CustomDir="@CPACK_TEMPORARY_DIRECTORY@\..\CustomDir"
After thi
Hi,
I was wondering if there is a way to undefined a project(). I want to do
this to prevent projects from being included in a solution when I generate
for Visual Studio. Example:
project( A )
add_executable( A a.cpp )
project( B )
add_executable( B b.cpp )
add_executable( C c.cpp )
I don't want
Hi,
You should have either 2 build trees or use custom commands.
If you have a lot of files you should go first way.
To ease development you may compile other tree using external project.
Unfortunately external project is not rebuilt if its sources changed. You
have to do it manually.
On Fri, May
On 5/22/2012 7:35 AM, Richard Wackerbarth wrote:
One of the differences that shows up in the dashboard is that there is a
compile test which passes with normal Unix file paths, but fails when
there is a space in one of the directory names. Perhaps we need to add
an explicit test for everyone, nin
It seems that this library is ONLY installed with Xcode which leads me to
believe that libclparser.dylib should ONLY be used during development and is
NOT a deployable library. Yes there are all sorts of ideas about copying it
from Snow Leopard but there are both technical and legal issues surro
My Lion has OpenCL framework too. But if you go down the path, there
is no 'libclparser.dylib' in
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/,
while it exits in Snow Leopard.
And by googling ImageMagick and libclparser.dylib, I found people
having this issue as well. The solu
You have a bad install of Lion (OS X 10.7.x). I just checked 3 different Lion
machines and ALL have OpenCL.framework installed. So I would suspect your Lion
Machine. Lion uses OpenCL for lots of system level calls so a Lion Install
without OpenCL is just plain Broken.
__
I have Lion 10.7.4 on my laptop and I do have an OpenCL.framework in
"/System/Library/Frameworks/OpenCL.framework/"
So the real question is: why doesn't it just work for you? Because it
should work without you having to copy the OpenCL framework into your
bundle.
Especially if the OpenCL.framewor
Sorry I forgot to mention what the framework is. I believe the OpenCL
framework is from MacOS since I checked two Snow Leopard machines and
both have the framework.
I am building my program in Snow Leopard. The program uses a library
called 'ImageMagick', which uses the OpenCL framework. In Snow
L
If you compile/install these 3rd party libraries yourself, and compile against
them, then they are automatically recognized as non-system libraries. That's
the approach I take instead of trying to overload the behavior to treat some
system libraries as non-system ones.
Clint
On Tuesday, May
I too am curios as to why you need to copy ANYTHING from /System/Frameworks.
Typically if a framework is in there then it is installed on OS X BY Apple. If
you are deploying your application to an OS X machine that does NOT have this
file then the version of the operating system (OS X) will NOT
My previous email was your first hint that this might not be a good idea.
This error message is the second hint that this might not be a good idea.
You can try setting "BU_COPY_FULL_FRAMEWORK_CONTENTS" to ON before calling
fixup_bundle. That will recursively copy the framework into the bundle
rat
After setting the framework type to 'other', the framework structure
is copied into my bundle, including the file OpenCL, but missing
libclparser.dylib.
And I got the following errors:
CPack: Create package using DragNDrop
CPack: Install projects
CPack: - Run preinstall target for: CISMM_VIDEO
CP
I have seen this question asked before, but did not find any good answer for
it, so I was hoping that meanwhile someone might have found a good solution.
I need to select one of the projects for building in our Visual Studio solution
(that contains ~ 20 total projects) only in a certain configu
Hi,
try as I might, I can't see a difference between the output and
expected output. Perhaps a copy-paste error?
Petr
On Tue, May 22, 2012 at 3:07 AM, Marmot Ken wrote:
> here is the function :
>
> FUNCTION( Append_headers_to_src_list src_list_out src_list_in
> header_file_path_in )
> MESS
One of the differences that shows up in the dashboard is that there is a
compile test which passes with normal Unix file paths, but fails when there is
a space in one of the directory names. Perhaps we need to add an explicit test
for everyone, ninja or otherwise, to test that compiles work with
On 22/05/12 18:20, Kfir Lavi wrote:
I would just compile it twice and create my-debug.rpm and my.rpm
Is that a viable solution for you?
I am gravitating towards that option.
Regards
--
Nicholas Yue
Graphics - RenderMan, Visualization, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
Please take a look at the CMake dashboard:
http://open.cdash.org/index.php?project=CMake
I will allow the ninja generator to be enabled by default after interested
parties fix all the failing tests in the "Nightly Expected" section related
to the ninja generator submissions.
Honestly, I was op
Yes, it's possible. But I would only advise it if you do it on a
per-framework basis, you built & installed it yourself, and you know for
certain that the framework in question works fine when moved from its
"/System/Library" location.
Is this an OpenCL that you built yourself, or did it come from
On Tue, May 22, 2012 at 1:45 AM, Eric Noulard wrote:
> 2012/5/21 Nicholas Yue :
> > Hi,
> >
> >I can build debug and release code by setting the CMAKE_BUILD_TYPE
> > variable.
> >
> >What is the recommend process/workflow if I wish to
> build/install/package
> > both the Debug and Release
29 matches
Mail list logo