Hi Jaka, David,
below I tried to assemble a minimal excerpt from CMake-Files defining a
project that I successfully compile under Windows XP, 32bit, MSVC 10
Express, using the CMake 2.8.5 GUI.
There wasn't anything special about setting up MSVC or CMake, I think I
remember dimly that one had to c
On 09/29/2011 09:22 AM, Hendrik Sattler wrote:
> Zitat von Michael Wild :
>> Just a few of my thoughts on this:
>
> Same for me.
>
>> - There are several ways to handle dead symlinks:
>> 1. Don't check, let the linker complain (status quo)
>> 2. Check whether the found library is a symlink, a
On 09/29/2011 07:15 AM, Clifford Yapp wrote:
> On Wed, Sep 28, 2011 at 8:52 PM, Michael Hertling wrote:
>
> What do you do on systems which have no idea of symbolic links, e.g.
>> previous Windows versions? Adding more platform-specific code to the
>> sources of the FIND_LIBRARY() function?
>
>
ctest_update(SOURCE "${CTEST_SOURCE_DIRECTORY}" RETURN_VALUE
update_result) is producing this error.
> Update command failed: "/opt/bin/svn" "update" "--non-interactive"
If I run svn --non-interactive update manually, the update occurs with
out any problems. Also svn status says that there isn'
On 10/3/2011 1:39 PM, John R. Cary wrote:
I am using the cmakedefine mechanism for a fortran include file.
If the variable is not defined, rather than
/* #undef HAVE_PLASMASTATE */
I need
! #undef HAVE_PLASMASTATE
Are there existing solutions?
Thx...John Cary
You could do something like
I am using the cmakedefine mechanism for a fortran include file.
If the variable is not defined, rather than
/* #undef HAVE_PLASMASTATE */
I need
! #undef HAVE_PLASMASTATE
Are there existing solutions?
Thx...John Cary
--
Powered by www.kitware.com
Visit other Kitware open-source projects
Thanks all, the help is *very* much appreciated. I'll revise and report
back.
On 03/10/2011 15:14, Richard Wackerbarth wrote:
I don't think that you want the SOURCE file in the bundle.
First, you need to process the source file with configure_file():
Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist
On Mon, Oct 3, 2011 at 12:00 PM, Steven Wilson <
steven.wesley.wil...@gmail.com> wrote:
> I was able to get the FOLDER working with the following form:
>
> set_property(GLOBAL PROPERTY USE_FOLDERS ON)
> set_property(TARGET "target" PROPERTY FOLDER "value")
>
> The following construct does not work
I was able to get the FOLDER working with the following form:
set_property(GLOBAL PROPERTY USE_FOLDERS ON)
set_property(TARGET "target" PROPERTY FOLDER "value")
The following construct does not work (in either Visual Studio or Xcode):
set_target_properties(target PROPERTY FOLDER "value")
In Xco
My apology ... I haven't kept up with the non-explicit implications of the
Mac-specific properties.
On Oct 3, 2011, at 9:34 AM, David Cole wrote:
> On Mon, Oct 3, 2011 at 10:14 AM, Richard Wackerbarth
> wrote:
> I don't think that you want the SOURCE file in the bundle.
>
> First, you need to
On Mon, Oct 3, 2011 at 10:14 AM, Richard Wackerbarth wrote:
> I don't think that you want the SOURCE file in the bundle.
>
> First, you need to process the source file with configure_file():
> Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist as input
> and ${CMAKE_CURRENT_BINARY_DIR}/Info.plist as outp
On Mon, Oct 3, 2011 at 10:22 AM, David Cole wrote:
> On Sat, Oct 1, 2011 at 4:08 PM, Stephen Torri wrote:
>
>> On Sat, 2011-10-01 at 13:50 -0400, David Cole wrote:
>> > On Mon, Sep 26, 2011 at 11:37 AM, Stephen Torri
>> > wrote:
>> > I am using CMake to run SWIG to generate C# wrapper fi
I don't think that you want the SOURCE file in the bundle.
First, you need to process the source file with configure_file():
Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist as input
and ${CMAKE_CURRENT_BINARY_DIR}/Info.plist as output.
Then you incorporate the configured version into the bundle:
set_
Hi Daniel
In a word: badly :(
1. I cannot get CMake to parse this:
# should end up in resources section
SET (RESOURCE_FILES ./WV.icns ./InfoPlist.strings ./MainMenu.xib
./Info.plist)
# we want an OSX bundle
set_target_properties(${this_target} PROPERTIES MACOSX_BUNDLE_INFO_PLIST
${CMAKE_CURR
Hi,
Let me know how it works out for you...
We will be writing an article about this subject (platform independence, OSX,
iOS, Windows, mainly focussed on OpenGL/ES1/ES2) in the fall,
so we need all the feedback we can get ;-)
Thanks,
Daniel Dekkers
On Oct 2, 2011, at 6:27 PM, g...@novadsp.com
Am Sonntag, 2. Oktober 2011, 12:21:01 schrieb Cristobal Navarro:
> hello,
>
> as many of us, i am making a library and this is my first time. I have some
> concept questions.
>
> for example, my library depends on "GLEW" library. Therefore applications
> that use my library must compile with "-l
Hi all,
I'm trying to build cmake 2.8.5, but the system I'm building on doesn't
have a dynamic libraries, so static only.
When cmake comes to link I get this (with debug from make)
Invoking recipe from Source/CMakeFiles/ccmake.dir/build.make:365 to
update target `bin/ccmake'.
Linking CXX exe
Il 23/09/2011 7.36, Alan W. Irwin ha scritto:
On 2011-09-22 16:14-0400 David Cole wrote:
Please try this version of CMake on your projects and report any
issues to the list or the bug tracker.
Happy building!
Hi Dave:
I have done fairly exhaustive tests of the PLplot build and test system
u
Hi Michael,
On Sun, Oct 2, 2011 at 6:07 PM, Michael Hertling wrote:
> On 10/01/2011 10:07 AM, Yuri Timenkov wrote:
> > that's the problem: you don't know neither file name nor it's location,
> > especially in multi-configuration generators.
>
> You *do* know a debug file's name and location, eith
19 matches
Mail list logo
