On 14. Jul, 2010, at 22:36 , michael.schm...@l-3com.com wrote:
> Hello again,
>
> I read the FAQ on Swig generation, but I still have a couple questions.
> Here's a snippet from my original Makefile.am:
>
> mylib_la_SOURCES = swig_main.i regular.cxx swig_gen.cxx
>
> ...
>
> swig_gen.cxx : swi
Den 14-07-2010 22:24, Dr. X skrev:
Hi All,
I am building an application requiring Xdmf library. Is there a
FindXdmf.cmake that I can use to locate the corresponding library? I
don't find it in Modules/. Thanks a lot.
There is a FindXdmf.cmake from Visit
http://portal.nersc.gov/svn/visit/branches/
Am Wednesday 14 July 2010 schrieb Brian Davis:
> I have a macro which gets called to create cuda and matlab mex enabled
> libraries and apps. I call this macro **twice from within a single
> directory** to create 2 libraries. Problem is that I desire to set
> compiler defines -DWHATEVER=goop etc
I'm trying to create a project that embeds mono. I'm using Visual Studio
2010. In VS, I would normally go to Project -> Properties -> Linker -> Input
and adjust the Additional Dependencies list. How do you add items to this
list in CMake? I've been playing around with add_library and
target_link_li
Hello again,
I read the FAQ on Swig generation, but I still have a couple questions.
Here's a snippet from my original Makefile.am:
mylib_la_SOURCES = swig_main.i regular.cxx swig_gen.cxx
...
swig_gen.cxx : swig_main.i swig_a.i swig_b.i regular.h
swig -Wall $(INCLUDES) -c++ -python -o s
Hi All,
I am building an application requiring Xdmf library. Is there a
FindXdmf.cmake that I can use to locate the corresponding library? I
don't find it in Modules/. Thanks a lot.
There is a FindXdmf.cmake from Visit
http://portal.nersc.gov/svn/visit/branches/bonnell/SIZET/src/CMake/
which is ver
On 07/14/2010 04:37 PM, michael.schm...@l-3com.com wrote:
> Hello,
>
> My project has third party source in a subdirectory. The third party
> source has to be compiled without special options. With autoconf, we
> had "CFLAGS =". How would I do the same with cmake and restore CFLAGS
> to their o
Also strange is I have to change the code:
-snip-
#ifdef gpuPMatrixRecon_EXPORTS
#define DllImportExport __declspec( dllexport )
#else
#define DllImportExport __declspec( dllimport )
#endif
-end snip-
to
-snip-
#if defined(gpuPMatrixRecon_EXPORTS) || defined(cpuPMatrixRecon_EXPORTS)
#define
>> Try changing your macro into a function instead.
I did try as you suggest and it works exactly the same as if it were a
macro.
>From my cmake gui output debug messages the macro or function is seeing the
CPU_RECON and GPU_RECON.
ARG_SRCDIRS =
ARG_CPP_SOURCES = gpuPMatrixRecon.cpp;CUDADeviceP
Try changing your macro into a function instead.
James
On 14/07/2010, Brian Davis wrote:
> I have a macro which gets called to create cuda and matlab mex enabled
> libraries and apps. I call this macro **twice from within a single
> directory** to create 2 libraries. Problem is that I desire t
In regards to this topic *in my opinion* linking directory structure/level
to CMake CFLAGS is not a good design (on the part of CMake)... again *in my
opinion*.
I would prefer there was project level (and ability to inherit project level
settings from another project using the project() where proj
On 07/14/2010 05:51 PM, Kevin Fitch wrote:
> A.a is not intended to be a path. From my reading of the cmake book adding
> .a is the way you say you specifically want the static library over the
> dynamic library. To me libA.a would be a path.
If "A.a" is not the name of a target it's treated as a
On 7/14/2010 12:46 PM, John Drescher wrote:
Be careful with your use of $ENV{PROGRAMFILES} - it might not give you what
you expect on a 64-bit computer. Since the CMake binary is by default
32-bit, you need some logic to make sure you're looking where you think
you're looking.
I had that cover
> Be careful with your use of $ENV{PROGRAMFILES} - it might not give you what
> you expect on a 64-bit computer. Since the CMake binary is by default
> 32-bit, you need some logic to make sure you're looking where you think
> you're looking.
>
I had that covered. I just shortened the example not t
Be careful with your use of $ENV{PROGRAMFILES} - it might not give you what
you expect on a 64-bit computer. Since the CMake binary is by default
32-bit, you need some logic to make sure you're looking where you think
you're looking.
See also:
http://public.kitware.com/Bug/view.php?id=9992 - relat
By default, variables (such as CMAKE_C_FLAGS and CMAKE_CXX_FLAGS) open a new
nested scope with each subdirectory. So, any changes you make in a
directory will only be seen in that directory and its children, not any
parent or sibling directories.
So, in short, you can just do what you were planni
2010/7/14 John Drescher :
> On Wed, Jul 14, 2010 at 11:15 AM, Verweij, Arjen
> wrote:
>> Hi,
>>
>>>
>>>You seem to have a path using \ instead of /
>>>
>>
>> Isn't that to be expected of a PATH setting on a Windows computer?
>> Anyway, the path to the Visual Studio compiler is of the same format
2010/7/14 Benjamin Eikel :
> Hello Mike,
>
> Am Mittwoch, 14. Juli 2010, 17:33:57 schrieb michael.schm...@l-3com.com:
>> I'm a newbie with cmake, and I wanted to clarify a couple things. From
>> what I understand, there's no command to clear CMakeCache files. If I
> the program cmake-gui has a me
-snip-
I do not think that this is necessary. CMake should overwrite the according
values.
-end snip-
IMHO clearing the cache and starting from scratch is the best approach if
you are developing the build spec and not simply compiling 3rdParty source
as the CACHE may contain variables you created
Hello,
Am Sonntag, 11. Juli 2010, 17:40:58 schrieb Kevin Fitch:
> I am transitioning from a make based build system to cmake, overall I am
> quite happy with cmake, but currently there are two snags:
>
> 1) The main project I am doing this on is quite large, it produces about
> 300 targets. So, w
I have a macro which gets called to create cuda and matlab mex enabled
libraries and apps. I call this macro **twice from within a single
directory** to create 2 libraries. Problem is that I desire to set compiler
defines -DWHATEVER=goop etc differently for each lib (for each of the two in
questi
A.a is not intended to be a path. From my reading of the cmake book adding
.a is the way you say you specifically want the static library over the
dynamic library. To me libA.a would be a path.
So, you are saying that there is currently no way in cmake to get transitive
link dependencies AND speci
Hello Mike,
Am Mittwoch, 14. Juli 2010, 17:33:57 schrieb michael.schm...@l-3com.com:
> I'm a newbie with cmake, and I wanted to clarify a couple things. From
> what I understand, there's no command to clear CMakeCache files. If I
the program cmake-gui has a menu option "Delete Cache".
> add a ne
I'm a newbie with cmake, and I wanted to clarify a couple things. From
what I understand, there's no command to clear CMakeCache files. If I
add a new file or change the CMakeLists, then I have to delete the
CMakeCache files manually. If I change an option using ccmake, do I
have to remove the c
On 7/14/2010 11:23 AM, John Drescher wrote:
On Wed, Jul 14, 2010 at 11:15 AM, Verweij, Arjen wrote:
Hi,
You seem to have a path using \ instead of /
Isn't that to be expected of a PATH setting on a Windows computer?
Anyway, the path to the Visual Studio compiler is of the same format and
On 7/14/2010 11:00 AM, Knox, Kent wrote:
Does "." in the name work for any other version of VS?
[KK] I've tested with both vs9& vs10, and it works in vs9. In vs10, even
though the binary name is truncated at the first period, the .pdb and static .lib
files are not truncated and contain mult
On Wed, Jul 14, 2010 at 11:15 AM, Verweij, Arjen wrote:
> Hi,
>
>>
>>You seem to have a path using \ instead of /
>>
>
> Isn't that to be expected of a PATH setting on a Windows computer?
> Anyway, the path to the Visual Studio compiler is of the same format and
> cmake deals with it just fine.
>
Hi,
>Likely someone forgot to use a VERBATIM somewhere.
I guess that would be in the cmake sources then, since my CMakeLists.txt is
quite unspectacular. :)
Arjen
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.k
Hi,
>
>You seem to have a path using \ instead of /
>
Isn't that to be expected of a PATH setting on a Windows computer?
Anyway, the path to the Visual Studio compiler is of the same format and cmake
deals with it just fine.
Regards,
Arjen
___
Powered
On Wed, Jul 14, 2010 at 10:16:36AM -0400, cmake-requ...@cmake.org wrote:
> CMake Error at CMakeLists.txt:4 (SET):
> Syntax error in cmake code at
>
> S:/mnt/usr3/people/verweija/build/CMakeFiles/CMakeTmp/CMakeLists.txt:4
>
> when parsing string
>
> Files\VNI\CTT5.0\include\IA32" /fpe
> Does "." in the name work for any other version of VS?
[KK] I've tested with both vs9 & vs10, and it works in vs9. In vs10, even
though the binary name is truncated at the first period, the .pdb and static
.lib files are not truncated and contain multiple periods.
On 7/13/2010 2:39 PM, Knox,
Hello,
My project has third party source in a subdirectory. The third party
source has to be compiled without special options. With autoconf, we
had "CFLAGS =". How would I do the same with cmake and restore CFLAGS
to their original value in the parent directory?
Thanks,
Mike
___
[snip]
>>
>> Ok first thing: I had two cmakes on my system, one was 2.8.1, and an older
>> 2.6.3 that snuck in through an incorrect script of mine.
>>
>> Second thing: the TARGET_FILE thing works. But the usual add_test(name
>> command) does not.
>
> This is because you set the CMAKE_RUNTIME_
On 07/14/2010 06:40 AM, Paul Harris wrote:
> On 11 July 2010 20:36, Michael Hertling wrote:
>
>> On 07/10/2010 06:54 PM, Paul Harris wrote:
>>> On 9 July 2010 22:39, Michael Wild wrote:
>>>
On 9. Jul, 2010, at 15:48 , Michael Hertling wrote:
> On 07/08/2010 09:47 AM, Paul Harr
On Wed, Jul 14, 2010 at 10:16 AM, Verweij, Arjen wrote:
>
> Hi,
>
>
>
> I’m trying a little F90 example on Windows with cmake. Apparently something
> is amiss, but I can’t find much on Google about it; at least not about this
> particular case.
>
>
>
> All I do is cmake ..\f90example and the fol
Hi,
I'm trying a little F90 example on Windows with cmake. Apparently something is
amiss, but I can't find much on Google about it; at least not about this
particular case.
All I do is cmake ..\f90example and the following appears in my terminal:
S:\mnt\usr3\people\verweija\build>cmake ..\f90e
On 07/14/2010 02:38 PM, Kevin Fitch wrote:
> I have found a situation where transitive link dependencies don't seem to
> work the way I would expect. I have a library A that depends on B. e.g.
>
> target_link_libraries(A B)
> # and elsewhere we have ...
> target_link_libraries(foo A)
> #then B get
I have found a situation where transitive link dependencies don't seem to
work the way I would expect. I have a library A that depends on B. e.g.
target_link_libraries(A B)
# and elsewhere we have ...
target_link_libraries(foo A)
#then B gets linked into foo as expected
#But, if I try to be more e
38 matches
Mail list logo