2007/8/8, gga <[EMAIL PROTECTED]>:
> I'm currently using cmake for a variety of projects. Love it.
> However, one feature I find myself missing more and more is one from
> autotools configure scripts: AC_ARG_ENABLE().
> That is, the ability to allow the configuration script (ie. cmake) to be
> run
I'm currently using cmake for a variety of projects. Love it.
However, one feature I find myself missing more and more is one from
autotools configure scripts: AC_ARG_ENABLE().
That is, the ability to allow the configuration script (ie. cmake) to be
run with arbitrary flags to turn on or turn off
doing exacly that was exactly the reason I wrote here...
in my first email of this trhread you will see the problems doing that
Philip Lowman wrote:
Alex Dantart wrote:
Matthew Woehlke wrote:
Alex Dantart wrote:
Matthew Woehlke wrote:
Any reason you aren't using a pr
Matthew Woehlke wrote:
Alex Dantart wrote:
Matthew Woehlke wrote:
Any reason you aren't using a pre-compiled binary?
where can i find a pre-compiled binary >2.4.2 for ubuntu ? I can't !
http://www.cmake.org/HTML/Download.html ??
WHERE ?!?!?!
no binnaries for ubuntu there !!
the .sh just
Alex Dantart wrote:
Matthew Woehlke wrote:
Any reason you aren't using a pre-compiled binary?
where can i find a pre-compiled binary >2.4.2 for ubuntu ? I can't !
http://www.cmake.org/HTML/Download.html ??
Alternatively, maybe you should try bootstrappping cmake (you can
build cmake on a s
Matthew Woehlke wrote:
Alex Dantart wrote:
Hi:
I need cmake > 2.4.2 for a project.
I'm on ubuntu. First I installed the cmake I have in the dapper
repository: apt-get install cmake
That installs 2.2 successfully:
[snip bits about cmake 2.2 not building newer cmake]
Any reason you aren't usi
Alex Dantart wrote:
Hi:
I need cmake > 2.4.2 for a project.
I'm on ubuntu. First I installed the cmake I have in the dapper
repository: apt-get install cmake
That installs 2.2 successfully:
[snip bits about cmake 2.2 not building newer cmake]
Any reason you aren't using a pre-compiled binary
Hi:
I need cmake > 2.4.2 for a project.
I'm on ubuntu. First I installed the cmake I have in the dapper
repository: apt-get install cmake
That installs 2.2 successfully:
# cmake
cmake version 2.2-patch 3
...
Now, I follow the instructions of Install page
(http://cmake.org/HTML/Install.html)
Alan W. Irwin wrote:
PLplot used to have a library built from Fortran and C. It worked
okay on
Linux, but caused nothing but trouble on other platforms so we split the
library into two libraries, one containing fortran objects and one
containing
C objects, and my life has been much more pea
On 8/7/07, Philip Lowman <[EMAIL PROTECTED]> wrote:
> Jon W wrote:
> > I need to have a specific library linked before all other libraries.
> > For example, I need foo.lib linked before the defaults, "
> > kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib
> > advapi32.lib shell32.lib ole
Jon W wrote:
> I need to have a specific library linked before all other libraries.
> For example, I need foo.lib linked before the defaults, "
> kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib
> advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib
> odbccp32.lib".
>
>
I need to have a specific library linked before all other libraries.
For example, I need foo.lib linked before the defaults, "
kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib
odbccp32.lib".
What would be the best way
David Cole wrote:
The first argument of SET_TARGET_PROPERTIES should be the same as the
first argument of your ADD_LIBRARY or ADD_EXECUTABLE command.
You need one SET_TARGET_PROPERTIES for each library or executable
target where you have a mixture of C, CXX and Fortran code...
HTH,
David
The first argument of SET_TARGET_PROPERTIES should be the same as the
first argument of your ADD_LIBRARY or ADD_EXECUTABLE command.
You need one SET_TARGET_PROPERTIES for each library or executable
target where you have a mixture of C, CXX and Fortran code...
HTH,
David
On 8/7/07, Marie-Christin
David Cole wrote:
Your first one should work. But it should be "CXX" with uppercase X
characters.
That is the case, it's just a Typo
And the value of "TARGET" must be set prior to invoking
SET_TARGET_PROPERTIES using ${TARGET} -- are you sure the value of
${TARGET} is correct...?
How to I
On 2007-08-07 11:02-0700 Marie-Christine Vallet wrote:
Hi,
I have C++ Fortran project, and cannot seem to set the linker_language of
the project. What am I doing wrong?
Any suggestion?
PLplot used to have a library built from Fortran and C. It worked okay on
Linux, but caused nothing but t
Your first one should work. But it should be "CXX" with uppercase X
characters. And the value of "TARGET" must be set prior to invoking
SET_TARGET_PROPERTIES using ${TARGET} -- are you sure the value of
${TARGET} is correct...?
HTH,
David
On 8/7/07, Marie-Christine Vallet <[EMAIL PROTECTED]> wr
Hi,
I have C++ Fortran project, and cannot seem to set the linker_language
of the project. What am I doing wrong?
Any suggestion?
Thanks,
Marie
--- CMakeLists.txt
PROJECT(skinmesh Fortran CXX C ) # the name of your project
SET_TARGET_PROPERTIES(${TARGET}
PROPERTIES
LINKER_LANG
2007/8/7, Frederik Deweerdt <[EMAIL PROTECTED]>:
> On Mon, Aug 06, 2007 at 06:31:32PM +0200, Eric Noulard wrote:
> > 2007/8/6, Alexander Neundorf <[EMAIL PROTECTED]>:
> > 2) Those files MUST define the following variables
> >
> > CPACK_GENERATOR_NAME --> the name of the GENERATOR
> > e.g. S
On 8/7/07, Berardino la Torre <[EMAIL PROTECTED]> wrote:
>
> Trying to read an installation path from the windows registry:
>
> SET(FBXSDK_ROOT_PATH
> [HKEY_LOCAL_MACHINE\\SOFTWARE\\FBX\\File SDK
> 2006.11.1;Install_Dir]
> CACHE PATH "FBX")
Well, whatever the answer, I see no documentation on [HK
On 8/7/07, Christian Convey <[EMAIL PROTECTED]> wrote:
> When my project contains two libraries, where one depends on the other...
>
> Are there any reasons for, or against, calling th
> TARGET_LINK_LIBRARIES command to express that dependency?
>
> Does the answer change depending on whether zero,
On Mon, Aug 06, 2007 at 06:31:32PM +0200, Eric Noulard wrote:
> 2007/8/6, Alexander Neundorf <[EMAIL PROTECTED]>:
> 2) Those files MUST define the following variables
>
> CPACK_GENERATOR_NAME --> the name of the GENERATOR
> e.g. SET(CPACK_GENERATOR_NAME "RPM")
>
> CPACK_RPM_OK will be
When my project contains two libraries, where one depends on the other...
Are there any reasons for, or against, calling th
TARGET_LINK_LIBRARIES command to express that dependency?
Does the answer change depending on whether zero, one, or both of them
are static vs. dynamic libraries?
Thanks,
C
Trying to read an installation path from the windows registry:
SET(FBXSDK_ROOT_PATH [HKEY_LOCAL_MACHINE\\SOFTWARE\\FBX\\File SDK
2006.11.1;Install_Dir] CACHE PATH "FBX") and then using the variable
FBXSDK_ROOT_PATH to setup theinclude and lib directories.
INCLUDE_DIRECTORIES(${FBXSDK_ROOT_P
Christian Convey wrote:
I've got two subprojects: A library FOO, and a program BAR.
If I have this:
ADD_EXECUTABLE(BAR main.cpp)
TARGET_LINK_LIBRARIES(BAR FOO)
Then does CMake somehow realize that it needs to build its FOO library
before trying to link the BAR program?
Yes. TARGET_LINK_LIBR
I've got two subprojects: A library FOO, and a program BAR.
If I have this:
ADD_EXECUTABLE(BAR main.cpp)
TARGET_LINK_LIBRARIES(BAR FOO)
Then does CMake somehow realize that it needs to build its FOO library
before trying to link the BAR program?
Or do I need to explicitly tell it to do this, us
Hi,
I want to remove the /GZ flag which is set for Windows Visual C++ compilers
in CMAKE_CXX_FLAGS_DEBUG_INIT. Furthermore I want to remove some .lib files
defined in CMAKE_C_STANDARD_LIBRARIES_INIT.
How I can achieve this without touching
CMake\Modules\Platform\Windows-cl.cmake ?
I tried remove
27 matches
Mail list logo
