Hi all,
Is the correct way to tell MSVC6 to build a release version of my
project to use the command SET (CMAKE_BUILD_TYPE Release) in the
CMakeLists.txt file?
If so, there must be something else I'm missing. I can get a debug
version of my dll built, but cannot get a release version built t
James Mansion wrote:
For those that run Windows (and don't have the unixtools installed) the
preferred interface is a GUI anyway.
I don't think that's a good assumption. Windows has a command interpreter
(and in my experience people erroneously believe CMD.EXE is as limited
>For those that run Windows (and don't have the unixtools installed) the
>preferred interface is a GUI anyway.
I don't think that's a good assumption. Windows has a command interpreter
(and in my experience people erroneously believe CMD.EXE is as limited as
COMMAND.COM without having looked at
I'd like to create a library from a mix of
assembler and C files.
I'm reading the book to try to determine how
to achieve this. There seems to be perhaps two
possible approaches.
(Initially this is for Win32, and I have files for NASM
and MASM with extensions .nasm and .masm)
1) define new lang
Doug Henry wrote:
I assume this is a special case and cmake is capable of building fortran
projects?
There should be no problem for projects that do not have modules
(Fortran77 for example). Some support for modules is implemented but it
has never been tested beyond a few toy examples. I do
I assume this is a special case and cmake is capable of building fortran projects?On 5/30/06, Brad King <
[EMAIL PROTECTED]> wrote:Doug Henry wrote:> Has there been any resolution to this issue? I receive a variety of
> mod.proxy errors when compiling fortran using cmake 2.4.2.No one has had time
Doug Henry wrote:
Has there been any resolution to this issue? I receive a variety of
mod.proxy errors when compiling fortran using cmake 2.4.2.
No one has had time to investigate the problem.
-Brad
___
CMake mailing list
CMake@cmake.org
http://www.
Has there been any resolution to this issue? I receive a variety of mod.proxy errors when compiling fortran using cmake 2.4.2.On 11/10/05, Paulo Jabardo
<[EMAIL PROTECTED]> wrote:
Sorry, I musta have mada some very silliy mistake when originally posting: My CMakeLists.txt is as follows: In the t
At 11:11 AM 5/30/2006, Alexander Neundorf wrote:
>If I understood Bill correctly, the idea is to provide a special file which is
>read by cmake and which provides mappings between full cmake variable names
>and short command line parameters.
>Like:
>CMAKE_MAP(CMAKE_INSTALL_PREFIX prefix)
>
>so th
Brandon J. Van Every wrote:
I agree. There's like, 5 hardwired commands that ./configure users see
all the time, that we could have CMake understand.
I totally agree.
Even a simple "configure" shell script wrapping teh appropriate cmake
calls is doing the job fine, here.
Jan.
--
Axel Roebel wrote:
I move this thread back into the user mailing list, because this is not
promotion but interface design. Everybody would suffer if there are any
errors in the command line interface organization!
On Monday 29 May 2006 19:38, William A. Hoffman wrote:
May
Explicitly setting CMAKE_SKIP_RPATH to OFF
addressed the problem.
Thanks,
Iker
Brad King wrote:
Iker Arizmendi wrote:
What is the correct way to set the install RPATH under
CMake 2.4.2? At the moment I do the following within my
project's top most CMakeLists.txt file:
SET(CMAKE_BUILD_WITH_
Hi,
> Von: Thomas Zander <[EMAIL PROTECTED]>
>
> On Tuesday 30 May 2006 16:48, Alexander Neundorf wrote:
> > > But the 'configure' idea is exactly for that set of people who are
> > > used to doing so. And, honestly, unix shell (sh) are available
> > > everywhere. For those that run Windows (and
On Tuesday 30 May 2006 16:48, Alexander Neundorf wrote:
> > But the 'configure' idea is exactly for that set of people who are
> > used to doing so. And, honestly, unix shell (sh) are available
> > everywhere. For those that run Windows (and don't have the unixtools
> > installed) the preferred int
Hi Thomas,
> Von: Thomas Zander <[EMAIL PROTECTED]>
>
> On Tuesday 30 May 2006 14:58, you wrote:
> > I don't think we want to generate a configure script since it will only
> > run on systems with a unix shell.
>
> But the 'configure' idea is exactly for that set of people who are used to
> doin
Hi,
> Von: Amitha Perera <[EMAIL PROTECTED]>
>
> On Mon 29 May 2006, William A. Hoffman wrote:
> > There is a wxWidgets GUI in CVS. The question is, would a GUI make
> > the configure command line people happy, or will there always be a
> > group that wants a -- style command line like configure
[EMAIL PROTECTED] wrote:
I would like to have suggestions/feedback about my usage of CMake for
MSVC2005. I have little project with an executable and a dynamic library.
I would like to generate either the debug and the release version of the
dlls and exes files. So my CMakeLists.txt files looks
Andreas Beckermann wrote:
Hi
I have a problem with FindPythonLibs on unix: if the shared version of this
library is not available (but the static one is!), then dependencies of the
python libraries are not resolved.
I think FindPythonLibs.cmake should place the dependencies into the
PYTHON_LIB
Iker Arizmendi wrote:
What is the correct way to set the install RPATH under
CMake 2.4.2? At the moment I do the following within my
project's top most CMakeLists.txt file:
SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE)
SET(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_PREFIX}/lib)
And the RPATH refuses
Looking at Modules/CMakeFortranCompiler.cmake.in it would appear you can
try to set the environment variable "FC" to indicate your preferred
fortran compiler. Or you could try passing
-DCMAKE_Fortran_COMPILER:STRING=ifort on the cmake/ccmake command line.
(Or setting it in your "initial cache"
On Mon 29 May 2006, William A. Hoffman wrote:
> There is a wxWidgets GUI in CVS. The question is, would a GUI make
> the configure command line people happy, or will there always be a
> group that wants a -- style command line like configure.
A command-line configure is always important. Often, t
Hi,
> Von: William A. Hoffman <[EMAIL PROTECTED]>
...
> to cmake configurable. I think we all agree that avoiding
> cmake -DSOME_REALLY_LONG_CAP_NAME=/some/path is a good thing.
> The question now, is what is the best way to provide better,
> configurable options
> to cmake. I think some fil
On Tuesday 30 May 2006 14:58, you wrote:
> I don't think we want to generate a configure script since it will only
> run on systems with a unix shell.
But the 'configure' idea is exactly for that set of people who are used to
doing so. And, honestly, unix shell (sh) are available everywhere.
For
At 04:05 AM 5/30/2006, Thomas Zander wrote:
>Maybe a little change in approach will solve some hard-to-crack issues.
>If the project manager just runs 'cmake --create-configure' after he made
>some changes in the build system, which in turn will generate a configure
>script with the projects opt
The bug 2331 involving incorrect VC7 folder structure is not fixed in
CVS (cmake version 2.5-20060526). Please can someone look at this.
SET(SOURCE_GROUP_DELIMITER "/")
SET(SOURCE_FILES src_sub1/Testlib.cpp src_sub1/MyTestObj.cpp)
SET(HEADER_FILES src_sub1/MyTestObj.h)
ADD_LIBRARY(TestLibA
On Tuesday 30 May 2006 03:30, William A. Hoffman wrote:
> >> set_variable_property(CMAKE_INSTALL_PREFIX COMMNAD_LINE_OPT
> >> "--prefix")
> >
> >I don't think a configurable behavior is needed here. It is my opinion
> > that there is no need for freedom for these things. It is more
> > important to
Hi,
Why not having it configurable in a file so new mapping can be added without
recompiling.
It's much easier and shorter to remember ./configure --prefix=/usr instead of
cmake -DCMAKE_INSTALL_PREFIX=/usr or ./configure --verbose instead of cmake
-DCMAKE_VERBOSE_MAKEFILE
Millions of people h
27 matches
Mail list logo
