You're right. I tried a simple example and it did work. Now I have to find
out why mine didn't. Thanks for your help.
On Jan 24, 2008 3:23 PM, Sahn Lam <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote:
>
> > Am Donnerstag 24 Januar 2008 schrie
I'm just starting with CMake and was wondering if there is an option in
cmake to specify 64 bit or 32 bit builds ? Or does cmake do an auto
detect on architectures. I just want to know exactly what I'm getting,
64 or 32 bit.
Regards
IMPORTANT: This email remains the property of the Austral
On Wednesday 23 January 2008, Rodolfo Schulz de Lima wrote:
> Hi, currently when invoking make to generate an assembly output, it
> generates it inside CMakeFiles/.dir. Is it possible to generate
> it in the ${CMAKE_CURRENT_BINARY_DIR}? That's where I'd expect it to go
> since I'm doing a 'make .s'
Hi,
On Wednesday 23 January 2008, Jeremy Webster wrote:
> I'm new to cmake and I'm trying to compile a small project in KDE but I
> get the error
>
> Unknown CMake command "kde4_add_ui_files"
>
> I think this command is in KDE4Macros.cmake, which is on my computer in
> /usr/lib/kde4/share/kde4/app
On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote:
> Am Donnerstag 24 Januar 2008 schrieb Sahn Lam:
> > I don't trust myself to be able to specify the dependencies correctly -
> now
> > or in the future. It is not as simple as it seems. For example, let's
> say
> > I have this s
On Jan 24, 2008 2:17 PM, Hendrik Sattler <[EMAIL PROTECTED]> wrote:
> Am Donnerstag 24 Januar 2008 schrieb Sahn Lam:
> > I don't trust myself to be able to specify the dependencies correctly -
> now
> > or in the future. It is not as simple as it seems. For example, let's
> say
> > I have this s
Can someone explain how FindVTK.cmake sets VTK_USE_FILE? I don't see
anywhere in there where it is set. Must be a side effect of some other
command?
On my system, VTK_USE_FILE is getting set to
/usr/bin/usr/lib/vtk-5.0/UseVTK.cmake instead of
/usr/lib/vtk-5.0/UseVTK.cmake.
Thanks!
--
Ori
Am Donnerstag 24 Januar 2008 schrieb Sahn Lam:
> I don't trust myself to be able to specify the dependencies correctly - now
> or in the future. It is not as simple as it seems. For example, let's say
> I have this structure:
>
> libA has gen.h which is generated
> libB has header1.h which includ
I don't trust myself to be able to specify the dependencies correctly - now
or in the future. It is not as simple as it seems. For example, let's say
I have this structure:
libA has gen.h which is generated
libB has header1.h which includes libA/gen.h
libC has header2.h which includes libB/heade
On 24.01.08 14:59:19, Brandon Van Every wrote:
> On Jan 24, 2008 2:50 PM, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
> >
> > Any ideas how to solve this (besides upgrading cmake)?
>
> Quotes?
Thanks.
Andreas
--
Don't get to bragging.
___
CMake mailin
Am Donnerstag 24 Januar 2008 schrieb Sahn Lam:
> I have a top level custom target that depends on a header file generated by
> a custom command. I want this custom target to be invoked first so the
> generated header is built before any other targets needing the header are
> built.
>
> Adding the
Hi,
I have a top level custom target that depends on a header file generated by
a custom command. I want this custom target to be invoked first so the
generated header is built before any other targets needing the header are
built.
Adding the ALL keyword to ADD_CUSTOM_TARGET does what I want in
On Jan 24, 2008 2:50 PM, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
>
> Any ideas how to solve this (besides upgrading cmake)?
Quotes?
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi,
consider the following code snippet:
IF(_boost_REQ_VERSION)
IF( Boost_VERSION LESS ${_boost_REQ_VERSION})
SET(Boost_INCLUDE_DIR FALSE)
ENDIF( Boost_VERSION LESS ${_boost_REQ_VERSION})
ENDIF(_boost_REQ_VERSION)
cmake 2.4.5 and 2.4.6 err
Hi all,
I'm getting repeated questions from other developers at my company about
why the project files CMake generates for Visual Studio aren't movable,
so I sat down, created a minimal project, switched on the
CMAKE_USE_RELATIVE_PATHS flag, and ran cmake. It turns out that there
are actuall
>>
> That worked. The compile lines were:
> /usr/bin/f95 -o CMakeFiles/hello.dir/hello.o -c
> /home/jgonzalez/cmake-test/hello.f90
> /usr/bin/f95 -fPIC "CMakeFiles/hello.dir/hello.o" -o hello -rdynamic
>
> Now, I don't compile any fortran code as part of my project but link to
> a library
Bill Hoffman wrote:
Javier Gonzalez wrote:
I did it and it works (I removed the link just in case):
bash-3.2$ ls
hello.f90
bash-3.2$ cat hello.f90
PROGRAM HelloWorld
WRITE(*,*) "Hello World!"
END PROGRAM
bash-3.2$ gfortran -o hello hello.f90
bash-3.2$ ./hello
Hello World!
bash-3.2$
OK
17 matches
Mail list logo